#GPPT The type initializer for ‘Microsoft.Dexterity.Applications.root’ threw an exception

David Meego - Click for blog homepageWhile researching for the recent support case referenced in my earlier article, I identified another similar situation that I thought would be worth explaining.

In this example, we were receiving another Add-In Initialization Error when launching Microsoft Dynamics GP which was related to GP Power Tools and the WinthropDC.GpPowerToolsVB.dll or WinthropDC.GpPowerToolsVC.dll add-in.

Please note that a similar issue could be caused by any Dexterity product that also uses Visual Studio Tools addin dlls.

The Problem

The full error message displayed on launching Microsoft Dynamics GP was:

WinthropDC.GpPowerToolsVB.dll: The type initializer for ‘Microsoft.Dexterity.Applications.root’ threw an exception. InnerException: Specified argument was out of the range of valid values. Parameter name: productId

Below is a screenshot of the error message:

GPPTAddinError2

During the troubleshooting steps, we confirmed that if you removed or renamed (by changing the extension) of the WinthropDC.GpPowerToolsVC.dll and WinthropDC.GpPowerToolsVB.dll files in the Addins folder, that Microsoft Dynamics GP would launch without error.

However, once launched there was no sign of GP Power Tools on the menus or area pages.

The Cause

The cause of this issue was that the system was launching Microsoft Dynamics GP with a shortcut that pointed to a different launch file than Dynamics.set.

All Microsoft Dynamics GP dictionaries (both Microsoft created and ISV created) use chunk files that extract themselves when the Dynamics.set launch file is used. Part of the chunking process defines the name of the launch file to Dynamics.set.

During the GP Power Tools install, it silently extracts its GPPTools.cnk chunk file against Dynamics.set launch file to create the GPPTools.dic dictionary file.

If you look in the application folder you will see the dictionary file and if you edit the Dynamics.set launch file you will see GP Power Tools is installed.

The WinthropDC.GpPowerToolsVC.dll and WinthropDC.GpPowerToolsVB.dll files are installed into the Addins folder and are automatically loaded and initialized when Microsoft Dynamics GP starts up.

If you start Microsoft Dynamics GP using the Dynamics.set launch file, the GP Power Tools dictionary is loaded and when the add-ins initialize, they can find the dictionary objects they need and no errors are generated.

If you start Microsoft Dynamics GP using a different launch file that does not load the GP Power Tools dictionary, then you will receive errors when the add-ins attempt to initialize.

The Solution

To fix the issue you will need to ensure that both GP Power Tools and the Mekorma Product Manager dictionaries are manually added to the custom launch file. You can look at the Dynamics.set to get the settings to copy.

Note: Make a backup copy of the custom launch file before you edit it.

You will need to increment the number of products installed and then copy the Product ID and Product Name lines across. Then you will need to copy the 3 path lines for each dictionary into each set of workstation paths (usually only one set, by can be more).


5261
GP Power Tools
7156
Mekorma Products Manager

:C:Program Files (x86)/Microsoft Dynamics/GP/GPPTOOLS.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/GPPT_FRM.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/GPPT_RPT.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/MEP7156.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/MEP7156F.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/MEP7156R.DIC

Moral: Please be aware that using custom launch files will require extra steps when installing or removing products.

Hope this helps

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Dynamics, GP, GP Power Tools, Microsoft, Products Tagged: GP Power Tools, GPPT

Originally posted here:
#GPPT The type initializer for ‘Microsoft.Dexterity.Applications.root’ threw an exception

March 16, 2016 · WinthropDC · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 88

#GPUG Webinar: Why is the Support Debugging Tool/GP Power Tools so Amazing?

David Meego - Click for blog homepageAfter the huge success at the GPUG Summit 2015 conference, Beat Bucher MVP and I will be presenting an encore performance of our GP Power Tools (GPPT) session as a webinar.

Even though the session title mentions the Support Debugging Tool (SDT), the session focusses on GP Power Tools. This is because the Support Debugging Tool has been discontinued since October 2014 and replaced by GP Power Tools.

The webinar session is being presented as part of the DBA SIG (Database Administrators Special Interest Group). The details of the session are below:

This webinar takes you through some of the many ways that the Support Debugging Tool can make your life administering, supporting, consulting or developing for Microsoft Dynamics GP easier. David Musgrave and Beat Bucher will use real life examples to show how the Support Debugging tool can help. This session also includes demonstrations of GP Power Tools, and its new features.

