My analyst is getting this error when she is billing. Not sure where to start with checking logs/code.
Hi James
Next step :)
Do you have customization? if yes, disable it and then see if you will get wrong number of argument error or not.
Hi Almas,
That was one of the first things I tried to make sure all the files were the same version. The only difference between the two systems is one was Windows 7 and the new one is Windows 10.
James, Did you install Dynamics GP in new PC?
Do you have GP folder from Old machine?
Backup GP folder in your new machine by renaming it, copy GP folder from old machine and past on same path. (I if have installed GP on default path then you don't need to change anything)
Login to GP and check if still getting error?
Does this happen for any other users?
Recompiling is not something end users can do.
If you install GP Power Tools, we would be able to use logging to capture the name of the script that is causing the error. Then we can identify the product that script is from and check the version of the dictionary. If it needs updating you can contact the developer to get them to update the code.
GP Power Tools has a 30 day trial so you can install it and test it out. There are many other benefits so most users that try it, buy it.
Regards
David
Hi David,
I am new to the Great Plains system. I have very basic install notes from my predecessor but that is it.
Could you point me in the direction of instructions on how to recompile everything? The user started having issues after she got a new PC.
They must have third party customization or ISV code that has not been upgraded and recompiled against GP 2016.
Please check the Dynamics.set and the version numbers of all dictionaries.
If you have GP Power Tools, the Product Version Validation window will show all the dictionary version numbers.
To get this error they must have some code that was compiled before an optional parameter was added to the IV_Check_Location global procedure in March 2012.
If they had a trigger against this script it would give an error on startup when the trigger was registered. However, if the custom code is calling the script it would fail at the time the call is made.
The code does not need changing, it just needs to be recompiled against a GP v16.0 dictionary.
Did they recently update to GP 2016?
This is the risk of using dictionaries that have not been updated for the same version of GP and Dexterity.
Regards
David
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,524 Super User 2024 Season 2
Martin Dráb 228,493 Most Valuable Professional
nmaenpaa 101,148