File not found: VBA6.dll error occurs or GP crashes

This is a follow up to my previous post on the VBA6.dll not found error (for 64-bit). I have found this can occur on 32-bit computers and Microsoft Dynamics GP 10.0 and GP 2010.

Important: This post contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base (KB) Article:

• KB 256986: Windows registry information for advanced users

I have found that the issue is because the 4.0 registry key is missing.  This is created with earlier versions of Microsoft Office and Microsoft Dynamics GP.

To resolve this error, you need to add the 4.0 registry key. 

Here are the steps:

1. Make a full backup of the system registry.
    
2. Export all modifications to a .package file from Microsoft Dynamics GP under Tools | Customize | Customization Maintenance.
    
3. Create a .reg file that contained the following in Notepad:
    
   Windows Registry Editor Version 5.00
    
   HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.0
    
   @=”Visual Basic For Applications”
    
   HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.09 
    
   HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.09win32 
    
   @=”C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL”
    
   HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.0FLAGS 
    
   @=”0″
    
   HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.0HELPDIR 
    
   @=”C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\”
    
4. Next, double-clicked the .reg file, so it was added to the system registry. 
    
5. The HKEY_CLASSES_ROOTTypeLib00204EF-0000-0000-C000-0000000000464.1 key should point to the VBE7.dll file.
    
6. Next delete the .vba files that were 4kb and renamed the .vba files that were over 4kb in the Microsoft Dynamics GP code folder.
    
7. Start Microsoft Dynamics GP.  You should not receive any errors.
    
8. Import the .package file.  Verify the code works and the error no longer occurs.

I have had a few customers state that they had to unregister the msvbvm60.dll.  But I did not run across that with the customers I have streamed in with.

Beth Gardner

Support Escalation Engineer
Microsoft Dynamics GP Developer Support

16-Nov-2010: Added link to previous article.

Read more:
File not found: VBA6.dll error occurs or GP crashes