Microsoft KB Archive/308896

= PRB: [SSAFE] - File Access Error on Ss.ini When Remotely Accessing Database in the Default Installation Location =

Article ID: 308896

Article Last Modified on 2/23/2007

-

APPLIES TO

 Microsoft Visual SourceSafe 6.0C, when used with:  Microsoft Visual Studio .NET 2002 Professional Edition

 Microsoft Visual Studio .NET 2002 Enterprise Architect

 Microsoft Visual Studio .NET 2002 Enterprise Developer  Microsoft Visual SourceSafe 6.0 Standard Edition</li></ul>

-

<div class="notice_section">

This article was previously published under Q308896

<div class="symptoms_section">

SYMPTOMS
When you access a Visual SourceSafe database from a remote (client) computer, various errors may be returned indicating there are insufficient permissions to the SS.ini file. For example:

Access to the file &quot;\\MachineA\vss\users\user1\ss.ini&quot; denied

<div class="cause_section">

CAUSE
By default, on Windows 2000 members of the Users group are not given write or modify permissions to folders in the Program Files tree. This is what causes the problem.

<div class="resolution_section">

RESOLUTION
To resolve this issue, do not install the Visual SourceSafe database to the default location (the Program Files folder), because it is inherited permissions from this folder that cause the problem.

<div class="status_section">

STATUS
This behavior is by design.

<div class="moreinformation_section">

Steps to Reproduce Behavior
<ol> Install Visual SourceSafe on one computer (for example, MachineA). Let it create a database at the standard install location (C:\Program Files\Microsoft Visual Studio\VSS).</li> Create a share at the database install directory (C:\Program Files\Microsoft Visual Studio\VSS in this example) named VSS. Add a user ( User1 ) to the Visual SourceSafe database who is not a member of MachineA's Administrators or Power Users group, but is a member of the Users group. (By default domain users will be members of the local computer's Users group).</li> On another (remote) computer that has the Visual SourceSafe client installed, log on as User1. Connect to the Visual SourceSafe database on MachineA by using the client in the development tool of your choice or the Visual SourceSafe Explorer.

Note that various errors are returned when you attempt to access the SourceSafe database in this scenario. For example:

Unable to open user login file path to ..data\loggedin\VSSusername.log

</li> On MachineA open the Properties dialog box for C:\Program Files\Microsoft Visual Studio\VSS. Look at the Security tab and note that the Users group has read, list folder contents, and read & execute Permissions. Give the Users group write permission. (Note that these are operating system file permissions, NOT share permissions.)</li> Next, open the database from the remote computer. Now you can access Visual SourceSafe, but when you close the database you will get:

Access to the file &quot;\\MachineA\vss\users\user1\ss.ini&quot; denied

</li> Go back to MachineA and give the Users group modify permission (allows files to be deleted).</li> Note that User1 can now access the database from remote computers.</li></ol>

<div class="references_section">