We've run into this from time to time, it occurs when two or more users thry to access the data at exactly the same time even though SQL is suppose to handle it. Just refreshing it seems to clear up the deadlock. I haven't heard any other solutions for resolving the problem though. Let me know if you do.
*************************************** Bob Imperial Software Development Team Schoollink, Inc. 910-223-2116 ext. 108 *************************************** "Linking Schools to The World ...... One Classroom at a Time" -----Original Message----- From: Houk, Gary [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 3:06 PM To: CF-Talk Subject: What is this SQL Error? First time I've seen this one...what does it mean? Diagnostics: ODBC Error Code = 40001 (Serialization failure) [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 60) was deadlocked on {lock} resources with another process and has been chosen as the deadlock victim. Rerun the transaction. ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
