I 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 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:
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 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.
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
This article was originally posted on http://www.winthropdc.com/blog.