6 replies to this topic

[zaytsevi]

Any help on these would be greatly appreciated. We have 4 clients that are getting the exact same winsock errors.

[anipirakis]

One place I looked to see the description of 10093 said:

"failed, or--possibly--you are accessing a socket which the current active task does not own (i.e. you're trying to share a socket between tasks)."
http://www.sockets.c...ANOTINITIALISED

Perhaps there is something that is holding onto the default port that Pro-IV uses (23 I believe). Course it could be that a patch was recently installed that is messing with Pro-IV (more likely since Socket share would seem to me to mean the actual Socket object and not the port). What operating system? 2003?

Thanks,

Aleksei

Any help on these would be greatly appreciated. We have 4 clients that are getting the exact same winsock errors.

Edited by anipirakis, 29 June 2007 - 04:55 PM.

[zaytsevi]

Yes 2003. I am the system Tech support for this software and not the developer. If you could explain in more simpler terms as to what you think is happening, id appreciate it.

[anipirakis]

If you have several clients who are experiencing the same issue, and seemed to start having the issue about the same time, I would say that perhaps there was some security update to Windows 2003. I know here, I have the Pro-IV server(we use Glovia) not receive the Windows Update because I know that sometimes Security updates can affect Glovia (remember that some of this software, the server stuff, is OLD really OLD!!!). I had been thinking that it will either be that the port that Pro-IV uses (the TCP-PORT) maybe is being used, or possibly blocked (firewall perhaps?). I believe that the exe you are showing is the server side, am I right that you see these on the server?

I would start here:

1. If this did work at one time, and the suddenly stoped, I would check to see if any new software/updates were installed. If yes, then I would remove said software.

2. If it never worked, I would check the firewall settings. Is firewall running? If it is then I would look in and make sure that port 23 is unblocked (TCP and UDP) --- or whatever port Pro-IV is configured to use.

3. If it is not the above, I would definately get ahold of the software vendor to see if they have any suggestions. By the way, what software are you running in Pro-IV? Which version of Pro-IV (it looks like 4.x but I am not sure about that).

It really REALLY sounds like a windows update, though admitidly I have no idea for any new updates that would break Pro-IV.

Thanks,

Aleksei

Yes 2003. I am the system Tech support for this software and not the developer. If you could explain in more simpler terms as to what you think is happening, id appreciate it.

[zaytsevi]

Yes this was taken directly from the Server. I have attached the Application and the System.evt log files. To open them, open event viewer, click on application, click on action, Open Log file as...

Attached Files

•  Server_Application_Log.zip   0bytes   127 downloads
•  Server_System_Log.zip   0bytes   107 downloads

[anipirakis]

It appears both files are completly empty.

Thanks,

Aleksei

Yes this was taken directly from the Server. I have attached the Application and the System.evt log files. To open them, open event viewer, click on application, click on action, Open Log file as...

[Lewis Mccabe]

Can you please give us more info regarding version of Windows 2003 Server these clients are running? Are they all the same?