WINSOCK ERRORS 10093, 10004, 997, 10038
Posted 29 June 2007 - 04:53 PM
"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)."
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?
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.
Posted 29 June 2007 - 08:33 PM
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.
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.
Posted 02 July 2007 - 01:16 PM
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...
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users