This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I have been seeing a number of reports on Newsgroups and Support cases of Add-In Initialization Errors.
In particular, after installing updates or service packs after v10.00 SP2, receiving the following message:
eOne.Dynamics.GP.ExcelBuilder.Engine.dll: Exception has been thrown by the target of an invocation. InnerException: The type initializer for ‘eOne.Dynamics.GP.ExcelBuilder.GPAddIn’ threw an exception.
The error message is shown after launching the application and before the login window is displayed. It looks like the screenshot below:
The cause of errors of this type is when a Visual Studio Tools add-in assembly dll is looking for a Dexterity dictionary which is no longer included in the current workstation’s Dynamics.set launch file.
In this case, you can generate the error if you remove SmartList Builder (Product ID 3830) from the Dynamics.set without removing the eOne.Dynamics.GP.ExcelBuilder.Engine.dll file from the Addins folder.
To fix the issue, you can perform either of the following options:
- Add SmartList Builder back into the Dynamics.set launch file.
- Delete or move the eOne.Dynamics.GP.ExcelBuilder.Engine.dll file from the Addins subfolder under the Microsoft Dynamics Application folder. (Default location: C:Program FilesMicrosoft DynamicsGPAddins).
The problem with this add-in would not have been seen prior to v10.00 Service Pack 2 as the Excel Builder functionality was added as part of the Feature Pack included with Service Pack 2.
At the bottom of the following Knowledge Base (KB) article is a similar situation relating to the Report Scheduler (Product ID 3278):
How to disable third-party products in the Dynamics.set file in Microsoft Dynamics GP (KB 872087)
I hope you find this helpful information. Thanks to Robert Cavill for bringing this issue to my attention.
More information can be found in the following KB Article:
David
10-Feb-2009: Added link to KB 963087.
This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.
Hi David
I am big fan of your Blog, keep up the good work.
I would like to also add that it has been my experience that if you launch Utilities and re-upgrade the GP dictionary the error goes away as well.
please see group post:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&lang=&cr=&guid=&sloc=en-us&dg=microsoft.public.greatplains&p=1&tid=ce14f058-5431-453c-ad44-43612ddec0d3
Thanks
LikeLike
Posting from the Dynamics GP Blogster
http://dynamicsgpblogster.blogspot.com/2009/01/developing-for-dynamics-gp-weekly.html
LikeLike
Sorry wrong URL in post.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?&lang=&cr=&guid=&sloc=en-us&dg=microsoft.public.greatplains&p=1&tid=bd3f43fe-146c-47cd-8a63-31ea1d02f495&mid=bd3f43fe-146c-47cd-8a63-31ea1d02f495
LikeLike