It's been quite a while since I've had to import package files into Dynamics GP, so when I got this error today when trying to import a large package file into GP 2013, it puzzled me for a few minutes.
Error: "VBA cannot be initialized. Cannot import this package because it contains VBA components."
If you search for this error, you will likely come across a Microsoft KB article saying that this error means that your VBA install is damaged and you have to fix it. Um, no, I don't think that's the issue, since I have three GP installs on this server, and all of the VBA customizations work fine, and I can import packages into those other GP installs.
So something else was up.
Thanks to the prolific Dynamics GP Community Forum, I found this thread from 2010 where a clever user recommended checking to see if Modifier was registered in GP. Hmmmm.
https://community.dynamics.com/gp/f/32/p/31214/72654.aspx
Sure enough, this was a new GP 2013 R2 install, and I hadn't yet entered reg keys. Once I entered the license keys and saved them, the package imported fine.
What a useless error message.
Steve Endow is a Microsoft MVP for Dynamics GP and a Dynamics
GP Certified IT Professional in Los Angeles. He is the owner of Precipio
Services, which provides Dynamics GP integrations, customizations, and
automation solutions.
1 comment:
This appears to be a .Net thing. A client has just installed MR CU15 which installed .NET 4.6 and had to exec wfDeployClrAssemblies afterwards due to errors in Workflow.
Post a Comment