This webinar is part of the Database Administrators Special Interest Group, whose goal is to help you learn and share expertise, tools and tips for managing and developing for Dynamics GP

DBA SIG: Why is the Support Debugging Tool/GP Power Tools so Amazing?

Thursday 17th March 2016 (10:00 AM) to Thursday 17th March 2016 (11:00 AM) (US EST)

Click here to Register.

For more information see:

Hope to see you there

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Dynamics, GP, GP Power Tools, GPUG, Microsoft, Products, Support Debugging Tool Tagged: GP Power Tools, GPPT, GPUG, SDT, Support Debugging Tool

Continue reading here:
#GPUG Webinar: Why is the Support Debugging Tool/GP Power Tools so Amazing?

March 15, 2016 · WinthropDC · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 80

#GPPT Function MBS_Net_Execute_Available does not exist in the dictionary

David Meego - Click for blog homepageI recently had a support case where the customer was receiving an Add-In Initialization Error when launching Microsoft Dynamics GP which was related to GP Power Tools and the WinthropDC.GpPowerToolsVB.dll or WinthropDC.GpPowerToolsVC.dll add-in.

The Problem

The full error message displayed on launching Microsoft Dynamics GP was:

WinthropDC.GpPowerToolsVC.dll: Fuction MBS_Net_Execute_Available does not exist in the dictionary. Parameter name: scriptName

Below is a screenshot of the error message:

GPPTAddinError

During the troubleshooting steps, we confirmed that if you removed or renamed (by changing the extension) of the WinthropDC.GpPowerToolsVC.dll and WinthropDC.GpPowerToolsVB.dll files in the Addins folder, that Microsoft Dynamics GP would launch without error.

However, once launched there was no sign of GP Power Tools on the menus or area pages.

The Cause

The cause of this issue was that the Dynamics.set launch file was corrupted. There were paths pointed to in the Dynamics.set launch file which did not exist. For custom forms and reports dictionaries, it is alright if the files themselves don’t exist, but the folder path specified must exist. This issue stopped the dictionaries listed after the bad paths from loading.

It is also possible to get the same error if the Dynamics.set launch file does not have the GPPTOOLS.DIC GP Power Tools application dictionary on the correct line in the list of the paths. This could happen if the Dynamics.set launch file is incorrectly manually edited.

Another existing dictionary file was on that line so we did not receive a “dictionary not found” error, however, when the WinthropDC.GpPowerToolsVC.dll and WinthropDC.GpPowerToolsVB.dll addin files attempt to initialize they are unable to locate the expected GP Power Tools resources in that dictionary.

The Solution

To fix the issue we needed to ensure that the Dynamics.set was correct. That it had 2 product lines for the number of installed products (number on first line) and that it had 3 path lines for the number of installed products (for each workstation set, if more than one), and that the paths all pointed to valid folders and files.

Note: Make a backup copy of the Dynamics.set launch file before you edit it.


5261
GP Power Tools

:C:Program Files (x86)/Microsoft Dynamics/GP/GPPTOOLS.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/GPPT_FRM.DIC
:C:Program Files (x86)/Microsoft Dynamics/GP/Data/GPPT_RPT.DIC

Hope this helps

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Dynamics, GP, GP Power Tools, Microsoft, Products Tagged: GP Power Tools, GPPT

See the original article here:
#GPPT Function MBS_Net_Execute_Available does not exist in the dictionary

March 14, 2016 · WinthropDC · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 66

Friday Funny: How many 3’s are in the image?

David Meego - Click for blog homepageI am no longer testing your maths skills, but instead testing your powers of observation.

I found another challenge doing the rounds on the internet and thought we could have some more fun.

The question is: How many 3’s are in the image below?

1026708677375884

Do not post the answer in comments, instead here is a poll for you to respond to:

Take Our Poll

Let’s see how good you observant you are.

Enjoy

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Fun Tagged: Friday Funny, Fun

Excerpt from:
Friday Funny: How many 3’s are in the image?

March 11, 2016 · WinthropDC · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 102

Microsoft Dynamics GP 2016 due in May

David Meego - Click for blog homepageEarlier today, my friend Pam Misialek from the Microsoft Dynamics GP product marketing team announced the release date for Microsoft Dynamics GP 2016 on the Inside Dynamics GP blog.

This is the first release of Microsoft Dynamics GP to support HMTL5 for its web client, which enables it to work across any browser on any device (including Apple and Android tablets).

Microsoft Dynamics GP 2016 is scheduled for a general availability worldwide release on the 1st May 2016.

Pam’s article goes on to mention some of the other enhancements such as the OData connection for Microsoft Power BI and easier data at a glance with more All-In-One document viewers.

Have a read of her post here:

There will be a Feature of the Day series starting this month to highlight the many other new features.

Looking forward to GP 2016.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: 2016, Business, Dynamics, GP, Microsoft, News Tagged: GP 2016, News

More:
Microsoft Dynamics GP 2016 due in May

March 10, 2016 · WinthropDC · No Comments
Tags: , , , , , ,  · Posted in: Blogs I Follow Total Views: 115

#GPUGAmplify vs #GPUGSummit

David Meego - Click for blog homepageFollowing on from last week’s announcement of the new GPUG Amplify conference, #GPUGAmplify Welcome to the New GPUG Amplify Conference, there have been questions about the focus of the new conference when compared to GPUG Summit.

So Bob McAdam posted a graphic on Facebook which compares the two conferences.

It shows how GPUG Amplify is all about meeting with Microsoft and learning about the future of the Microsoft Dynamics GP product, while GPUG Summit is focussed on meeting with your peers and learning about the current versions you are using.

GPUG Amplify vs GPUG Summit

As you can see there is value in attending both GPUG Amplify and GPUG Summit.

Enjoy

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Conference, GPUG Tagged: Continuum, GPUG, GPUG Amplify, GPUG Summit 2016

See more here:
#GPUGAmplify vs #GPUGSummit

March 10, 2016 · WinthropDC · No Comments
Tags: , , , , , ,  · Posted in: Blogs I Follow Total Views: 145

SBA is not as Asynchronous as you might think

David Meego - Click for blog homepageService Based Architecture (SBA) was released with Microsoft Dynamics GP 2015, it covers technologies to make Dynamics GP more accessible to external applications by allowing Dexterity global procedures to be exposed as Web Services. It also allows Dexterity code to directly access and use .Net objects via the .Net Interop.

SBA opens up an entire new world of development opportunities.

As you might have noticed, in the last few days I have posted articles relating to Web Services using Service Based Architecture and the Batch Posting Service Toolkit (BPST).

There is a reason…. I have been working with Neal Santin from WebSan Solutions to implement BPST on their systems. Neal has been a great help to work through some of the issues we found and his assistance is appreciated. He told me of a new issue that he has come across which is the subject of this article.

When they started using BPST to post batches, they found that if they make the web service calls too quickly they would receive a 403 (forbidden) error with the description:

403 – The specified user is not authorized to perform operations in this context

The issue is that the web service call uses credentials to log into a specific user and company of Dynamics GP. Once the web service finishes processing it logs out. As is the same with the full Dynamics GP client you can only log in once for a specific user and company combination.

So if you try and log in again before the web service has finished, you will get the above error message. This issue will be worse on web service calls that take longer to process, such as posting. The issue was that they were generating web services calls faster than Dynamics GP’s ability to process them.

I did double check with my friend Brian Roney at Microsoft and he confirmed that you cannot call a web service using same user until the previous call had completed:

If a call is still processing for a user that user cannot successfully make another call until the first one finishes.

Once Neal and his team worked out the cause of the error they implemented a retry loop to pause and try again if they received a 403 error. However, this method meant staying single threaded (same user and company) and a backlog of web service calls could easily build up.

To get around the issue, Neal came up with the second part of the solution to use a pool of User IDs in rotation so that multiple web service calls can be processed concurrently. Creating additional Active Directory (AD) users and linking them to different GP User IDs allowed for multiple web services calls to launch multiple instance of the runtime engines used for processing SBA web services.

Moral: If you are planning to make heavy use of web services using a single User ID to make the calls, be aware that you might hit this 403 error issue and need to implement some workaround solutions.

Moral 2: A 403 error could just mean that the User ID and Company ID you are trying to use is currently logged into Dynamics GP.

Thanks to Neal for letting me share his experiences.

Hope you find this helpful.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: 2015, 2015 R2, Development, Dexterity, Dynamics, GP, Microsoft, Service Based Architecture, Uncategorized Tagged: Batch, BPST, Development, Dexterity, SBA, Service Based Architecture

Continued here:
SBA is not as Asynchronous as you might think

March 9, 2016 · WinthropDC · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 112