You’re offline. This is a read only version of the page.
I fielded a call today with the usual batch stuck in posting issue. This was a PO receiving batch. The batch in the SY00500 table was marked to post with a BCHSTTUS of 5. I set both of these values to zero and logged in as 'sa' I could see and print the edit list for this batch. The user who originally tried to post the batch was locked so I had to use task manager to kill GP. As soon as he logged back into GP the batch posting process picked up from where it left off and completed successfully. This is not the first time I have seen this type of behavior. How is this possible? What caused the initial locking were records in the DYNAMICS..SY00800 table. It appears that deleting those two records pertaining to this user's activity were what was causing the locking.
Hi Richard,
This appears to be more of a comment than a question. Records can get stuck in the activity tables, and having the user log out and back in again is one of those 'troubleshooting tricks' to see if it helps. If not, then you would have to clear out the activity tables with SQL scripts. But yes, sometimes logging and logging back in again can refresh temp/activity tables for that user and the process picks up where it left off. We always have you do this as in this KB article for when a payables check run batch gets stuck:
support.microsoft.com/.../852064
A status of 5 just means that it was in 'printing' status.
Cheryl Waswick
Microsoft Dynamics GP Support
Share
Report
75,848
All responses (
Answers (
