FIX: Error message when you connect to an instance of SQL Server 2005 by using a login for which you create a logon trigger: "The server failed to resume the transaction"

Article translations Article translations
Article ID: 951188 - View products that this article applies to.
Bug #: 50002573 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005, you create a logon trigger for a login. Then, you connect to the instance of SQL Server 2005 by using the login. In this scenario, you receive the following error message:
The server failed to resume the transaction. Desc: 5400000002.(Microsoft SQL Server , Error: 3971)
Additionally, the following error message is logged in the error log:
Date Time SPID Process SPID unlocking unowned resource: DATABASE: n
Date Time SPID Error: 1203, Severity: 20, State: 1.
Date Time SPID Process ID SPID attempted to unlock a resource it does not own: DATABASE: n . Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
Date Time SPID Process SPID unlocking unowned resource: DATABASE: n
When this problem occurs, a minidump file is generated in the SQL Server 2005 log folder.

RESOLUTION

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
949095 Cumulative update package 7 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
949095 Cumulative update package 7 for SQL Server 2005 Service Pack 2

Important information for SQL Server 2005 Analysis Services

A known issue exists in Cumulative Update 7 for SQL Server 2005 Analysis Services. Consider the following scenario. You install Cumulative Update 7 for SQL Server 2005 SP2. In SQL Server Profiler, you start a trace or stop a trace. Then, you run a query. The execution time of the query exceeds the value of the ForceCommitTimeout server setting. In this scenario, all the queries that are running on the server are canceled. To work around this issue, do not run MDX queries before you start a trace or stop a trace.

REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 951188 - Last Review: May 6, 2008 - Revision: 2.2
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbsql2005engine KB951188

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com