Don, Check your system event log, both application and system, to see if you're hitting your tcp maximum concurrent connection limit.
I am getting this error, immediately after starting window eyes, for some time, and I suspect it's all the scripts I have installed (48?), which are trying to see if there are any updates for themselves. There could be other reasons, but I was just ruling out whether the script was having a problem connecting to the web site. If you don't know how to check your system event log, open the run dialog and type in: eventvwr.msc as the command. This brings up a dialog with 2 list controls: the default one, on the left, is which log you want to look at (it's actually a tree control, and you may have to open some branches before you find logs named "application" and "system"). The tab key takes you to the other control, which really is a list control, which are all the entries in that log. Pressing control-home will take you to the top, and then you can look downward for one that's a "warning" or a "error". Actually, I'm sorry, but I can't remember if this tcp message is definitely a warning or an error, so that means you'll need to open anything that has a time stamp near the time you had the trouble. To open an event just press enter, and you'll get a detailed dialog, with many edit boxes (under vista, really many). One of them has the detailed description; under xp, I remember the access key for it is alt-d. Under vista, I recall it's the first one you come to when you press the tab key. Under vista, the tree control has a lot of entries; the one you want to open is named "windows logs"; under it you should find application and system. hth, Chip0 ------------------------------ Chip Orange Database Administrator Florida Public Service Commission [EMAIL PROTECTED] (850) 413-6314 (Any opinions expressed are solely those of the author and do not necessarily reflect those of the Florida Public Service Commission.) > -----Original Message----- > From: don bishop [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 11, 2008 12:56 AM > To: gw-scripting@gwmicro.com > Subject: bcscan script error > > Anyone else having trouble with bcscan? I can scan and get a > code, but > am also getting an error saying "cannot open socket". I suspect it's > something with the bcscan database, but just wondering if > anyone else is > seeing this also. > > I tried it on two different machines. > > Don > > >
