"Address in Use"?

Kevin · Post by **Kevin** » Fri Jul 21, 2006 10:07 am

My SOS service suddenly doesn't seem to be able to listen on
port 8888.

I turned on logging and am getting the message "Address In Use" rather
than the usual "Listening for connections on unsecure port 8888".
Any suggestions?

SOS version 3.53
Windows Server 2003
VSS 6.0d

lbauer · Post by **lbauer** » Fri Jul 21, 2006 12:43 pm

This means the port is in use. Either SOS isn't releasing the port or another application is using port 8888.

Kevin · Post by **Kevin** » Mon Apr 30, 2007 3:55 pm

This issue has become chronic. It happens almost every day.
There are no other applications using port 8888, except SOS 3.5.3.
How can I get SOS to release the port after it crashes?
(and why does it crash so often)?

Posted: Fri Jul 21, 2006 10:07 am Post subject: "Address in Use"?

--------------------------------------------------------------------------------

My SOS service suddenly doesn't seem to be able to listen on
port 8888.

I turned on logging and am getting the message "Address In Use" rather
than the usual "Listening for connections on unsecure port 8888".
Any suggestions?

SOS version 3.53
Windows Server 2003
VSS 6.0d

lbauer · Post by **lbauer** » Mon Apr 30, 2007 4:19 pm

If you have VSS 6.0d, you may be experiencing a concurrency crash in the VSS automation component. See this KB article to determine if your version of VSS could be causing the SOS crashes:
http://support.sourcegear.com/viewtopic.php?t=10

Kevin · Post by **Kevin** » Thu May 03, 2007 11:55 am

Yes, I checked and the value is set to 'both'. Any other suggestions? Thanks.

Beth · Post by **Beth** » Thu May 03, 2007 4:01 pm

Can you perform a restart of the SOS service?
How about a reboot of the entire server?

After those two, if it still doesn't work, can you try out a different port? You can go into the SOS server manager to change the port it uses. If it can only connect on a different port, then it's very likely some other application is now using 8888.

Kevin · Post by **Kevin** » Thu May 03, 2007 4:23 pm

We do reboot the server each time this occurs, as restarting the SOS service doesn't free up the port. I'm sure that nothing else is
using the port, as I've checked. Any other suggestions? Kevin