PRJ41:"Could Not initialize VBA", "Timer Driver Not Installed"

Last reviewed: March 20, 1998
Article ID: Q154658
4.10 4.10a WINDOWS

The information in this article applies to:

  • Microsoft Project for Windows 95, versions 4.1 4.1a
  • Microsoft Excel for Windows 95, version 7.0, 7.0b

SYMPTOMS

When you start Microsoft Project, the following error message is displayed:

   Could not initialize Visual Basic for Applications.
   Timer Driver not installed.

The same message also appears when you attempt to insert a module in a Microsoft Excel workbook.

CAUSE

There are several possible causes:

Case 1

A conflict with another device or software running on the system.

To test whether there is a conflict with a device or software application running on the system, start Windows 95 in Safe Mode. If Microsoft Project starts properly, then check for and disable items loading in the Windows 95 Start folder and also check for items in the registry Run, RunOnce, RunServices, and RunServicesOnce keys. You can find these keys at:

   \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

To remark-out a key's value data without deleting it, edit the value and place a semi-colon or other character as the first character in the value name. This will disable the device so that you can test without it being loaded when Windows 95 starts.

Case 2

The Vba32.dll, Vbaen32.dll, or Vbaen32.olb file is corrupted or missing.

Case 3

The file Mmsystem.dll is corrupted or missing. This file should be in the Windows\System folder. The correct file size is 103,248 bytes, and the correct file date is July 11, 1995.

Case 4

The System.ini file is missing a line that says "drivers=Mmsystem.dll," or the file Mmsystem.dll is missing from the Windows\System folder.

NOTE: The "drivers=" line in the System.ini file may contain more than one file name to the right of the equal sign.

RESOLUTION

To work around this problem, use the appropriate method for your situation.

Method 1:   Remove the offending program that is conflicting with the
            Windows 95 virtual timer services.

Method 2:   If the files Vba32.dll, Vbaen32.dll, or Vbaen32.olb are
            corrupted or missing, rename the files and reinstall
            Microsoft Project.

            1. In the Windows\System folder, locate the following files:

               Vba32.dll
               Vbaen32.dll
               Vbaen32.olb

            2. Select each file and give it a different name. For example,
               you might change the extension to "old."

            3. Reinstall Microsoft Project.

Method 3:   If the Mmsystem.dll file is corrupted or is missing, replace
            the existing Mmsystem.dll with the extracted file from the
            setup disks.

            The file is located in WIN95_08.CAB on Disk 8 of the Windows 95
            disks, or in the Win95 folder of the Windows 95 CD-ROM.

            For additional information on how to extract individual files
            from CAB files, please see the following article in the
            Microsoft Knowledge Base:

               ARTICLE-ID: Q129605
               TITLE     : How to Extract Original Compressed Windows 
                           Files 

Method 4:   If the Mmsystem.dll file is missing from the System.ini file,
            edit the System.ini file so that Mmsystem.dll is listed on the
            "drivers=" line, and make sure that Mmsystem.dll is present in
            the Windows\System folder.

STATUS

Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

For additional information, please see the following article(s) in the Microsoft Knowledge Base:

   ARTICLE-ID: Q109778
   TITLE     : Timer Driver and "Error . . . Initializing VBA Libraries"


KBCategory: kbprb kbenv
KBSubcategory:

Additional reference words: VBA timer.drv initialize Visual Basic library
Keywords : kbenv kbprb
Version : 4.10 4.10a
Platform : WINDOWS


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: March 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.