Article ID: 162627 - Last Review: January 19, 2007 - Revision: 3.3 OFF97: Error Message "Vbe.dll Was Unable to Register Itself"This article was previously published under Q162627 IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
On This PageSYMPTOMS When you run Setup, you may receive one or both of the
following error messages after all files have been copied to the hard disk on
your computer. VBA332.dll error The Visual Basic
Environment could not be initialized. Please run Setup to install it correctly.
Microsoft <program> Setup Vbe.dll was unable to register itself in the system registry. Microsoft Visual
Basic Unexpected critical error: can't start program
Microsoft <program> Setup was not completed successfully. NOTE: You may also receive this error message if you click Tools on the menu bar and Setup stops responding. CAUSE This problem may occur if the following conditions are true
for any of the following cases: Case 1
Case 2
Case 3
WORKAROUND To work around this problem, use any of the following five
methods. Method 1Modify the path to point to the shared programs, and then run Setup again.NOTE: This modification is required only while you are running Setup. You can remove the modification to the path statement after you successfully install the program. Under Microsoft Windows NTIf you are running Microsoft Windows NT, follow these steps:
Under Microsoft Windows 95If you are running Microsoft Windows 95, follow these steps:
Method 2WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To prevent this problem from occurring, follow these steps:
Method 3In some cases, you may be able to correct this problem by using the Windows Explorer to copy the file Vbeext1.olb into the following folder:C:\Program Files\Common Files\Microsoft Shared\Vba You can find Vbeext1.olb in the OS\System folder of your administrative installation of Microsoft Office 97, or in the OS\System folder of your Microsoft Office 97 compact disc. After you have copied the Vbeext1.olb file into the Vba folder, re-run Microsoft Office 97 Setup. Method 4If the following folder exists on your hard disk driveC:\Windows\Temp\Vbe Method 5If none of the above solutions resolve the problem, try following the steps in the following article in the Microsoft Knowledge Base:158658
(http://support.microsoft.com/kb/158658/EN-US/
)
OFF97: How to Completely Remove Microsoft Office 97 Note that a utility that automates the process of removing Office
97 is available.
The following file
is available for download from the Microsoft Download
Center:
Eraser97.exe
(http://download.microsoft.com/download/office97std/utility/4.0/win98mexp/en-us/eraser97.exe)
For
additional information about how to download Microsoft Support files, click the
following article number to view the article in the Microsoft Knowledge Base: 119591
(http://support.microsoft.com/kb/119591/EN-US/
)
How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most
current virus-detection software that was available on the date that the file
was posted. The file is stored on security-enhanced servers that help to
prevent any unauthorized changes to the file.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
APPLIES TO
| Article Translations
|

Back to the top
