SOS service has to be stopped and restarted after rebooting

[aokun]

I started having an issue after upgrading to SOS 4.2. Every time my server computer is restarted the SOS 4.2 clients cannot connect to the server. The server log shows following message:

6/13/2007 10:27:49 AM - Waiting for a connection....secure = True
6/13/2007 11:11:30 AM - Connection accepted from 192.168.1.1:1125 on local address 192.168.1.102:10661, session id is 1.
6/13/2007 11:11:35 AM - 1: Unable to get hostname from address: 192.168.1.1
6/13/2007 11:11:35 AM - 1: Exception during Login: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80070006.
6/13/2007 11:11:35 AM - 1: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80070006.

What I do next is stop SourceOffSite 4 Service which throws System.ObjectDisposedException from sosservice.exe. I then start the service again after which everything works fine.

Any ideas on what might be causing this? This is on a Windows XP Pro computer.

One thing that I noticed is that on first reboot the 'Server Information' in the log file is missing all the information:

6/13/2007 10:26:48 AM - ****************************************************
6/13/2007 10:26:48 AM - SourceOffSite Server 4.2 Professional - With Cryptography

6/13/2007 10:26:48 AM - CurrentCulture is en-US.

6/13/2007 10:27:49 AM - Server Information
6/13/2007 10:27:49 AM - No Operating System information is avaiable
6/13/2007 10:27:49 AM - Total Physical Memory: 2 GB
6/13/2007 10:27:49 AM - Time Zone: (GMT-08:00) Pacific Time (US & Canada)
6/13/2007 10:27:49 AM -
6/13/2007 10:27:49 AM - SSAPI.dll Information:
6/13/2007 10:27:49 AM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
6/13/2007 10:27:49 AM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
6/13/2007 10:27:49 AM -
6/13/2007 10:27:49 AM - Started at 6/13/2007 10:27:49 AM

When I restart the information is present:

6/13/2007 11:25:22 AM - ****************************************************
6/13/2007 11:25:22 AM - SourceOffSite Server 4.2 Professional - With Cryptography

6/13/2007 11:25:22 AM - CurrentCulture is en-US.

6/13/2007 11:25:22 AM - Server Information
6/13/2007 11:25:22 AM - Operating System: Microsoft Windows XP Professional
6/13/2007 11:25:22 AM - Service Pack: 2.0
6/13/2007 11:25:22 AM - OS Version: 5.1.2600
6/13/2007 11:25:22 AM - Locale: Ox0409
6/13/2007 11:25:22 AM - OSLanguage: 1033
6/13/2007 11:25:22 AM - Total Physical Memory: 2 GB
6/13/2007 11:25:22 AM - Time Zone: (GMT-08:00) Pacific Time (US & Canada)
6/13/2007 11:25:22 AM -
6/13/2007 11:25:22 AM - SSAPI.dll Information:
6/13/2007 11:25:22 AM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
6/13/2007 11:25:22 AM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
6/13/2007 11:25:22 AM -
6/13/2007 11:25:22 AM - Started at 6/13/2007 11:25:22 AM


Thank you
Alex

[Beth]

The error you are receiving usually points to a problem with the VSS Automation component. All I can think of initially is that maybe it's not accessible at the point SOS tries to start. On the service properties of SOS, if you go to the recovery tab for when the start fails, you can set it to try and restart again after a minute, or however long it takes the server to come up, and see if that takes care of it.

[aokun]

That didn't help since the service was not crashing. It was just throwing exception during login and continuing to run.

Here is what I tried. If I set the startup service to Manual and start it after everything is running it starts right up without any issues.

A Microsoft article suggested making a dependence on a 'late loading service such as Spooler' to delay loading of a service. I did that and I am still having same issue.

Any other ideas? If you can't reproduce the problem maybe you can try making other services depended on SourceSafe to make it load sooner.

Thanks
Alex

[Beth]

It seems strange that it is just particular about 'when' it starts up. But the error technically points to a problem with the automation component, which I guess, if VSS isn't fully running properly yet while the computer is booting, makes sense.

How long of a delay did you put on the spooler for start up? What happens if you put a really long delay on there? Can it get it started if it waits long enough? I'm sort of curious if it can start that service on it's own if given enough time.

[Beth]

Here's another thing to check. Can you go to your SOS temp directory and see if it's cleaning up the files there? One way to see is to restart SOS (when everyone is logged off) and then go to it and see if it's empty? If there's a lot of connections sitting there, then those could be getting in the way.

[aokun]

I don't think there is a way to put a specific delay on when to start a service. I was only able to make it dependant on other services. The recommended 'long delay' services are Spooler and Messenger. In both cases I am getting same error.

The temp directory is getting cleaned up fully upon service termination.

Here is what worked for me. I installed Windows Server 2003 Resource Kit from here:
http://www.microsoft.com/downloads/deta ... laylang=en

I then installed Autoexnt service as described here:
http://support.microsoft.com/kb/q243486/

I created an autoexnt.bat file with following contents:
C:\Program Files\Windows Resource Kits\Tools\sleep 300
C:\Windows\System32\net start sossvrsvc.net

This starts up sos correctly. Basically it waits 5 minutes from startup which works on my system.

Not sure what is causing all this but since it looks like an isolated problem it might be a good workaround.
Alex

[Beth]

Thanks for the follow up. Sounds good to me.