The information in this article applies to:
SYMPTOMS
When permanently deleting or renaming a project in the Microsoft Visual SourceSafe (VSS) Explorer, you may receive a series of errors: followed by:
RESOLUTIONThese operations can be performed at the command line. For example, the following operation is for the delete permanently operation:
The following is for the rename operation:
Note that this produces multiple "File or project not found" errors, but it will complete.An alternative workaround exists in the case of permanently deleting files. The error messages do not occur when deleting without destroying and then purging from the Visual SourceSafe Explorer. A supported fix for Visual SourceSafe 6.0 that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.asp The English version of this fix should have the following file attributes or later:
All files are contained in a self-extracting EXE.
NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the earlier Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. MORE INFORMATIONThis problem is intermittent and has not been consistently reproduced by Microsoft. This happens only on projects immediately below the root ($/) project in databases that have been updated to the new Visual SourceSafe 6.0 database format. Additional query words: destroy string load failure
Keywords : kbCommandLine kbSSafe600bug kbSSExplorer kbDSupport kbGrpSSafe kbSSafe600qfe |
Last Reviewed: December 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |