Solution to "File not found: VBA6.DLL" Error Message

The File Not Found: VBA6.DLL issue which I had explained in my previous post has got a solution.

Thanks to Japheth Nolt, who pointed me to this Partner Forum post.

The following are the steps to fix this issue, taken directly from Dynamics GP Partner Forum Post (Link To the Original Post: File Not Found: VBA6.dll):

Important This article contains information about how to modify the registry. Make sure to 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: 

1. Export all customizations to a .package file.

2. Close Microsoft Dynamics GP.

3. Make a backup of the system registry.

4. Change the following key in the system registry:


to have the path of this: C:\Program Files\Common Files\microsoft shared\VBA\VBA6\VBE6.dll

Note, if on a Windows 2008 Server R2 install the key was this: HKEY_CLASSES_ROOT\TypeLib\{000204EF-0000-0000-C000-000000000046}\4.1\9\win32

5. Delete all VBA files with a file size of 4KB.

6. Rename all VBA files with a file size greater than 4KB.

7. Start GP.

8. Open VBA editor.

9. Check the VBA reference to ensure the path is to the C:\Program Files\Common Files\microsoft shared\VBA\VBA6\VBE6.dll file.

10. Add a window and field to VBA and test the message box code.

11. Verify the message box works.

12. Import all customizations.

13. Verify more than one customization works.

Note, this has only been tested on an Office 32-bit installation. If you have an Office 64-bit installation, you will need to uninstall it and then install the 32-bit version. This will not affect Outlook user profiles.

What I did is the following:

1. I removed all the VBA files from GP Folder in my 32 Bit machine.

2. I performed the steps listed above from #1 to #4 (modifying the registry entry).

3. I launched GP and opened the VBA Editor, to make sure that the Visual Basic for Applications Reference is pointing to the path C:\Program Files\Common Files\microsoft shared\VBA\VBA6\VBE6.DLL.

4. Closed GP. Relaunched it.

5. Imported the VBA Customizations that were exported from 64 Bit machine.

6. My customizations started working.

IMPORTANT NOTE: You must re-reference any 3rd Party plugin references after importing the VBA Packages, in case these 3rd Party plugins sit in Program Files (x86) folder in 64 Bit machine.

Hope this is helpful for people who face this issue.



5 thoughts on “Solution to "File not found: VBA6.DLL" Error Message

  1. Vaidy: I have a simmilar issue. In my case we have a 64 bits PC with Office 2010 installed.I erase all the .vba files, rewrite the registry key. Open GP reimport the package, and everything goes well. But once I close GP and reopen it, it rewrites the system registry key, and start again to show the error in an infinite loop. I'm getting mad with this issue. Any tip???


  2. Manuel,The following must be the steps for you, before you import the packages:1. Export the VBA packages without any References (ADO, MDAC, etc.).2. Launch your 64 Bit GP and add each one of the VBA modified window to VBA Editor manually.3. Add the necessary references to respective windows.4. Then import the packages that you have exported. I stress again that these packages should NOT have any references. Those references must be added manually in GP 64 Bit PCs.5. Close GP and launch it back.The above steps must help you. I know it's a tedious job of manually adding windows to VBA Editor and then adding references. But this is the only way we can overcome this issue.Vaidy


  3. Hi there,actually i also got this error but i still can manage to open my GP. The error messages occured when i trying to print? Can i use your step above to solve my problem?


  4. Those who are using Windows 7 as their client operating system, please update the registry path will be :


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s