FIX: Admin Cannot See Files with Project Security Enabled

Article translations Article translations
Article ID: 165776 - View products that this article applies to.
This article was previously published under Q165776
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

  1. The SourceSafe Admin does not see any files in a project in the SourceSafe explorer.
  2. The error message: "this command only works on projects" appears when doing various SourceSafe operations.
  3. When assigning rights by project to a parent project, not all subprojects inherit the rights.
  4. When assigning rights by project, or rights assignments to users, you receive the following error: Error writing to file.

CAUSE

The Rights.dat file is corrupted when you assign more than 16 users the rights (by project) to an individual project.

RESOLUTION

To prevent this from happening, do one of the following:
  • Turn off project security. This provides all users global-full or read-only access rights. With project security turned off, you can set read-only access by selecting the Read Only check box on the Users menu under Edit User in the Admin module.
  • Limit user-right settings to 16 or less users per project.
Once the problem occurs, the Rights.dat file has become corrupted and the entire user management and rights system must be rebuilt. Use the following steps to do this:
  1. Make sure that the Visual SourceSafe server and all client installations are upgraded to Visual SourceSafe 5.0 Service Pack 1 or later, or to a later version of Visual SourceSafe.
  2. Rename the Rights.dat file in the VSS\data directory.
  3. Run analyze -f on the data directory.
This will rebuild the Rights.dat file, but there will be no project security information. You will need to run the Visual SourceSafe Admin module and re-create rights by user or by project.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in VisualStudio 97 Service Pack 1.

For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new Visual SourceSafe database.
  2. Add at least 1 project and at least 1 file to that project.
  3. In the Admin program, add 16 users.
  4. Setup the users with any combination of rights (R,RC,RCA,RCAD) to the new project.
  5. At this point, Admin should still have access to the project.
  6. Add the 17th user and give him/her rights as well.
  7. Run SSEXP, login as Admin and try to view the file(s) in the project.

Properties

Article ID: 165776 - Last Review: October 6, 2013 - Revision: 2.1
APPLIES TO
  • Microsoft Visual SourceSafe 5.0 Standard Edition
  • Microsoft Visual Studio 97 Service Pack 3
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbvs97sp1fix KB165776

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com