We are running two versions of SOS -- 3.5.3 and 4.1.2. Each version runs on a different server and connects to a different Visual SourceSafe 6.0 database. In the case of 3.5.3, the account that runs the service has only Read permissions to the srcsafe.ini file, and everything works fine. When we set up 4.1.2, we again gave the account that runs the service Read permissions to the corresponding srcsafe.ini file. The service failed to start and the logged error was: "Error verifying database path: Access to the path '\\pd1\SCGVSS_DATABASES\NG_VSS6\srcsafe.ini' is denied." We gave that account Write permissions to the file and then everything worked.
My question is why is this the case and is it expected? Our security auditors are telling us that this permission should not be necessary.
srcsafe.ini - permission requirements differ by version?
Moderator: SourceGear
This may be related to newer versions of VSS and the Automation Component because the we've recently had more reports of this error. What version of VSS and the VSS automation component is installed on your SOS Server machine?
Here's how to determine the version:
http://support.sourcegear.com/viewtopic.php?t=1510
SOS does not need direct access to the srcsafe.ini file, but the
VSS Automation component does.
Here's how to determine the version:
http://support.sourcegear.com/viewtopic.php?t=1510
SOS does not need direct access to the srcsafe.ini file, but the
VSS Automation component does.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager