Local System account can't be used to start the SOS service?

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 12:24 pm

Can't the Local System account be used to start the SOS service? This used to work but after applying an upgrade now only a VSS administrator's account can be used to start the service.

When we use the Local System account we get this error:

The SourceOffSite 4 Server service on Local computer started and then stopped . Some services stop automatically if they have no work to do, for example, Performance Logs and Alerts service".

Thanks,
Karin

Beth · Post by **Beth** » Wed Feb 20, 2008 1:10 pm

Where is your VSS database located? Is that on the same or different machine?

Which update did you install?

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 1:19 pm

It is on another server.

We updated SOS 4.0 to 4.2.

Here is the error from the Event Log:

Service cannot be started. System.Exception: Error starting the 'SOS 4' server. Please check the server log for more details.
at ClassicService.ClassicService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

Here is the event log when a the local system account is used:

2/20/2008 1:13:33 PM - ****************************************************
2/20/2008 1:13:33 PM - SourceOffSite Server 4.2 Professional - With Cryptography

2/20/2008 1:13:33 PM - CurrentCulture is en-US.

2/20/2008 1:13:33 PM - Server Information
2/20/2008 1:13:33 PM - Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
2/20/2008 1:13:33 PM - Service Pack: 2.0
2/20/2008 1:13:33 PM - OS Version: 5.2.3790
2/20/2008 1:13:33 PM - Locale: Ox0409
2/20/2008 1:13:33 PM - OSLanguage: 1033
2/20/2008 1:13:33 PM - Total Physical Memory: 1023.47 MB
2/20/2008 1:13:33 PM - Time Zone: (GMT-06:00) Central Time (US & Canada)
2/20/2008 1:13:33 PM -
2/20/2008 1:13:33 PM - SSAPI.dll Information:
2/20/2008 1:13:33 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
2/20/2008 1:13:33 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
2/20/2008 1:13:33 PM -
2/20/2008 1:13:33 PM - Started at 2/20/2008 1:13:33 PM

2/20/2008 1:13:33 PM - General logging level is Error. Method logging is Disabled.

2/20/2008 1:13:33 PM - Number of licenses configured: 10
2/20/2008 1:13:34 PM - \\\\gvw0032\\finrefitdcc-ss$\\srcsafe.ini does not exist!
2/20/2008 1:13:34 PM - Invalid or no databases to support.
2/20/2008 1:13:34 PM - Error starting up server. Stopping now....
2/20/2008 1:16:05 PM -

And here are the entries when a VSS administrator's account is used:

****************************************************
2/20/2008 1:16:05 PM - SourceOffSite Server 4.2 Professional - With Cryptography

2/20/2008 1:16:05 PM - CurrentCulture is en-US.

2/20/2008 1:16:05 PM - Server Information
2/20/2008 1:16:05 PM - Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
2/20/2008 1:16:05 PM - Service Pack: 2.0
2/20/2008 1:16:05 PM - OS Version: 5.2.3790
2/20/2008 1:16:05 PM - Locale: Ox0409
2/20/2008 1:16:05 PM - OSLanguage: 1033
2/20/2008 1:16:05 PM - Total Physical Memory: 1023.47 MB
2/20/2008 1:16:05 PM - Time Zone: (GMT-06:00) Central Time (US & Canada)
2/20/2008 1:16:05 PM -
2/20/2008 1:16:05 PM - SSAPI.dll Information:
2/20/2008 1:16:05 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
2/20/2008 1:16:05 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
2/20/2008 1:16:05 PM -
2/20/2008 1:16:05 PM - Started at 2/20/2008 1:16:05 PM

2/20/2008 1:16:05 PM - General logging level is Error. Method logging is Disabled.

2/20/2008 1:16:05 PM - Number of licenses configured: 10
2/20/2008 1:16:05 PM - SourceSafe Initialization file(s) located at:
2/20/2008 1:16:05 PM - \\gvw0032\finrefitdcc-ss$\srcsafe.ini

2/20/2008 1:16:05 PM - polaris-server is attempting to listen for connections on secure port 8081
2/20/2008 1:16:05 PM - polaris-server is attempting to listen for connections on unsecure port 8080

2/20/2008 1:16:05 PM - Waiting for a connection....secure = True
2/20/2008 1:16:05 PM - Waiting for a connection....secure = False

As you can see it appears to be putting additional back-slashes in when a local system account is used, and yet I didn't change any settings between each attempt.

Thanks,
Karin

Post by **jclausius** » Wed Feb 20, 2008 1:43 pm

