Symptoms

You may get the error when you try to connect to SourceAnywhere for VSS Server.

Cause

The current log on user of SourceAnywhere for VSS service may not have read/write permission of the Visual SourceSafe (VSS) directory.

The path to srcsafe.ini is incorrect.

Resolution

Troubleshooting of this problem depends on whether the SourceAnywhere for VSS Server is installed on the same machine where the VSS database resides.

If YES, please verify the following thing:

• The Log On user of SourceAnywhere for VSS service should have read/write permission of the Visual SourceSafe (VSS) directory.

For information about how to check the Log On user of SourceAnywhere for VSS service, please click here.

If NO, please verify the following things:

• If you specify a local user as the Log On user, please verify this username also exists on the machine where Visual SourceSafe (VSS) database resides and the passwords of these two users are identical. Meanwhile, you need to verify the user on the Visual SourceSafe (VSS) machine has read/write permissions and read/change share permissions of the Visual SourceSafe (VSS) directory.
  Please click here for information about how to check Security setting of a Windows folder, and click here to see how to check Share Permissions setting of a Windows folder.
  
  
• If you specify a domain user as the Log On user and SourceAnywhere for VSS Server is installed in the same domain as the one hosting Visual SourceSafe (VSS) database, please verify this domain user has read/write permissions and read/change share permissions of of the Visual SourceSafe (VSS) directory.
  
  
• No mapped driver letter is used to specify the path to srcsafe.ini, since the mapped driver may not be available for SourceAnywhere for VSS service.
  If you map \\ServerName\ShareName to driver Z:, for example, you should use the full network path \\ServerName\ShareName\SuorceSafe\srcsafe.ini to specify the path to srcsafe.ini, rather than Z:\SourceSafe\srcsafe.ini.