The information in this article applies to:
SYMPTOMSWhen you try to restore an archived project to the same database that it was archived from, you might get the following message:
CAUSEIf any repairs to the file were needed when you ran Analyze (build 2327 or earlier) with the -f switch, a new GUID in the UM.dat was created. As a result, an archive GUID and the UM.dat GUID are out of sync. STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. Analyze, build 8169, no longer regenerates the GUID in the UM.dat unnecessarily. MORE INFORMATION
Visual SourceSafe stores a 16-byte GUID in the header part of UM.dat file,
which is used to uniquely identify a database. SSARC and SSRESTOR uses this
information to determine whether it is restoring to the same database or a
different one. Whenever UM.dat needs to be repaired and you run Analyze -f
against the database, Analyze rebuilds the UM.dat. Builds of Analyze prior
to 8169 create a new GUID while rebuilding the UM.dat file, even if the
header information in the UM.dat file is not corrupt. Q190881 SAMPLE: Analyze6.exe Utility for Visual SourceSafeNOTE: Always back up your database before running Analyze. Additional query words:
Keywords : kbSSafe500bug kbSSafe600fix kbAnalyze |
Last Reviewed: August 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |