SOS version 4.2 needs to be restarted every so often ...

[MitchelT]

Hi:

Not sure what the problem is but we can be chugging along for a few weeks without any problems and them all of a sudden users cannot login to SOS.

I need to stop and restart the service and then it comes back up most of the time, sometimes I have to stop/start the service a second time.

Anyone else experiencing this problem or have any tips? I should point out that there are only 7 user accounts.

This registry fix has also been done:
HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32
Next, find the "ThreadingModel" Key, and set its value to "Both".

Thanks.

Mitch

[Beth]

Are there any errors listed in the SOS server log around the same time that SOS stops working? That is found in the program files directory under SourceOffSite and is called log.txt.

Are there any errors in your Event Viewer logs around the same time?

Are your VSS databases on the same server or a different server?

[MitchelT]

Hi Beth:

One of our developers just reported the problem and this is what we got.

SOS Server Log:

7/14/2009 3:15:45 PM - Connection accepted from 161.38.xxx.xxx:52550 on local address 65.36.xxx.xxx:8081, session id is 20.
7/14/2009 3:15:50 PM - 20: Unable to get hostname from address: 161.38.xxx.xxx
7/14/2009 3:28:33 PM - 7/14/2009 3:28:33 PM - Server Exception (-100): [Socket error - ParseStream(). Received : 0] - CONNECTION CLOSED
7/14/2009 3:28:33 PM - 20: Connection Closed: CONNECTION CLOSED
7/14/2009 3:28:33 PM - Killing disconnected or idle client 161.38.xxx.xxx- (161.38.xxx.xxx)
7/14/2009 3:28:33 PM - 9: Exception: A blocking operation was interrupted by a call to WSACancelBlockingCall

Event Viewer: Did not show anything related to SOS

VSS Databases: Yes, they are on the same server

Thank you for looking into this.

Mitch

[Beth]

Which VSS Automation Component Version are you using? (Instructions for finding that are in the link.)

Do you have any anti-virus on the on the SOS server that could be occassionally scanning files SOS needs?

Do any firewalls or routers possibly resetting their ports? The connection must be persistent for SOS.

[MitchelT]

Beth:

Here is the information you requested:

VSS Automation Component Version: 6.0.98.48

We have Symantec AntiVirus running on the server but we configured it to not scan the folder that has all of the Visual Source Safe files, C:\Program Files\SourceOffSite and C:\Program Files\SourceOffSite Server.

I contacted the server engineers and they told me that there should not be anything resetting the port connections on the firewall.

One of our coders mentioned that he sometimes notices a problem connecting to SOS when he has multiple instances of MS Visual Studio running.

Thanks,

Mitch

[Beth]

One of our coders mentioned that he sometimes notices a problem connecting to SOS when he has multiple instances of MS Visual Studio running.

Most of our users can't use multiple instances of SOS at the same time. All instances have the potential to be trying to access the cache file at the same time, or to be trying to communicate through the same port at the same time. This shouldn't require recycling the server though, and it's probably not related to the initial issue you posted.

On the anti-virus, could you also have it not scan the SOS folder? You might set a time to try a test with it not scanning at all as well. That way we can at least see if that has an effect and can rule it out.

Do you have an SOS client loaded on the server? If so, does that ever run into a time where it can't connect using localhost?

[MitchelT]

On the anti-virus, could you also have it not scan the SOS folder? You might set a time to try a test with it not scanning at all as well. That way we can at least see if that has an effect and can rule it out.

Do you have an SOS client loaded on the server? If so, does that ever run into a time where it can't connect using localhost?

We are not scanning these folders:
- C:\Program Files\SourceOffSite
- C:\Program Files\SourceOffSite Server
- Folder that has the VSS files

Not sure which "SOS Folder" you mean?

We pretty much never run the client on the server, I think we ran it once in the past few years.

Thanks,

Mitch

[Beth]

Could you look in your Event Viewer logs for any errors or warnings that happen around the same time that users can't connect?

The next time users can't connect, I'd like you to try out the client right on the server and use localhost for the server connection instead of an IP address or server name. If it can or can't connect, let me know. You might also try telnetting to the server and port a few different ways to see if the port responds to anything.