Article ID: 310451
Article Last Modified on 1/16/2007
APPLIES TO
- Microsoft .NET Framework 1.1
- Microsoft Visual Basic 6.0 Enterprise Edition
This article was previously published under Q310451
SYMPTOMS
When you use Visual Basic 6.0 components in your managed code, you may receive "Unhandled Exception" error messages.
CAUSE
Older versions of the Visual Basic 6.0 runtime (Msvbvm60.dll) have a shutdown problem that manifests as an "Unhandled Exception" error when you use Visual Basic 6.0 components from managed code.
RESOLUTION
Visual Basic 6.0 Service Pack 3 (SP3) includes Msvbvm60.dll version 6.0.8495. Any system that runs a managed code application and that uses Visual Basic 6.0 components must use Msvbvm60.dll version 6.0.8495 or later.
To work around this problem, install the latest Visual Basic 6.0 service pack on the computer where you develop or prepare distribution packages for your Visual Basic 6.0 components. This prevents the problem from occurring with future components that are packaged for distribution on this system.
You can download Visual Studio 6.0 Service Pack 5 from the following Microsoft Web site:
If you experience this problem on a production (non-development) computer, and if you verify that the version of the Visual Basic runtime is earlier than Visual Basic 6.0 Service Pack 3, you can download the latest version of the Visual Basic runtime file from the following Microsoft Knowledge Base article:
290887 VBRun60sp6.exe installs Visual Basic 6.0 SP6 run-time files
STATUS
This bug was corrected in the .NET Framework and in Visual Basic Enterprise Edition for Windows 6.0.
MORE INFORMATION
The circumstances that this article describes do not represent all possible causes of "Unhandled Exception" errors.
Additional query words: kbreadme unhandled application
Keywords: kbfix kbpending kbreadme KB310451
