In my experience, this isn't usually caused by CF issues. It's usually database issues. Two processes are having trouble getting at the table at the same time. Perhaps one is trying to update data, and it's taking too long. (bad indexing? Poorly designed query?)
Can you "force" this error to occur? If so, look in the Enterprise Manager under Current Activity -> Process Info (or one of the locks areas) and look for highlighted processes. That can tell you what is locking, though maybe not why. -----Original Message----- From: Clark Baker [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 9:18 AM To: SQL Subject: Transaction deadlock error I've been working with CF and SQL Server for several years and recently began seeing an error I've never seen before. It occurs very rarely but it's bugging me: "OLEDB Error Code = 1205 Your transaction (process ID #100) was deadlocked with another process and has been chosen as the deadlock victim. Rerun your transaction." The error is occurring on a pretty simple SELECT query (3 joins) and there is no <CFTRANSACTION> or <CFLOCK> used in the template. I've looked around and can't find anything on this. Has anyone seen this before in this situation? There isn't that much traffic so I don't know what's going on. Thanks, Clark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=6 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=6 Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
