Deadlock Victim When Listing Transactions

May 09, 2006 4 Replies

When using the POS interface and pulling up a listing of transactios, i.e. F11 and selecting void a transaction, we get an error stating that we were deadlocked with another process and the POS interface crashes. This typically happens after the busiest portion of the day. In manager we are able to pull up and view the receipt in the journal with no problems. The POS interface can pull transactions from a few days back without a problem, anything from that day or from 1 or 2 days before also causes this problem.



Enterprise manager is re-indexing the database nightly, in the morning there is no problem pulling the information from the POS. We do 1100 - 1500 transactions a day. This just a single store. Any ideas or suggestions would be greatly appreciated.



Patrick


The exact error message, is

Run-time error'-2147467259 (80004005)':

Transaction (process ID 65) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Not much help because you are using full SQL, but on MSDE this exact error occurs in a busy store when you get up to the 9th process (MSDE is limited to

8 processes at > The exact error message, is

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required