I've just installed SOS on a W2K3 server, accessing a sourcesafe database on another server.
The SOS service is using a domain user which is a member of a group that has modify permissions on the sourcesafe folder. When I log on to a PC with that user, everything works as expected.
The SOS service won't start, and the event log has this message:
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)
There is no log.txt in the SOS folder.
I use version 4.0.2.171 of the SOS service.
I have version 6.0.93.50 of SSAPI.DLL on the server.
Can't start SOS service
Moderator: SourceGear
I turned on verbose logging and method logging, but it still didn't produce a log file.
So that made me think that the service can't log on as the user. Switching to the domain admin (!) started the service correctly, so it's my other user that doesn't work. So problems solved for now.
But that leads me to another question:
What requirements are there for the service user? I created a domain account and gave it membership to the group that access source safe. Is there any other specific permission the user needs?
So that made me think that the service can't log on as the user. Switching to the domain admin (!) started the service correctly, so it's my other user that doesn't work. So problems solved for now.
But that leads me to another question:
What requirements are there for the service user? I created a domain account and gave it membership to the group that access source safe. Is there any other specific permission the user needs?