Page 1 of 2
3.1.1.1259 - Bad Request issue not resolved?
Posted: Sat Aug 22, 2009 8:14 pm
by weinrich
I downloaded MM 3.1.1.1259, uninstalled my previous version and install the new version. I'm still getting the "Bad Request" error when trying to use Auto-Tag from the Web.
See picture below, which has the MM main window in the background, the error in the Auto-Tag dialog, and the info displayed in "Help -> About", showing that I do, in fact, have 3.1.1.1259 installed and running.
Any ideas?

Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sat Aug 22, 2009 10:26 pm
by Peke
What Amazon site you use?
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 2:13 am
by ravn
I have the same problem, the same error with all of the amazon pages..
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 2:34 am
by Rezonator
I have the same problem since a week or so.
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 7:34 am
by nohitter151
ravn wrote:I have the same problem, the same error with all of the amazon pages..
Rezonator wrote:I have the same problem since a week or so.
Have you both upgraded to 3.1.1.1259? It is fixed for me with that version.
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 9:02 am
by BluAngel
Hi, same problem for me. MM version 3.1.1.1259, I'm still getting bad request error
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 10:26 am
by weinrich
Peke wrote:What Amazon site you use?
I get the same error with all the Amazon sites. It appears that build 1259 has not resolved the problem.
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 11:51 am
by saibbu
same for me. "Bad Request"...
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 11:58 am
by jiri
I can confirm that the build fixes the issue, at least on many machines it was tested on. Anybody having this problem, please let us know as many details as possible about your machine and configuration, a debug log might be useful as well (mail it to me).
Thanks,
Jiri
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 12:45 pm
by jiri
Out internal testing shows that this issue might appear when your computer doesn't have correct time. Please check out whether this isn't your case.
Jiri
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 2:13 pm
by BluAngel
jiri wrote:I can confirm that the build fixes the issue, at least on many machines it was tested on. Anybody having this problem, please let us know as many details as possible about your machine and configuration, a debug log might be useful as well (mail it to me).
Thanks,
Jiri
I'll just send you a PM with debug output. My clock time is correct.
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 2:20 pm
by sam.v.60
salut
tout ok pour moi
a+
Re: 3.1.1.1259 - Bad Request issue not resolved? [SOLVED!]
Posted: Sun Aug 23, 2009 2:29 pm
by weinrich
jiri wrote:Out internal testing shows that this issue might appear when your computer doesn't have correct time. Please check out whether this isn't your case.
That fixed it!
My clock was off by 5 minutes (slow). I updated my time synchronization with the Internet (w32tm.exe on Windows XP) and all is well.
Thanks very much for your support!
-Steve
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Sun Aug 23, 2009 3:43 pm
by Kaizen
Hi
Just upgraded to 3.1.1.1259 and it resolved my problem with downloading album art.
Thank you!
Re: 3.1.1.1259 - Bad Request issue not resolved?
Posted: Mon Aug 24, 2009 2:27 am
by dodger23
Morning All,
When I went to upload the new release put out to get around the Amazon artwork problem; I got the following message:
C:\ Program Files \ Media Monkey \ MMHelper.dll
An error occured while trying to replace the existing file: DeleteFile failed; code 5
Access is denied
Click retry again, Ignore to skip this file (not recommended) or Abort
I clicked retry again half a dozen times; then decided to skip this file; and new installation went ahead; and the artwork problem has been solved.
Am I missing out on something by skipping the above file instruction?
Thanks
Dodger