Posted by: istewart | December 3, 2009

Your previous transaction-level posting session has not finished processing


Trying to open a document in SOP and you get told the following? Your previous transaction-level posting session has not finished processing. Please allow time for it to finish. Second most asked question in support…this occurs when posting routines were interrupted for some reason.

  1. Back up your Dynamics and company databases.
  2. Note down the GP user ID of the session that is getting the error message. Then get everyone out of GP.
  3. Go to MSSQL and open a new query window. Run the following query: Delete dynamics..sy00800
  4. Run the following queries against the Company database
  5. SELECT * from SY00500 where BACHNUMB = ”
  6. If this query returns any rows, then run: Delete SY00500 where bachnumb = ”
  7. SELECT * from SY00500 where BACHNUMB = ‘???’ (where ??? is the USER ID of the person getting the problem in GP)
  8. If this query returns rows, then run: Delete SY00500 where bachnumb = ‘???’
About these ads

Responses

  1. Hi can you clarify to me why records are locked on that tables? By the way we are using currently this process hierarchy

    1. Sales Order
    2. Transfer to Sales Invoice
    3. Print
    4. Look Up Previous Invoice
    5. Post Invoice

    We don’t do batch posting due to errors encountered on GP not removing allocation on inventory.

    • Hi Kristoper,
      This error usually occurs because the posting process has been interrupted for some reason. Its not an issue with GP…GP is doingits work, but the posting routine has been stopped prematurely. It could be a system crash,a dropped network connection, or interference from a custom development / trigger that causes some standard GP posting process to fail. Generally,its a dropped network connection. If it is happening frequently, you really need to monitor things to find out why. By the way, what errors did you encounter with P not removing inventory allocations? Have you any custom developments running on the SOP entry window? Even just a badly placed custom trigger can cause problems. What version of GP and service pack?

      Send me your email address if you want to take this off line. Post your emal in a comment here, and I won’t publish the comment to keep your privacy.

  2. see the full procedure at microsoft’s KB: http://support.microsoft.com/kb/852623


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: