You’re offline. This is a read only version of the page.
We are frequently getting the 'Your previous transaction level posting has not completed' message when going into SOP Entry. I know how to fix the problem, but I don't know what is causing it. The batch that is always stuck is called 'void'. The users are not having any problem with GP crashing or erroring during posting. This even happens with users who never do any posting. Any idea's on how to stop this from happening?
*This post is locked for comments
The knowledge base contains instructions for fixing the problem:
mbs2.microsoft.com/.../kbdisplay.aspx
CAUSE
This problem may occur if an invalid record exists in the SY00500 table.
RESOLUTION
To resolve this problem, follow these steps; 1. Have all users exit Microsoft Dynamics GP.
2. Use the appropriate step: • If you are using Microsoft SQL Server 2005, start SQL Server Management Studio. To do this, click Start, point to Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
• If you are using SQL Server 2000, start SQL Query Analyzer. To do this, click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
• If you are using SQL Server Desktop Engine (also known as MSDE 2000), start Support Administrator Console. To do this, click Start, point to Programs, point to Microsoft Administrator Console, and then click Support Administrator Console.
3. Run the following statement against the company database.
Delete SY00500 where BACHNUMB = User_ID_Of_The_User_Who_Receives_The_Error_Message
If the problem persists, see Microsoft Knowledge Base article 852623. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
852623 Error message when you try to open the Sales Transaction Entry window in Sales Order Processing in Microsoft Dynamics GP: "Your previous transaction-level posting session has not finished processing"
I don't have any answer to your question however you mentioned in your post that when this occurs you know how to fix it but don't know what is the root of the problem. Can you at least let me know how to fix this. I am unable to do anything in SOP as I keep getting the same message.
Understood all.
Yes, it has become one of those things that since I couldn't reproduce or track - I just put it down to connectivity issues. Its not a big problem, but it has happened enough times for me to remark on it - with one customer who uses Citrix.
The SOP posting indeed is very heavy - a lot going on with Inventory, GL, Salespeople, VAT, Intrastat etc...much more than with other transactions - so it's no surprising that any connectivity issues will throw up errors here more than with other transactions.
But - any ideas why batch processing doesn't seem to suffer as much? Is it because of SQL functionality to handle batch processing better? Surely a transaction posting is handled the same way as a batch processing by SQL?
Ian.
The problem does not always happen on our system, so I cannot consistently reproduce it, which makes things very frustrating. But it does happen more to some users then others. I'm going to try disabling transaction level posting and see if that works around the problem.
The Allow Deletion of Documents is located under Setup->Sales->Sales Order Processing->Picke the Type of Document->Sales Document Setup. Unlclick the Allow Delete Documents button. This is combination with the Posting Setup option will stop anyone from deleting sales documents.
PS - Bob, you can disallow transaction level posting on the Posting Setup window (GP | Tools | Setup | Posting | Posting). Please be very careful on this window, as it controls all the posting behavior in GP and there is no Undo option.
Ian and Bob,
Unfortunately, it's not as straightforward as that.
I void and post SOP transactions in our production system all the time and never have any issues. And have been doing this for many GP versions. So it's not that this happens every time. I have done this with no issues in various customer environments as well, using RDP. I also have customers that do this routinely with no issue. I typically recommend they do not do this, because I have seen this problem enough times, but the point is that it may not be so easily reproducible as to be called a bug.
While it's very hard to make generalizations and I have not devoted any time to actually tracking this, in my experience it tends to happen with our customers that experience more connectivity issues than others. It also happens more with customers that have add-ons or customizations surrounding SOP. (These are often the same customers.) I believe that posting (and voiding?) in SOP does a lot more processing (for lack of a better word) than most other posting processes in GP, so if a problem was going to show itself, it is likely that it would be there.
I have also suspected at times that there may be a security setting responsible for this (especially for the voiding without a batch situation) because I recall at least one customer where some users were able to void without a batch with no issue and others ALWAYS got stuck. Again, hard to say this was not a connectivity issue and we didn't work too hard to find the cause after we figured out the work around, especially since voids were pretty rate there. Bob, since you're saying it happens every time you post, can you log into GP as a user who is a POWERUSER and see if this still happens? (Maybe in a test company if you have one?)
It looks like a bug to me, and one that we have experienced in version 9 and now in 2010. We have always run in a Citrix/XenApp environment, so I can' t comment on if that is the cause.
The problem does not appear to be limited to just voids. It also happens when posting invoices directly from the SOP Entry screen.
I personally have not seen the issue with RM documents, only SOP.
Hi all,
Are we saying we have a bug?
I've come across this before - again within a Citrix Xenapp enviornment. I always put it down to a network glitch, fixed the problem, and forgot about it until next time.
From what you are saying Leslie and Victoria, you have discovered a workaround by not allowing voids to be posted direct - If the Void problem isn't a bug, then its an undocumented 'Feature'!!
How long have you been working around this issue? I have a site running version 8 that gets this issue frequently enough for me to comment on it when it happens.
Other customers using XenApp also get this error - but with other transaction types (RM Invoices etc).
Is there something inherently flaky about the transaction level posting process, that posting as part of batches avoids?
Whats your experience?
Ian.
Thanks for the ideas. How do you turn off transaction posting in SOP? I looked for this options but could not find it.
We are still getting this error, and it does occur when someone posts directly from the SOP Entry screen.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (