Microsoft KB Archive/240883

= PRB: Shadow Folders Are Not Updated When You Use Mapped Drives =

Article ID: 240883

Article Last Modified on 8/9/2001

-

APPLIES TO


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

-



This article was previously published under Q240883



SYMPTOMS
After you create a shadow folder in Visual SourceSafe (VSS), the following error message occurs when you check in a file:

Invalid dos path to the mapped directory.

The shadow folder is not updated.



CAUSE
Visual SourceSafe attempts to update the shadow folder by referencing it from the SourceSafe client computer. Therefore, all clients must have mapped drives to the shadow folder that are identical.

NOTE: Visual SourceSafe does not issue a warning that all clients must also create a mapped drive in order for this feature to work.



RESOLUTION
To resolve this problem, shadow directly by using the Universal Naming Convention (for example, \\machinename\share). Alternatively, a mapped drive must be created for all individual clients that point to the shadow directory path.



STATUS
This behavior is by design.



Steps to Reproduce This Behavior

 * 1) Map a drive to the location where you intend to create a shadow folder.
 * 2) Open the Visual SourceSafe Administrator, click Tools, click Options, click the Shadow Folder tab, and then create a shadow folder to the mapped drive.
 * 3) Open SourceSafe Explorer on a client computer that does not have a mapped drive.
 * 4) The error occurs when you attempt to check in a file to the project that shadows to the mapped drive.

Additional query words: shadowing UNC

Keywords: kbprb KB240883

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.