A Local System account will not have access to any network resources.

From the looks of your log file, a VSS database exists over a network share (\\gvw0032\). For this reason, an account with access to network resources must be used for SourceOffSite.

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 1:51 pm

That's weird because it used to work in version 4.0!

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 1:53 pm

Also, that doesn't explain why a non-VSS user can't be used to start the service. Another user has VSS access to that database, but is not a VSS administrators. That person also gets the same error!

Here is the error when a non-VSS Administrator starts uses their credentials to start the service:

2/20/2008 1:55:53 PM - ****************************************************
2/20/2008 1:55:53 PM - SourceOffSite Server 4.2 Professional - With Cryptography

2/20/2008 1:55:53 PM - CurrentCulture is en-US.

2/20/2008 1:55:53 PM - Server Information
2/20/2008 1:55:53 PM - Operating System: Microsoft(R) Windows(R) Server 2003, Enterprise Edition
2/20/2008 1:55:53 PM - Service Pack: 2.0
2/20/2008 1:55:53 PM - OS Version: 5.2.3790
2/20/2008 1:55:53 PM - Locale: Ox0409
2/20/2008 1:55:53 PM - OSLanguage: 1033
2/20/2008 1:55:53 PM - Total Physical Memory: 1023.47 MB
2/20/2008 1:55:53 PM - Time Zone: (GMT-06:00) Central Time (US & Canada)
2/20/2008 1:55:53 PM -
2/20/2008 1:55:53 PM - SSAPI.dll Information:
2/20/2008 1:55:53 PM - Location: file:///C:/Program Files/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
2/20/2008 1:55:53 PM - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
2/20/2008 1:55:53 PM -
2/20/2008 1:55:53 PM - Started at 2/20/2008 1:55:53 PM

2/20/2008 1:55:53 PM - General logging level is Error. Method logging is Disabled.

2/20/2008 1:55:53 PM - Number of licenses configured: 10
2/20/2008 1:55:53 PM - Error verifying database path: Access to the path '\\gvw0032\finrefitdcc-ss$\srcsafe.ini' is denied.
2/20/2008 1:55:53 PM - Invalid or no databases to support.
2/20/2008 1:55:53 PM - Error starting up server. Stopping now....

This user has access to the VSS database from the normal VSS GUI.

Thanks,
Karin

Post by **jclausius** » Wed Feb 20, 2008 2:15 pm

kewlgeek wrote:That's weird because it used to work in version 4.0!

That is weird. Did something modify your "local system" configuration?

AFAIK, services without a Windows domain, user account, or password attempting to use a network resource are denied because they have no useful credentials.

Post by **jclausius** » Wed Feb 20, 2008 2:17 pm

kewlgeek wrote:Also, that doesn't explain why a non-VSS user can't be used to start the service. Another user has VSS access to that database, but is not a VSS administrators. That person also gets the same error!

Is it possible permissions changed on the share itself or on the share's folder security rights?

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 2:19 pm

Looks like our replies crossed. See my subsequent reply about another VSS user who has network access but is not a VSS Administrator using their credentials to start the service. That user has access to that network path and the VSS GUI works fine for them, but again they get the same error. Only the VSS Admin can start the service, but that gives every SOS user the ability to purge files, which we obviously do not want to allow.

Thanks,
Karin

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 2:20 pm

That user can access the share path just fine, no problems.

Post by **jclausius** » Wed Feb 20, 2008 2:20 pm

Also, is there an entry in the Windows Event Viewer regarding any kind of error?

Perhaps it would shed some light on why things are not working in your configuration.

Post by **jclausius** » Wed Feb 20, 2008 2:25 pm

I'm going to seek additional expertise.

kewlgeek · Post by **kewlgeek** » Wed Feb 20, 2008 2:53 pm

[quote]Also, is there an entry in the Windows Event Viewer regarding any kind of error?

Perhaps it would shed some light on why things are not working in your configuration.[/quote]

The error in the event log is this one:

Service cannot be started. System.Exception: Error starting the 'SOS 4' server. Please check the server log for more details.
at ClassicService.ClassicService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

lbauer · Post by **lbauer** » Wed Feb 20, 2008 4:46 pm

If you use a Domain Admin account, does the SOS Server service start?

kewlgeek · Post by **kewlgeek** » Thu Feb 21, 2008 6:54 am

The SOS service account starts if I use an account for a VSS admin (someone who can purge files in VSS, not just check-in, check-out, and delete files). I haven't tried a domain admin because those are not accounts that they (our system administrators) are ever going to give to us.

Thanks,
Karin