INTERACT FORUM
More => Old Versions => Media Jukebox => Topic started by: justinp on June 15, 2002, 03:00:13 pm
-
I am getting this error everytime I try and get information from CDDB! I am not behind a firewall or proxy. I was yesterday and I had the proxy information entered where required, even then it was very "hit and miss" as to whether it worked. Now I have removed that proxy information (as I am no longer behind it) and I have this error _every_ time. I am using 8.0.293.
Help!
Justin
-
Did you try reinstalling MJ?
-
Haven't tried reinstalling, is there anything I need to do to ensure I don't loose my media database and settings?
Thanks
Justin
-
I am back behind the firewall today (and therefore have re-added the proxy settings) and CDDB retrieval seems to be working again...I suspect that when I go home tonight and remove the proxy information it will give me this error again though...any ideas on where the problem may lie?
Thanks
Justin
-
Ok, sure enough it didn't work when I was no longer going through the proxy.
I think there is a bug in here somewhere (like maybe it is still trying to contact the proxy even though I unchecked the box) and am willing to test things out if a support person is available to work with me...?
Any takers?
Thanks
Justin
-
This is support. I am a person. Talk to me.
We aren't seeing many CDDB problems, so the problem you have is either configuration or some other program interfering with MJ's CDDB lookups.
Try disabling or uninstalling other music software and reinstalling the full version of MJ as the user you will be running as.
-
About This Firewall.
How Did You Deactivate It?
If you did not uninstall it it may still be blocking you. uninstall it if it is a software firewall.
if you have a router could that be blocking it?
the firewall and Proxy is the only thing i can think of.
Listening to: 'White Christmas' from 'The Sinatra Christmas Album' by 'Frank Sinatra' on Media Jukebox
-
King,
It must be pretty hot down there in NC if you're already dreaming of a white christmas!
Shelly
-
Deleted an accidental duplicate
My apoologies
Justin
-
> We aren't seeing many CDDB problems, so the problem you have is either configuration or some other program interfering with MJ's CDDB lookups.
>
> Try disabling or uninstalling other music software and reinstalling the full version of MJ as the user you will be running as.
The only other music software doing CDDB that I am aware of is Media Player and this is Windows XP so I am not sure if I can even remove that totally?
MJ was originally installed (just a week or so ago) as the user I am running under, if I uninstall what steps do I need to do to preserve my settings and database (if any)?
> How Did You Deactivate It?
I didn't deactive the proxy, I turned off the setting in MJ to go through a proxy by unchecking the box. The proxy/firewall in question is the corporate network where I work and not local to the machine so turning it off is not an option, but again, it only works when I am behind the proxy!
It seems really odd to me that when I am behind the proxy/firewall it works and when I am connected "directly" to the net it doesn't, is this feature (CDDB through a proxy) genernaly heavily used?
Thanks
Justin
-
>> The only other music software doing CDDB that I am aware of is Media Player
Media Player Does Not Use CDDB, Microsoft Uses There Own Data Base.
-
>> I turned off the setting in MJ to go through a proxy by unchecking the box.
humm, well maybe that really does not work.
I do know in the Sample SDK from CDDB if you disable the Proxy it really does not disable it, And thats prob the problem (Maybe An MJ Bug)
-
My gut feel is that not many people use this feature, and if they do then they are not frequently switching between proxy/no proxy so don't see the problem.
I am more than happy to test beta versions if somebody wants to try some workarounds without trying to duplicate the environment...?
Thanks
Justin
-
Justin,
I think your gut may not be reliable. CDDB gets heavy use both with and without proxy servers.
Your configuration has other problems that are not MJ related.
KingSparta's comment about firewalls not being deactivated is a known problem. He's 100% right.
Jim
-
> I think your gut may not be reliable. CDDB gets heavy use both with and without proxy servers
My comment was not that I didn't think it was used, it was that maybe not many people were frequently switching between proxy/no proxy.
> Your configuration has other problems that are not MJ related.
Ok, I won't rule anything out, I just want to find the solution whether it means there is a bug that needs to be fixed or whether it means I screwed something up!
Could you explain what you think may be the problem with my configuration or where I should look?
My web browseing works fine, home and office, as does Windows Messenger and EAC using FreeDB, all of these are using the same proxy settings I have set in MJ when in the office and all use no proxy settings at all when at home.
> KingSparta's comment about firewalls not being deactivated is a known problem. He's 100% right.
I must be confused, are you saying that there is a bug in the CDDB SDK with regards to proxy usage and if so why do you suspect my configuration is at fault and not this bug?
Thanks
Justin
-
I am not sure were the fault is but it may also be a windows problem.
i can't remember how i could fix it before it may have been a registry entry that can be deleted...
I just don't remember.
-
Have the same problem as justin.
I am behind a proxy at work and there I can access cddb.
At home I uncheck the proxy setting in the cddb settings and I change all the proxy settings in the browsers I use (Opera, IE) but MJ cannot access cddb.
Message:
Action: Accessing disk CDDB information
Status: CDDB: Socket open failed (82fa000a)
I am using Windows XP HE and MJ 8.0.329
Hope someone can help
Martin
-
Is CCDB down or have we all been hit with the same virus? I've been getting the same error all evening.
Does anyone have any clues?
-
Justin and Martin,
Without re-reading the entire thread, are you saying that you carry a notebook back and forth between two locations? Same PC, but different settings?
Jim
-
Oops! My error's actually different. It's just appeared tonight, never been a problem before.
Action: Accessing disk CDDB information
Status: CDDB: HTTP processing error (82fa0026)
My details are:
Media Jukebox 8.0.331
Install Path: C:\Program Files\J River\Media Jukebox\
CPU: Intel Pentium III 1003 MHz MMX
Memory: Total - 523 MB, Free - 350 MB
OS: Microsoft Windows 2000 Workstation 5.0 Service Pack 2 (Build 2195)
Internet Explorer: 6.0.2600.0000
ComCtl32.dll: 5.50.4704.1100
Shlwapi.dll: 6.00.2600.0000
Shell32.dll: 5.00.3502.4718
wnaspi32.dll: 4.71 (0001) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-2002 Adaptec, Inc.
Aspi32.sys: 4.71 (0001)
-
Hi Jim,
Yes, that is exactly right. I take my machince home most nights to continue through the laborious process of ripping my entire CD collection.
Justin
-
Exactly. The only thing I change at home is that I uncheck the "use a proxy" settings in Opera, IE and in the CDDB settings of MJ.
Martin
-
Then it sounds like the CDDB control isn't resetting the proxy server. Can you try entering a blank address and port in the CDDB settings? If this works, it's a CDDB bug.
Did you try checking their site for info?
-
I can confirm that it's our bug. It will be fixed in next build.
Nikolay
-
Sorry, I probably should have started a new thread. But now that I'm here, is it your bug that's causing my problem as well?
-
Vlad,
I don't think the error you are receiving is connected to the original post. I'm not sure what this error means (some cryptic CDDB message). Are you using Firewall software?
Nikolay
-
this message error code is in the CDDB sdk doc file
-
It is there, but "HTTP processing error" message does not explain much.
Nikolay
-
>> I can confirm that it's our bug. It will be fixed in next build.
Excellent, I'll be sure to test it and let you know :-)
Now if I can just get JimH to take back the "ass-chewing"
he gave me when I suggested it "felt" like a bug 
Justin
-
Nikolay Sokratov
that is always the way it is.
I think the CDDB docs need a bit more work explaining
-
> Now if I can just get JimH to take back the "ass-chewing" he gave me when I suggested it "felt" like a bug
I take it back. I don't think it was harsh, but if you think so, I apologize.
The light bulbs didn't come on until I realized that when you said this:
> I am not behind a firewall or proxy. I was yesterday ...
you meant not only you but also your PC. Once I knew that, I thought it could be our problem and asked Nikolay to double check.
Anyway, you should be set now.
-
justinp
maybe you can hog tie him and slap him with a dead fish.
let me count the mistakes I made today.
at least no one died thats the good thing.

The Bad: Stock market Down 321 Points
The Good: An Arrest Was Made In Cal
-
Chill out guys, I don't need an apology, just an opportunity to tease a little

No harm no foul.
Justin
-
and Conagra recalled the hamburger I ate last week.
-
justinp
Just joking with you
JimH
>> and Conagra recalled the hamburger I ate last week.
i hope you did not eat 18 million lbs of it.
-
I too just started having this problem after installing 8.0.333.
I have CD cataloging software and there is no problem connecting through that (been on machine for a year). Before the above build, MJ accessed with no problem whatsoever.
-
So when will we see that new build?
The bug is pretty easy to verify -- you can uncheck the box in the interface, watch the registry value HKCU\Software\JRiver\Music Exchange\1.0\Media Jukebox\Properties\CDDB_EnableProxy be set to "0", while the CDDB code continues to use the proxy. What's more bizarre is that recycling the MediaJukebox process doesn't change the behavior (where exactly is the state supposed to be stored). Is this a bug in the constructor/destructor code for CDDB objects?
And is there a workaround we can use while waiting on the new build?