Microsoft KB Archive/937950

= Explanation of error 3928 in SQL Server 2005 and in SQL Server 2000 =

Article ID: 937950

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition
 * Microsoft SQL Server 2005 Express Edition
 * Microsoft SQL Server 2005 Express Edition with Advanced Services
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Workgroup Edition

-



INTRODUCTION
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.



MORE INFORMATION
When you experience error 3928 in SQL Server 2005 and in SQL Server 2000, the error message resembles the following:

The marked transaction '%.*ls' failed. A Deadlock was encountered while attempting to place the mark in the log.

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.

