Microsoft KB Archive/171813

From BetaArchive Wiki
Knowledge Base


FIX: IPF in MSO97RT.DLL When Starting Visual Basic

Article ID: 171813

Article Last Modified on 11/18/2003



APPLIES TO

  • Microsoft Visual Basic 5.0 Learning Edition
  • Microsoft Visual Basic 5.0 Professional Edition
  • Microsoft Visual Basic 5.0 Enterprise Edition



This article was previously published under Q171813

SYMPTOMS

An attempt to start Visual Basic may fail with the following error:

VB5 caused an invalid page fault in module MSO97RT.DLL at 0137:306d820a

CAUSE

This problem is caused by corrupt information in the Windows registry at the following key:

HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\5.0\UI


This setting includes information regarding Visual Basic command bars (menus). If this information is invalid, Visual Basic will crash at startup while attempting to load command bar information.


RESOLUTION

One solution is to reset (clear out) this setting using the Registry Editor (regedit.exe). However, the recommended solution is to install the Visual Studio 97 Service Pack 2.

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:

170365 : INFO: Visual Studio 97 Service Packs - What, Where, and Why


For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

171554 : INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2



Additional query words: office crash gpf starting launch

Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp3fix kbvs97sp2fix KB171813