Socket Error # 10057

by **Guest** » Mon Oct 24, 2005 8:25 am

In Admuncher Configuration -> Option -> Filter Targets you can choose to not filter Mediamonkey (at least in the beta version).
Now you can leave Admuncher on and use Amazon auto label option in Mediamonkey anyway!

by **rovingcowboy** » Thu Sep 15, 2005 3:21 am

thanks i am glad it was not the amazon servers

by **pl5bnsf** » Wed Sep 14, 2005 4:35 pm

Just for reference in case anybody else gets a "10057 Socket is not connected" error while auto-tagging, it was due to AdMuncher, an ad blocking html filter I use. Even with AdMuncher turned off I got the error, I had to actually close AdMuncher.

by **rovingcowboy** » Wed Sep 14, 2005 12:53 pm

your welcome here of lately i have been getting lots of error codes from forums and web sites due to heavy vistor loads.

it does kind of make you unsure if it is you or them. but i think this is a them error,

by **pl5bnsf** » Mon Sep 12, 2005 5:18 pm

I was afraid it was just me

I have cleared my IE cache and cookies, reinstalled MM. Thanks for replying!

by **rovingcowboy** » Mon Sep 12, 2005 10:15 am

that might just be an error code coming back at you from their servers, and they use the number to tell you your computer failed to connect to their server because of bandwidth overload by heavy use from everyone all at once.?

i don't think it is media monkey.

by **pl5bnsf** » Mon Sep 12, 2005 1:49 am

I get this message when I Auto-Tag from Amazon:

"Couldn't show results: Socket Error # 10057 Socket is not connected."

If I keep clicking Search enough times I do get back results sometimes.

Also, when I do choose a match, I see the large cover image in the search window but the small cover image is saved in the MP3 tag.

Anybody else have this problem and hopefully a solution?????

Socket Error # 10057

Post a reply

Expand view Topic review: Socket Error # 10057

Socket Error # 10057