Microsoft KB Archive/158471

= PRB: 'File not found' When Attempting Command Line Check In =

Article ID: 158471

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
 * Microsoft Visual SourceSafe 4.0a
 * Microsoft Visual SourceSafe 4.0a

-



This article was previously published under Q158471



SYMPTOMS
When you check in files from the Command Line, you may receive the message:

File " " not found

where is the name of the file you want to check in. This message appears if the following four conditions exist:

 You changed the working directory for the file prior to checking it out. You did not close the Visual SourceSafe Explorer after changing the working directory.  As indicated in your Ss.ini file, your current SourceSafe project is set to the wrong project, not the project that you are attempting to check it into. This setting is saved as: ; Your current SourceSafe project. Project =   The FORCE_DIR entry in your Ss.ini file is set to NO.



CAUSE
When checking in a file, the Visual SourceSafe Command Line examines your Ss.ini file to determine the working directory for a given project. When you change the working directory in the Visual SourceSafe Explorer, the change is cached in memory until the Visual SourceSafe Explorer is closed. This means that the Ss.ini will not be updated until you close Visual SourceSafe. Consequently, if you change a file's working directory and then check it out, the Visual SourceSafe Explorer sees the updated working directory but the Command Line does not.



RESOLUTION
- Check in the file using the Visual SourceSafe Explorer.


 * If you change the working directory and intend to use any Command Line functions, close and restart the Visual SourceSafe Explorer.



STATUS
This behavior is by design.

<div class="moreinformation_section">

Steps to Reproduce Behavior
 Open your Ss.ini file and verify that the setting FORCE_DIR=NO is present. (If it is not, set it to FORCE_DIR=NO.)</li> Open or switch to Visual SourceSafe Explorer.</li> Select any project and set its working directory to "C:\Test". (If the directory doesn't exist, create it.)</li> Activate $/ as the current project by double-clicking it. Close and restart Visual SourceSafe Explorer.</li> Select the project from step 3 and reset its working directory to "C:\Test2". (If the directory doesn't exist, create it.)</li> Check out a file from the project. It will be checked out to C:\Test2.</li> Minimize Visual SourceSafe and Open a DOS Box. If you are running on a 32-bit operating system, switch to the \Vss\Win32 subdirectory. If you are not, switch to the WIN subdirectory.</li>  Type the following command: SS CHECKIN $/<projectname/filename> where <projectname/filename> is the Visual SourceSafe path and file name of the file checked out in step 6. You get the following message:

$/<projectname/filename> was checked out from C:\Test2, not from the current directory. Continue anyway?(Y/N)

N cancels the Check-In. Y prompts the following message:

File "C:\Test1\ " not found

where is the name of the file checked out in step 6. </li></ol>

NOTE: If you repeat these steps with the Ss.ini file set to FORCE_DIR=YES, the error will not occur.

Keywords: kberrmsg kbprb KB158471

-

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

© Microsoft Corporation. All rights reserved.