Microsoft KB Archive/142763

= PRB: Path Problems on Client Installation of SourceSafe =

Article ID: 142763

Article Last Modified on 5/4/2001

-

APPLIES TO


 * Microsoft Visual SourceSafe 5.0 Standard Edition
 * Microsoft Visual SourceSafe 6.0 Standard Edition
 * Microsoft Visual SourceSafe 4.0 Standard Edition
 * Microsoft Visual SourceSafe 4.0 Standard Edition

-



This article was previously published under Q142763



SYMPTOMS
It may appear that certain configurable items are not working properly.



CAUSE
The Srcsafe.ini file contains a reference to a local drive when the network address is the intended entry.



RESOLUTION
The path to the shadow directory should be made using Universal Naming Conventions (UNC) to prevent confusion when using Visual SourceSafe from another computer located on the network. If, for example, the shadow directory is set via the SSADMIN program on the server to D:\ssafe\shadow on the server's local D drive, each workstation will attempt to locate its own D:\ssafe\shadow directory, which may not exist. Changing the path to the correct UNC (for example \\myserver\myshare\shadow) will work correctly from the server and all workstations.

NOTE: This problem and resolution also applies to the Journal file setting.



STATUS
This behavior is by design.



Steps to Reproduce Behavior

 * 1) From a computer that is being used as a network location for the Visual SourceSafe data, use the Ssadmin.exe program.
 * 2) On the Tools menu, click Options, and then click Shadow Directories. Set the project to Shadow to $/ and select a directory by using the Browse button.

