Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / glpBatchCleanup retune...
Microsoft Dynamics GP (Archived)

glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hi

After upgrading Dynamics GP (9 to 2013 (sp2), I am getting some error while posting the GL Batches...  everything is working properly (even from the sub modules posting also working fine) 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." - 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 Testing purpose I created one sample company in the same server and created some accounts and try to post, its working perfectly.....without any error...

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

Thanks in advance.

Biju

*This post is locked for comments

  • Kevin Day Profile Picture
    Kevin Day 610 on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Just wanted to throw something out there that I am testing out in case anyone else finds this article.  

    My system also gets this error (maybe not this specific error number) but it prompted me to look at the stored procedure itself.

    For some reason the system I am supporting was installed on SQL Server that is case sensitive (Binay Installation I guess)

    So I can't run

    SELECT * FROM dynamics..sy01500

    It has to be 

    SELECT * FROM DYNAMICS..SY01500

    Even field names need to be capitalized.

    In this stored procedure there is stuff like this all throughout

    SELECT rsrcid
    FROM dynamics.dbo.sy00801
    WHERE ruleid = @RULE_RESERVESTATE
    AND rsrcid = @I_cBatchNumber
    AND rsrcsbid = @I_cBatchSource
    AND cmpanyid = @I_sCompanyID
    AND userid = @I_cUserID
    AND rsrdesc = str(@I_iSQLSessionID) )

    That select statement will not even run on my system.  In fact I have spent the last 30 minutes synching up the variables that have mixed case and updating all the filed names to try and get it to even re-create.

    If all of the SQL is not formatted properly, I'm not sure how it can even run at all.  Or why I only get this error sporadically.  Maybe it just doesn't get called all the time?  

    Aynways, I am going to make it case sensitive and try it out.  I'll post back  

  • Almas Mahfooz Profile Picture
    Almas Mahfooz 11,003 User Group Leader on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    :)

    good. when there is a will,there is always some work around.(Y)

    thanks for sharing.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Hi Almas, As I mentioned earlier, I have created a separate company for Testing purpose, with some demo data, I dint face any issue while posting.. So I focused on that way only... take out all the data out through BCP.. then removed the DB,  created  the Company DB again with same ID, insert the data into the newly created DB  (BCP ),  Made necessary changes in DB ( before doing this process in the LIVE company, I did it  in a TEST company for checking, when everything was fine, then I did it for the LIVE company,)  anyway everything is fine, including  posting :)

    Biju

  • Almas Mahfooz Profile Picture
    Almas Mahfooz 11,003 User Group Leader on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Biju, I am glad that you are able to solve your problem, and I am also keen to know your work around. Hope you will share here it with all of us.

    When we have these types of posting issues we always try to find things by breaking it, that's why I asked you to first post on sub modules, because sometimes some data creats problem otherwise you have mentioned all the things in your first post. Actually fixing posting issues are just like a detective work.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Hi Mahmoud , this solution is ok for 1 or 2 transaction and if its happens for once in a while, my situation is ,  transactions are 100's daily, and the DB size is almost 24 GB... and  20-25 users are online at the sometime...Anyway I almost found a solution in other way-around to overcome this...Anyways thank you for the support..

    Regards / Biju

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Thanks for the msg, As I mentioned in my first query, I have mentioned there, if i post from any sub modules, its posting fine, only from GL I am getting this error.... anyways I have sort it out this issue in another way..Thanks for the support..

    .

  • Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    For this batch specifically, post corruption occurred leaving part of the batch in GL10000 (Work) and moving part of the batch to GL200000 (Posted). In order to get this problem specifically solved, you need to do the following;

    • With all the users logged out of Dynamics GP, run the following select statements
    SELECT * FROM DYNAMICS..ACTIVITY 
    SELECT * FROM DYNAMICS..SY00800 
    SELECT * FROM DYNAMICS..SY00801 
    SELECT * FROM TEMPDB..DEX_LOCK 
    SELECT * FROM TEMPDB..DEX_SESSION
    • If any records are returned form the above, run the following delete statements;
    DELETE DYNAMICS..ACTIVITY 
    DELETE DYNAMICS..SY00800 
    DELETE DYNAMICS..SY00801 
    DELETE TEMPDB..DEX_LOCK 
    DELETE TEMPDB..DEX_SESSION
    UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 WHERE BACHNUMB = '#BachNumber'
    After applying the steps above, you will have the batch released. Go to the original batch entry and get it posted. Please note that you need to check GL2000 for any potential duplication.
    Now, most importantly, you have mentioned that the problem occurs quite often, then you need to determine what is causing this issue. Would it be Server Performance, network performance ... etc. There are a long list to check regarding this issue, thorough diagnosis for your environment is a must.
    Hope this helps,
  • Almas Mahfooz Profile Picture
    Almas Mahfooz 11,003 User Group Leader on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Issue is with your posting, and I think first you need to find out the reason of issue.

    Can you do it.

    1.Create new batch in any module, lets say sales module with only having one transaction.(saving existing transaction in your new batch).

    do batch posting and then check your sy00500 table. if everything seems fine then go further.

    else

    query the SY00500 table and share the results here.

    We will move further to GL posting after will be done at that point.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Thanks, I have check the SY00500 status is 6 / in SY00801, record is available... in GL100001 no data available, but Gl10000 Header Part of the GL  is available (same available in GL20000) - so every time I have to remove this manually and run the reconcile / check links.... Any suggestions please....

    Regards

    Biju

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: glpBatchCleanup retuned the following results: DBMS: 0, Microsoft Dynamics GP: 20820

    Hi Mahmoud , This solution is fine if the error will appear sometimes, but i am getting this error for each and every GL batches while posting...

    Anyway thanks for the reply

    Regards

    Biju

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!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans