Source OffSite Server fails to start

[pcteladmin]

Previously this was working fine. We installed .NET1.1 on the server and the following has begun happening.

Using version 4.0.2
If we use the LocalSystem account (which has full access to all directories the server needs). We get the errors:
Could Not Start the SourceOffSite 4 Server service on Local Computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem presists, contact your system administrator.

If we use the Domain Admin we get:
Could Not Start the SourceOffSite 4 Server service on Local Computer.
Error 1069: The Service Did not start due to a logon failure.

Logs show no activity at all.

Manually starting the service causes the same errors as above.

We are completely down at this point, any help would be appreciated.

[lbauer]

Did you have a different version of .NET previously?

Is there any error logged to the Event Viewer regarding SOS Server?
If yes, what is it?

If not, Have you tried uninstalling and re-installing the SOS Server?

[pcteladmin]

> Did you have a different version of .NET previously?
Yes we had 1.0 installed.

> Is there any error logged to the Event Viewer regarding SOS Server?
> If yes, what is it?
Yes, the errors are:
Service cannot be started. System.ArgumentException: Illegal characters in path.
at System.IO.Path.Combine(String path1, String path2)
at ClassicService.Server.Startup(String[] args)
at ClassicService.ClassicService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

>If not, Have you tried uninstalling and re-installing the SOS Server?
Yes, did not help.

I have moved it over to another server (new) temporarily to allow people to continue to work.

[lbauer]

This error is seen on certain operating systems\service packs. There's an easy resolution:

http://support.sourcegear.com/viewtopic.php?t=1987

[schoepel]

We've applied the suggested fix in the registry, but we continue to get the "Illegal characters in path" error. We've even done an iisreset. (SoS Server Version 4.1.)

I've searched other posts, but it seems no one has problems after applying this fix. We've verified the fix changes. Any relevant help is appreciated.

[Guest]

By the way, this is the installation path as it appears for that registry entry, without the double-quotes now:

C:\Program Files\SourceOffSite Server\SosService.exe

[lbauer]

We've even done an iisreset.

SOS doesn't interact with IIS at all.

You might try rebooting the machine, in case the registry edit didn't "take" for some reason.

[schoepel]

After we reboot it, it put the double quotes back again. Did it two times, it does the same thing.

[lbauer]

That's very strange. The changes are not being saved.

Does your user account have permission to write to the registry?

What OS and service pack is SOS installed on? You can check this in Windows 2003 by right clicking on the registry key and selecting Permissions.

[schoepel]

I am in the Administrators group so I guess I should have all the permissions.

The Windows 2003 Server with latest updates (whatever MS sent out )

I changed the registry fine.. Even close the editor and reopen it.. And see the changes there..

[lbauer]

Well, as you said, we haven't had cases where the registry fix didn't work.

We'll have to keep digging.

Is there a log file in the SOS Server directory?

Are you getting any other errors when you try to start the SOS Server service, like Error 1053? Can you restart other services on that machine?

Can you send (email Linda at sourcegear.com)or post a screen shot of your registry entry?

[schoepel]

It seems it WAS a permissions problem, not with the registry, but rather the .ini profile. Here is what my IT guy emailed me (I've been relaying information):

"Here is how I tried to set it up: I installed SoS on my test server which connects to the server with the VSS database. The reason it wouldn't start is because it couldn't use the *.ini on the server and it failed. After give it the full permissions, everything works like a charm.

Do I need to configure the *.ini so that it refers to the local ini instead of the ones on the server? How is the VSS client setup? Does it refer to the *.ini from the server or do you have to have it locally?"

I guess we are still working out the setup, I will try to refer to the manuals unless we meet other roadblocks. Thanks for suggesting the permissions issue!

[lbauer]

Glad you're getting things figured out. Are you referring to the srcsafe.ini file or the user's ss.ini file? The SOS Server needs access to both.

The account used by the SOS Server Service should have read/write access to the VSS database directory where the srcsafe.ini file resides. It also needs access to the SOS Server directory to write the log file.

To see what account you're using, check the Logon As properties of the SOS Server service in the Services Control Panel.