FIX: ANALYZE Crashes When No Log Entries Found in Log File

 Last reviewed: December 18, 1997
Article ID: Q171535
The information in this article applies to:
  • Microsoft Visual SourceSafe, 32-bit, for Windows, version 5.0
  • Microsoft Visual Studio 97

SYMPTOMS

In Pass 3 of 4, the status bar stops displaying new files. After processing on the same file for a random amount of time, an Access Violation error occurs: 

   Analyze.exe Exception: access violation (0xC000005), address 0x00406372
You may experience other variations of errors messages, all resulting in Analyze crashing.

CAUSE

Analyze tries to rebuild a file containing no log entries.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.

For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

MORE INFORMATION

Please note that The Visual Studio 97 Service Pack 2 readme states that the issue fixed was: "ANALYZE Application Error When Directory Not Found." This is incorrect.

Additional query words: gpf general protection fault crash hang
Keywords : vss VS97FixlistSP3 VS97FixlistSP2
Version : WINDOWS:5.0
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix kbservicepack

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.