FIX: Analyze -F Overwrites the Analyze.Log File When the Backup Folder Is Not Empty

Article translations Article translations
Article ID: 275926 - View products that this article applies to.
This article was previously published under Q275926
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page


If you use Analyze -F, the Analyze.log file is replaced in the \data\backup folder and the following warning message appears:
The backup folder \data\backup, is not empty.
Before an autofix rebuild is run the backup folder needs to be emptied.
However, the analyze.log is replaced.


The backup directory needs to be empty before running Analyze -F.


Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in the next service pack for Visual Studio 6.0.

For additional information about Visual Studio service packs, click the following article numbers to view the articles in the Microsoft Knowledge Base:
194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 HOWTO: Tell That a Visual Studio Service Pack Is Installed
To download the latest Visual Studio service pack, visit the following Microsoft Web site:


Steps to Reproduce Behavior

  1. Run Analyze -F ../data, and note that a backup directory containing Analyze.log is created.
  2. Run Analyze -F ../data again without renaming the backup directory.


Article ID: 275926 - Last Review: October 21, 2013 - Revision: 1.2
  • Microsoft Visual SourceSafe 6.0 Standard Edition
kbnosurvey kbarchive kbbug kbfix kbssafe600fix kbssafeanalyze kbvs600sp5fix KB275926

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from