Service does not start for some existing VSS database

[raviisrani]

Hi

I tried to download your evaluation version and set it up with my existing VSS database but the service does no start. It gives me the following error in the log.
9/13/2004 12:56:49 PM - \\\\bas-208\\VSS\\VSSNEW\\srcsafe.ini does not exist!
9/13/2004 12:56:49 PM - Invalid or no databases to support.

However when I setup a new database on my locale machine and connect the service starts very smoothly

What could be the issue with existing VSS database ( which are on W2K environment)

regards
Ravi

[lbauer]

See this KB article for help:

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

[relay_denied]

Is a copy of the client required on the server as well to allow the server service to connect to the databases? I am having this same issue:

11/19/2004 1:21:08 PM - Number of licenses configured: 10
11/19/2004 1:21:08 PM - D:\\VSS\\Engineering\\srcsafe.ini does not exist!
11/19/2004 1:21:08 PM - D:\\VSS\\W\\srcsafe.ini does not exist!
11/19/2004 1:21:08 PM - Invalid or no databases to support.
11/19/2004 1:21:08 PM - Error starting up server. Stopping now....

And have seen this in another posting:

These error messages indicates that a copy of the Visual SourceSafe Client has not been installed on the SOS Server machine. The VSS client provides the API that the SOS Server needs to communicate with the VSS database.

[lbauer]

Yes, a copy of the Visual SourceSafe client is required on the SOS Server machine. The SOS Server communicates with the VSS database via the SourceSafe Automation Component. The Automation Component is provided by the VSS Client.

However, if there is no automation component, usually the error in the log is different.

These errors:
11/19/2004 1:21:08 PM - D:\\VSS\\Engineering\\srcsafe.ini does not exist!
11/19/2004 1:21:08 PM - D:\\VSS\\W\\srcsafe.ini does not exist!

indicate that the account used by the SOS Server Service doesn't have access to the location of the databases. Is D:\ a mapped drive? If so, try browsing to the location of the srcsafe.ini files in the SOS Server Manager.

Did you try the instructions in this KB article:

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