Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

glpBatchClenup - Error

Posted on by 70

HI,

we are using Dynamics GP 2010. and a user reported that he got the below error message while he was trying to print the entries in his batch. 

" The stored procedure glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820."

More Info:

glpBatchCleanup. Error occurred attempting to update Batch_Headers.

appreciate if anybody can explain why this error occurring and applicable solutions. 

Thanks in advance.

*This post is locked for comments

  • Suggested answer
    Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at
    RE: glpBatchClenup - Error

    The issue apparently lies within mostly the batch data. Therefore, I might check the following;

    • GO to SQL, check SY00500 | Posting Definition Master. You might find corrupted batch or batches (empty batch number for instance)
    • GO to Microsoft Dynamics GP > Tools > Utilities > Financial > Reconcile > Batches 

    Your feedback is highly appreciated.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchClenup - Error

    Any Luck ? I am also getting the same error after upgrading Dynamics 9 to 2013 (sp2), everything is working properly except GL batch posting...when posing the GL i am getting the error message - " The stored procedure glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820." - bust when I checked it in the database,  original batch data isn’t cleared out from the entry tables (SY00500, GL10000, but from GL10001 its cleared ) although the batch was actually posted.

    For Tesing purpose I created one sample company in the same server and crate 2 accounts and try to post, its working perfectly.....

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchClenup - Error

    Hi - do you have any batches stuck in posting? If so, I would clear these first.

    It is possible that the batch header has become corrupted. Easiest way to get around it is to call up the transaction in this batch and assign them to a new batch - post this batch and delete (if you can) the old batch through he GP interface. If you can't then you will need to delete it through SQL.

    If the above doesn't work - get everyone out of GP and run the following in SQL:

    DELETE DYNAMICS..ACTIVITY

    DELETE DYNAMICS..SY00800

    DELETE DYNAMICS..SY00801

    (Back everything up first :))

    Ian.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans