Client can not connect, need to restart services

[bven]

Hello,

I'm new to this forum. We just implemented SOS and VSS in our company. Everything seems to be working fine except for 1 minor problem that we experienced at least once a week. Anytime of the day users will complain that they can not connect to the server and the solution is we just have to restart the services on the server and after that, they can already connect to the server. Although, restarting the services will only take a few seconds but sometimes downtime will take longer because users can not contact IT immediately, especially that we operate in 24 hours.

Appreciate any inputs. Thanks.

[Beth]

Which version of SOS are you on?
Which version of VSS?
What is the exact version number of the VSS automation component that is registered? Instructions for finding that are here: Automation Component Version

[bven]

Thank you very much for a very quick reply. Below are the information you have requested.

SOS Version - 4.2
VSS Version - 6.0D
VSS automation component - 6.0.98.48

Thank you very much.

[Beth]

In the same registry location where you looked up the path to the ssapi.dll, mentioned in the instructions I linked to, what setting do you have set for the Threading Model? 6.0.98.48 works best when it is set to 'Both' instead of 'Apartment'.

Can you either attach or send your SOS server log? The SourceOffSite (SOS) log file (log.txt) is located on the machine where the SOS server resides in this path C:\Program Files\SourceOffSite Server.

Can you look in your event viewer around the time that user's complain and see if any errors are logged? If you see something there, could you save the Application and System logs as .evt's and provide those as well?