ezscan socket error #11001

[Mikejo]

I'm at that point as well BUT I figure when they fix the socket error down the road, then thats when I'll update the rest within EZ-Scan. FYI, the newest database as of yesterday is "881" not the two typo's referenced as 781. Yeah, I'll look forward to the 'Plug-N-Play' EZ-Scan down the road for sure...


.

Hi there, the way I update the data on my scanner after I’ve installed the latest database update is by using this procedure below.

Using the easy scan program do this:

1) Go to the file tab and in the drop-down list you’ll see “Open V scanner folder“, click on that.

In the list, select the V scanner folder that you want to update; Click on it to highlight it, and then click “select”, and it will open it up.

2.) On the row of tabs click on the “library import“ tab.

You can now select, preferred, by city, by county, by ZIP Code (I believe you could even just leave it as “select type”) and click on the button “update channels”

3.) On the “library import” page that opens, you can check off whichever checkboxes you want and then below that click on the “update channels” button. and now you can watch it go through updating, you can see what gets updated and what gets skipped.

Do this for every “V-Scanner Folder” you wish to update.

I know this is a pain, but that’s how I update mine using the easy scan program.

You can do the same-similar thing on the scanner by drilling down to open V-Card, and then scrolling to update objects and it’ll do it in the scanner. I may not have given you the exact instructions to do it on the scanner itself, but it’s kind of a similar process.

 

[kruser]

The only thing I haven't been able to figure out is after the manual update to EZ Scan, I can't figure out how to apply the changes in update 781 to the data I've programmed in EZ Scan for my scanner.

I think you can do this from the Library Import tab in EZ-Scan.
After you open the Library Import tab, look near the bottom and you should see a Update Channels box you can click in the Channel Update part of that window. I'm pretty sure this is what you're looking for.
This option normally runs after you do a successful DB update online but it does not run when you manually update the DB files.

 

[joec157]

I use the "Update from Library" on the scanner and it updates the user data if any. Works every time.

 

[N2SCV]

Hiya, it's happening now for both my radios.

 

[MWS]

New Error Code getting on my TRX-1

 

[w0nwa]

Hiya, it's happening now for both my radios.

Been like this for 2 weeks now. Whistler says it is there issue by phone but e-mail about this keep referring to their download page which is crazy as the current version of EZ scan is the same on the download page. I sent an E-mal today with no response yet asking when they expect this to be fixed.

 

[w0nwa]

Hiya, it's happening now for both my radios.

Also was doing error code 10060 for a few days then switched to error code 11001

 

[w0nwa]

Same error here. I thought it was my connection to the scanner at first so glad it's not just me. Hope it's just a temporary technical glitch.

I E-mailed Whistler awhile back and They kind of pushed it off on me telling me to check the download files. Same version on DL files I have already. I called them they admit it is their problem. I did E-mail them today to see if they have any expected time frame for it to get fixed. No response yet.

 

[w0nwa]

You think Whistler would update us. Or would have made an announcement that the service was down etc.

 

[w0nwa]

I use the "Update from Library" on the scanner, and it updates the user data if any. Works every time.

Not the same. doing that your just copying from the file area on EZscan to the radio.
all internal not over the internet updates

 

[w0nwa]

New Error Code getting on my TRX-1

Welcome to the club. Whistler knows about this it is on their side. but of course, no updates

 

[RaleighGuy]

This is the fourth thread on the same topic, guys if you read the first thread you'll see a fix, but instead people just keep starting new threads.

WS1080: - Whistler weekly Database Updates

Are the Whistler database updates still being created every week? Have they been moved to someplace else? Every time I go to EZ Scan for a database update it tells me I already have the latest version. It has been 2 to 3 weeks now.

forums.radioreference.com

 

[w0nwa]

This is the fourth thread on the same topic, guys if you read the first thread you'll see a fix, but instead people just keep starting new threads.

WS1080: - Whistler weekly Database Updates

Are the Whistler database updates still being created every week? Have they been moved to someplace else? Every time I go to EZ Scan for a database update it tells me I already have the latest version. It has been 2 to 3 weeks now.

forums.radioreference.com

This this is the only thread. dated back to 2023.

ezscan socket error #11001​

• Thread starterWackyracer
• Start dateJun 5, 2023
• TagsNone

 

[CycleSycho]

This this is the only thread. dated back to 2023.

ezscan socket error #11001​

• Thread starterWackyracer
• Start dateJun 5, 2023
• TagsNone

Seems someone REMOVED the latest link (as posted in # 92 and others)? WTH is going on with RR and the removal of the latest thread on this topic? Were all of these latest topics removed as well? IF they are removed, were they MERGED into THIS old topic? If so, shouldn't the original topic have been just locked and noted to refer to this post from 2023?

IF (seems to me) the reasoning for the latest posts is because Whistler is winding down (which it seems no-one can determine as of late), then maybe the latest posts should be left alone? I do know some of the posts were redirected/added to the one that is now gone, shouldn't those posted topics have been just locked and not removed? And finally, where is the records of these posts that seem to have been removed?

Inquiring mind(s) want to know (at least my inquiring mind).


.

 

[w0nwa]

OK, I've taken this up and just sent Mr. Hopkins an email asking for honest clarity on this issue, included a link to this discussion, and also offered my extensive network engineering experience for free to resolve the issue, if in fact this is a network issue (I'm now leaning toward the service has been deprecated in anticipation of something larger, but we'll see...it doesn't take a week to resolve a socket/server service issue, it takes hours at most).

Thanks for the lead. I'm not going to post my email to Mr. Hopkins here as of yet out of respect, and to give him an appropriate yet measured time to respond to it either in a reply, or in a post here. Either way, I will of course share my results with you all here if/when I receive a response.

Fingers crossed, now we wait....

Hello well into July any response from him yet?

 

[trp2525]

FYI the Radio Reference Database File 882 (dated yesterday June 11, 2024) for Whistler Scanners is now posted on the Whistler website (with instructions on how to do a manual update): Manual Library Update

 

[trp2525]

My post #96 above should have showed the date for the Whistler RR 882 database as July 11, 2024. I noticed the error after the window to edit my original post had closed.

 

[w0nwa]

If Whistler went to the hassle of posting in the download file the current updates you would think they would use that time to fix the update issue. I am thinking there might be a problem with the agreement between Whistler and Radio Ref.

 

[Machria]

Wow, just went to do an update (haven't done one in a while) and hit this error.

Still no solution other than something manual?

 

[buddrousa]

It has been over a month.