
We have two separate users having similar issues in Microsoft Dynamics GP 2018.
One has issues running payroll and it locks up and then causes SQL Database issues and we have to get our Dynamics Vendor to fix and then proceed.
Another has this kind of error when posting Inventory, especially in batches...
We also worked with our vendor over this (and we do like and trust them) but they have been unable to resolve. This has all happened since doing the year end update for GP 2018 but also when I set up new PC's for both users. GP is installed correctly, we did the REPAIR option for GP 2018 and we also set up new dictionary files. Nothing has resolved it and we've spent a lot of money for support with our vendor. Like a lot and can't keep paying it every week.
Has anyone seen these kinds of problems?
Hey Brian,
All steps are provided as is. Steps should be tested in a test company with a copy of live.
Let's see if we can get to the bottom of this.
The first error is likely because you have stuck records in the your Payroll Work Tables. The following KB is what we recommend for this error.
Errors when selecting a batch - Dynamics GP | Microsoft Learn
Now the second error is going to be a little more difficult. This is referring to your Reports and the error does not give enough info to determine what might the problem. My assumption is when you attempt to recover, it continues the posting process and when a report attempts to generate, this is what is causing the error.
Can you submit a screenshot of the More Info if you click the button. This might give us some further insight.
In addition, have you tried to recover the batches using the sa user? The sa user should have access to everything so would be a good test.
Another thing that i would recommend since you just applied a patch is to recreate and synchronize your forms and reports. These can cause problems after an upgrade and might be part of your issue. This is machine specific.
If the above does not help, please send a screenshot of the 2nd error more info and hopefully it will give us some insight.
You can also look at creating a support case with Microsoft as well for one of the specific errors as well.
I hope this helps!
Thank you!
Brandon | Microsoft Support Engineer.