Microsoft Knowledge Base Email Alertz

KBAlertz.com: Explanation of error 3928 in SQL Server 2005 and in SQL Server 2000

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 937950 - Last Review: November 20, 2007 - Revision: 1.5

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

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.

REFERENCES

For more information about SQL Server deadlock, click the following article number to view the article in the Microsoft Knowledge Base:
118552  (http://kbalertz.com/Feedback.aspx?kbNumber=118552/ ) Description of handling deadlock conditions in SQL Server
For more information, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms178104.aspx (http://msdn2.microsoft.com/en-us/library/ms178104.aspx)

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
Keywords: 
kbtshoot kbinfo kbsql2005engine kbexpertiseadvanced KB937950
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please