BUG: Analyze Problems with Open Log FilesLast reviewed: February 27, 1998Article ID: Q181717 |
The information in this article applies to:
SYMPTOMSAnalyze reports returns the error listed below and if you are running Analyze with either the -f or the -d switch, or both, files are deleted either from the data\<a-z> directory, or destroyed in the SourceSafe database. Here is the error:
Unable to open file <physical filename> File <physical filename> is already open. CAUSEIf a log file (a file with no extension in one of the data\<a-z> folders) is opened and locked by a different process, such as a backup utility running simultaneously with Analyze, Analyze treats the file as an orphan.
RESOLUTIONThe best cure is prevention. You should run Analyze without any switches before running it with either the -d switch or the –f switch. If Analyze reports that a file is already open, take whatever steps necessary to close that file before using the additional switches. Once the problem has occurred, the resolution will be determined by a number of factors, such as which files have been deleted, how important it is to maintain their history, and whether a file or project was affected. If you are not sure what action to take, contact Microsoft Technical Support.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONAn orphan file is one that has been destroyed from the SourceSafe database via the SourceSafe Explorer or the command line, and is not branched to or from a file that still exists in the database. In the scenario described in the CAUSE section, Analyze sees this file as an orphan, but its physical file pair still exists in the data\<a-z> folder. Analyze -d attempts to delete the file pair. It might delete either or both of the files, depending on which file is locked at the time it attempts the deletion. A locked file is not deleted. This may result in "File <physical data file name> not found" errors. Analyze -f behaves differently on projects and files as described below:
Steps to Reproduce BehaviorNOTE: Reproducing this behavior causes problems with the SourceSafe database. Do not attempt to reproduce this on a live database. Use this on a database that is set up for testing purposes only. Using an application that locks files that it opens, such as Microsoft Word, opens a log file in the SourceSafe data directory. Run Analyze with any combination of the -f and -d switches, for full information, use the -v4 switch.
REFERENCESFor additional information, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q139566 TITLE : SAMPLE: Analyze5.Exe Utility for Visual SourceSafe ARTICLE-ID: Q168634 TITLE : INFO: When -d Switch of Analyze Deletes Files ARTICLE-ID: Q157984 TITLE : How SourceSafe Uses the DATA Directory ARTICLE-ID: Q167263 TITLE : PRB: <filename> is Already Open Keywords : ssdb Version : WINDOWS:5.0 Platform : WINDOWS Issue type : kbbug |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |