Case Study: GplPostBatch Error DBMS:0, Microsoft Dynamics GP 20052

Situation:
I have had several clients come to me with the following error: GplPostBatch returned the following results: DBMS:0, Microsoft Dynamics GP 20052. This typically occurs when they are posting a journal entry in the GL or printing an edit list. The one thing that they all have in common is that they used the Excel copy and paste feature.

To resolve this, there are two solutions, one before and one after the event occurs.

Solution 1 – Prevention:

1. Always have the cursor in the first entry position when you paste from Excel.
2. Only the data that is being copied needs to be highlighted. This would leave the header information blank.
3. If your cursor ends up anywhere other than the blank account after pasting the data, then you will need to delete the blank line that appears at the bottom. Data is still in the line and is only appearing blank.

Solution 2 – Correction:

1. Go to the end of the journal entry. If you expand the blank entry, the entry should be blank. If you expand the information in the distribution reference, then the entry is reading data in the field. Delete this line.
2. If the error still occurs after the line is deleted, then recreate the Journal entry by repasting it in. Delete the old journal entry.
3. If this is a persistent issue, then consider upgrading to GP2018 R2. In their most recent release, they included a fix list, and this error was marked as repaired.


Comments

One response to “Case Study: GplPostBatch Error DBMS:0, Microsoft Dynamics GP 20052”

  1. I like the efforts you have put in this, regards for all the great content.

Leave a Reply to Jaquan Kidd Cancel reply

Your email address will not be published. Required fields are marked *