Article ID: 937950 - View products that this article applies to.
This article discusses error 3928 in Microsoft SQL Server 2005 and in SQL Server 2000. The wording of the error message may be misleading when you troubleshoot this error.
When you experience error 3928 in SQL Server 2005 and in SQL Server 2000, the error message resembles the following:
This error message indicates that a typical SQL Server deadlock has occurred. However, when error 3928 occurs, SQL Server cannot add a mark in the transaction log in a way that would prevent later deadlocks. Therefore, the typical troubleshooting steps to find and to resolve deadlocks do not apply to error 3928. For example, you should not use trace flag 1204 to troubleshoot error 3928.
The marked transaction '%.*ls' failed. A Deadlock was encountered while attempting to place the mark in the log.
For more information about SQL Server deadlock, click the following article number to view the article in the Microsoft Knowledge Base:
118552For more information, visit the following Microsoft Developer Network (MSDN) Web site:
(https://support.microsoft.com/kb/118552/ )Description of handling deadlock conditions in SQL Server
Article ID: 937950 - Last Review: November 20, 2007 - Revision: 1.5