SourceOffSite 4.2 on Windows 2008 Server

mmatson · Post by **mmatson** » Wed Mar 19, 2008 2:40 am

Hi,
Does SourceOffSite 4.2 work on Windows 2008 Server? When I try and start the service I get the following error even though a valid SS ini file is configured.

18/03/2008 18:35:35 - SourceOffSite Server 4.2 Professional - With Cryptography

18/03/2008 18:35:35 - CurrentCulture is en-GB.

18/03/2008 18:35:37 - Server Information
18/03/2008 18:35:37 - Operating System: Microsoft® Windows Server® 2008 Standard
18/03/2008 18:35:37 - Service Pack: 1.0
18/03/2008 18:35:37 - OS Version: 6.0.6001
18/03/2008 18:35:37 - Locale: Ox0809
18/03/2008 18:35:37 - OSLanguage: 1033
18/03/2008 18:35:37 - Total Physical Memory: 4 GB
18/03/2008 18:35:37 - Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
18/03/2008 18:35:37 -
18/03/2008 18:35:37 - SSAPI.dll Information:
18/03/2008 18:35:37 - Location: file:///C:/Program Files (x86)/SourceOffSite Server/Interop.SourceSafeTypeLib.DLL
18/03/2008 18:35:37 - DisplayName: Interop.SourceSafeTypeLib, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null
18/03/2008 18:35:37 -
18/03/2008 18:35:37 - Started at 18/03/2008 18:35:37

18/03/2008 18:35:37 - General logging level is Error. Method logging is Disabled.

18/03/2008 18:35:37 - Number of licenses configured: 10
18/03/2008 18:35:37 - Invalid SourceSafe Initialization file
18/03/2008 18:35:37 - Invalid or no databases to support.
18/03/2008 18:35:37 - Error starting up server. Stopping now....

Regards

Mike

Post by **jclausius** » Wed Mar 19, 2008 8:23 am

We haven't tested SourceOffSite 4.2 with Windows Server 2008.

In theory, since the SOS Server is a .NET based application it should just work. We will have more support information for Windows Server in the upcoming weeks.

In the meantime, the error "Invalid SourceSafe Initialization file" is logged when the path to the VSS database does not end in "srcsafe.ini". The full path to that file including the file name must be used within the SOS Server setup.

mmatson · Post by **mmatson** » Tue Mar 25, 2008 4:05 am

Thanks for the reply. I can confirm that the full path is being entered in the database settings including the srsafe.ini part.
Regards

Mike

Post by **jclausius** » Tue Mar 25, 2008 7:47 am

Is it possible there are multiple files (SOS Server is reading one file and the SOS Server Manager is reading/writing another)?

The lookup in the server is similar to the following:

Code: Select all

if (strDatabase.ToLower().EndsWith("srcsafe.ini") == false)
{
	Log.Message("Invalid SourceSafe Initialization file " + strDatabase);
	return false;
}

In your log, the value for strDatabase is completely missing.

Do you have multiple "sossvr.prp" files? Or could there be some sort of permissions problem with Win 2008 Server that the SOS Service cannot read the file?

mmatson · Post by **mmatson** » Thu Mar 27, 2008 7:26 am

You are right. I did a search for the sossvr.prp file and it existed in both the default install location (c:\program files (x86)\SourceOffSite Server) and this location - c:\users\mmatson\appdata\local\VirtualStore\Program Files (x86)\SourceOffSite Server. It seems that when the file is saved by server manager it is saved into this user based location - I guess this is a security feature of 2008 (note I was a domain admin when doing this). I copied the file from the user based location back into the default location and the service started up fine.

To be able to connect via the client I had to add a new inbound rule to Windows Firewall with Advanced Security to allow the the service to accept connections.

Post by **jclausius** » Thu Mar 27, 2008 7:35 am

Thanks for the report and work-around. I'll log this down to see if we can find a better solution.

Thanks again.