Scott.Macmaster
July 1st, 2008, 10:43 AM
I have an ASP.NET page that occasionally gaves this error message, "Transaction (Process ID 72) was deadlocked on thread | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction." It's fairly rare. I think I've gotten 3 it times in the last month.
The page is for reporting a does a lot of processing. It has generally has to pull in 100,000+ records. However, it does no updates to the database. I see no reason for it to get involved in a deadlock.
Does anyone know what could cause this or at least if this is a database or ASP.NET issue?
Thanks
The page is for reporting a does a lot of processing. It has generally has to pull in 100,000+ records. However, it does no updates to the database. I see no reason for it to get involved in a deadlock.
Does anyone know what could cause this or at least if this is a database or ASP.NET issue?
Thanks