22.16
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 116) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 125
21.34
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 141) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 187
If any of you were as sad as me and woundering what was causing Matts headache then this is one probable cause. ( I wish i had not looked now)
Microsoft OLE DB Provider for SQL Server (0x80004005) Your transaction (process ID #<spid>) was deadlocked with another process and has been chosen as the deadlock victim. Rerun your transaction. This can occur if you use an isolation level of READ COMMITTED or READ UNCOMMITTED and have multiple concurrent connections attempting to run the same procedure or batch. Consider using REPEATABLE READ or even SERIALIZABLE, realizing that this will be a performance hit (usually sending lock blocks through the roof). Otherwise, try and make your T-SQL code more efficient, so that there is less chance that two unique users will trip over each other.
(source http://tutorials.aspfaq.com/8000xxxxx-errors/80004005-e...rrors.html)
23:13 - 12/08/2007
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 123) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 187
ok I've made some more changes, by setting up transaction lock types that should allow the server to manage requests better.
I've only changed the main forum page for now, so let's monitor it and see how we get on.
Cheers
lol, ok. Dont think it's gonna be fixed though, not sure what else I can do now either.
I'm working with the webhosts to set up full-text indexing which may alleviate some problems
Ok there have been some big changes made on the database now (Full text indexing configured for those in-the-know).
I'm hoping this will help us out a lot.
Please continue to let me know of any errors you get, especially over the next 24 hours.
Cheers!
22.01
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 180) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 182
Dammit! Just wish I could see what was locking the database at the time these errors occured.
I've got a course this week, wed-fri, and my teacher has offered to help me investigate this. He's an SQL wiz as it's an SQL Designers course.
The internet sites have been pretty useless so far in helping me... don't give enough info to help solve the issue.
Keep the info coming though please, it all helps. Thanks
Well what's everyone's opinion today???
You let this topic get to the second page of the forums, so I'm hoping that's good news!
I had a couple of time-outs, but nothing much today.
Let me know how you're all getting on.
Just had my first one of the day...
Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/header_inc.asp, line 276
23:10 your time (GMT)
![URGENT: Site errors - deadlock victim (5) - Forums [Biker Match]](/images/backgrounds/strips/8mobileLQ.jpg)
![URGENT: Site errors - deadlock victim (5) - Forums [Biker Match]](/images/backgrounds/strips/8desktopLQ.jpg)
