R
Robot Archive
Hi all,
slightly odd problem we've discovered. We have an applicaiton running on two servers (one 2008R2, one 2012R2). When we stop the service for the application, Windows take an age to shut it down and we see this error in the event viewer:
Closing a TCP socket with local port number 1234 in process 1234 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
Once the service has stopped we use Netstat to check the Ports in use but 1234 does not show up. This would, i think, make sense since by stopping the service and ending the process, Windows should free the port up.
However, when we try and start the applicaiton back up we get this error message: "Could not bind socket. Address and port are already in use." A reboot sorts it out but that's not much of a long term fix. Can anyone explain how a port can be in use/occupied somehow and yet not show up in Netstat?
Any help would be greatly appreciated.
Continue reading...
slightly odd problem we've discovered. We have an applicaiton running on two servers (one 2008R2, one 2012R2). When we stop the service for the application, Windows take an age to shut it down and we see this error in the event viewer:
Closing a TCP socket with local port number 1234 in process 1234 is taking longer than expected. The local port number may not be available until the close operation is completed. This happens typically due to misbehaving network drivers. Ensure latest updates are installed for Windows and any third-party networking software including NIC drivers, firewalls, or other security products.
Once the service has stopped we use Netstat to check the Ports in use but 1234 does not show up. This would, i think, make sense since by stopping the service and ending the process, Windows should free the port up.
However, when we try and start the applicaiton back up we get this error message: "Could not bind socket. Address and port are already in use." A reboot sorts it out but that's not much of a long term fix. Can anyone explain how a port can be in use/occupied somehow and yet not show up in Netstat?
Any help would be greatly appreciated.
Continue reading...