Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/fretbuzz/fbmsg.asp, line 49
I sometimes get it when I click to view messages. What's it about? Anyway I can stop it happening?
Yo Rob,
That has happened to me a few times. I just click on the Back button and try againand, it works for me after that! No big deal.
The reason that it happens, I have no idea....:^D
Clifton
It deals with the database engine used for storing the messages. In order to maintain the integrity of the data in the midst of multiple source update activity, there are certain resources that must be used in a single-thread manner. When two requests for that resource hit at exactly the same time, one is chosen to be the "loser" and is dropped. When you get that message, your request happened to be the "loser". There are times when you don't get the notification because someone else "lost".
Actually, from a geek perspective this is interesting because it happens when there is a "standoff". Your request locks some resource and needs to lock another. Someone else has that resource locked and needs the one that you have locked. The system can't just make one of you wait, so it flips a coin and shoots the loser (figuratively, that is). Without the standoff situation, it just makes you wait.
lol. That's awesome! Good to know. I used to just think it was a little glitch, and didn't think much about it... Now it seems more fun! Like a little game, even if I did lose... =D
Ah, I see :-)... it seems doctors never have problems getting the girls ;-)... plus all the germans gals I've met, are sweet as pie... So, I'm sure you'll have NO problems :-D
Oh yes. I love Northern european women. So much better than the Brits, and nice and tall. Mmmmmm. 5'10- 6' athletic girls rule. Not shotput "women" though. :-)