Dynamics Community Forum Thread Details

While accessing modified report error polulating "File not found: VBA6.DLL"

Hi Experts,

While accessing my GP 2010 customized report am facing this error and am getting thie error after moving to window7 from windows XP. I found one solution on community as below link and applied accordingly and it works for few days only and after that problem came back. Please advie with your valuable suggesions.

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2010/08/27/file-not-found-vba6-dll-error-occurs-or-gp-crashes-and-creats-a-watson-fault-bucket-1474386816.aspx

Thanks,

Habeeb

This issue actually is caused by MS Office updating the system registry incorrectly. The blog you mentioned is one resolution we've seen for this error. You can also try the following:

A. Unregister the msvbvm60.dll file:

1. Login to Dynamics GP 2010 as SA, go to the Customization Maintenance window and export everything into a package file.

2. Logout of Dynamics GP 2010 and then in the GP 2010 code directory, move all of the .VBA files out into a backup directory as well as any forms dictionary files, such as Forms.dic.

3. Un-register the 'MSVBVM60.DLL file:

• For a 64-bit Operating System: Go to Start > Run and enter in: regsvr32.exe c:\windows\syswow64\msvbvm60.dll /u

• For a 32-bit Operating System: Go to Start > Run and enter in: regsvr32.exe c:\windows\system32\msvbvm60.dll /u

4. Log back into Dynamics GP 2010 again as SA, go back into the Customization Maintenance window and import the package file from step 1 back into GP 2010, this will re-create the VBA files and forms dictionary files.

5. Try having users login again to Dynamics GP 2010 to see if the same VBA6.dll error shows.

B. As mentioned in the blog, if verifying the Windows Registry settings do not resolve this error, then the next step is to reinstall the VBA6.4 core components from the following location:

mbs2.microsoft.com/fileexchange

This will repair the VBA6 environment and resolve the incorrect references within Dynamics GP.

C. If the above all fails, the next step would be to uninstall and re-install first Dynamics GP 2010 and then MS Office 2010.

From my experience, un-registering the dll file and/or the Registry settings in the blog above, usually resolve this error.

Quick Links

Leaderboard