web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Receivings batch hung ...
Microsoft Dynamics GP (Archived)

Receivings batch hung in gl

(0) ShareShare
ReportReport
Posted on by SUPPORT-ICM 695
I have a receivings batch that will not post. The receivings were not done in a batch so when it was closed and posted, the master batch was still open. It has some June and July receivings in the master batch. When we go to post, it says "this batch is receiving". Any clue how to get this to post?

*This post is locked for comments

I have the same question (0)
  • jeffb Profile Picture
    jeffb 305 on at

    Sometimes rebooting the server will unlock it. If that does not work, then try running purchasing maintenance.

  • SUPPORT-ICM Profile Picture
    SUPPORT-ICM 695 on at
    We have rebooted the server - well actually it made us but it was done nonetheless. Where do i go to run the purchasing maintenance - is that the reconcile purchasing under utilities?
  • Ron Wilson Profile Picture
    Ron Wilson 6,010 on at

    Michelle,

    I have found a possible solution on Customer Source, but I am not allowed to post it here (***Maybe one of the MVP's can correct me if I am wrong***).  If you have Customer Source access then you can do a search for

    Article ID : 850289

    Let me know if that helps.  I would always recommend trying in my test database before doing anything in my production database.

    Ron

     

  • Community Member Profile Picture
    Community Member on at

    Not sure I fully understand your post above, but, if you have a batch that you believe is stuck in busy, receiving, posting, marked, locked etc. then the following will resolve the issue.

    First, note down the Batch ID.

    Then have everyone log out og GP. Then login to MSSQL. Back up your company database and the DYNAMICS database. Then run the following queries:

    SELECT * FROM DYNAMICS..ACTIVITY
SELECT * FROM DYNAMICS..SY00800 
SELECT * FROM DYNAMICS..SY00801 
SELECT * FROM TEMPDB..DEX_LOCK 
SELECT * FROM TEMPDB..DEX_SESSION
    Normally, if everyone is logged out of GP, there should be no data returned by the above. If data is returned, verify that everyone is logged out of GP and then run the following:
    DELETE DYNAMICS..ACTIVITY 
DELETE DYNAMICS..SY00800 
DELETE DYNAMICS..SY00801 
DELETE TEMPDB..DEX_LOCK 
DELETE TEMPDB..DEX_SESSION
     
    Then run the following query against the company database: (Replace XXX with the Batch ID)
    UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX'
    As always, best to run this on a test company first (you can force restore you live data into a test company). Make sure you have back ups before doing it in a live company.
  • jeffb Profile Picture
    jeffb 305 on at

    I would try the maintenance under utilites you mentioned or go to tools- maintenance-checks links and run purchasing.

  • Ron Wilson Profile Picture
    Ron Wilson 6,010 on at

    [quote user="Ian Stewart"]

    Not sure I fully understand your post above, but, if you have a batch that you believe is stuck in busy, receiving, posting, marked, locked etc. then the following will resolve the issue.

    First, note down the Batch ID.

    Then have everyone log out og GP. Then login to MSSQL. Back up your company database and the DYNAMICS database. Then run the following queries:

    SELECT * FROM DYNAMICS..ACTIVITY
SELECT * FROM DYNAMICS..SY00800 
SELECT * FROM DYNAMICS..SY00801 
SELECT * FROM TEMPDB..DEX_LOCK 
SELECT * FROM TEMPDB..DEX_SESSION
    Normally, if everyone is logged out of GP, there should be no data returned by the above. If data is returned, verify that everyone is logged out of GP and then run the following:
    DELETE DYNAMICS..ACTIVITY 
DELETE DYNAMICS..SY00800 
DELETE DYNAMICS..SY00801 
DELETE TEMPDB..DEX_LOCK 
DELETE TEMPDB..DEX_SESSION
     
    Then run the following query against the company database: (Replace XXX with the Batch ID)
    UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX'
    As always, best to run this on a test company first (you can force restore you live data into a test company). Make sure you have back ups before doing it in a live company.

    [/quote] 

     

    This was the KB that I had found as well.  It looks like it should solve your problems.  I didn't know if we could post it on these forums or not.

  • Community Member Profile Picture
    Community Member on at

    Hi Ron,

    Don't know for sure, but don't see why we couldn't post links to customer / partnersource KB's. I certainly have done so in the past, and others do too.

    Best regards,

  • Ron Wilson Profile Picture
    Ron Wilson 6,010 on at

     Great...thanks Ian!

  • SUPPORT-ICM Profile Picture
    SUPPORT-ICM 695 on at
    Thanks to everyone for their responses. I have given this to them to fix. Hope it works (fingers crossed).
  • Ron Wilson Profile Picture
    Ron Wilson 6,010 on at

    Well please do let us know if it works or not :)

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans