FIX: An access violation occurs intermittently when you run an application that uses SQL Server 2005 service broker or SQL Server 2008 service broker

Article translations Article translations
Close Close
Article ID: 976691 - View products that this article applies to.
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

When you run an application that uses Microsoft SQL Server 2005 service broker or Microsoft SQL Server 2008 service broker, an access violation occurs intermittently. Then, error messages that resemble the following are logged in the SQL Server error log file:
<Date Time>,spid76,Unknown,Service Broker needs to access the master key in the database '<Database Name>'. Error code:25. The master key has to exist and the service master key encryption is required.
...
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,* Access Violation occurred reading address 0000000000000000
<Date Time>,spid22s,Unknown,* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
<Date Time>,spid22s,Unknown,* Exception Address = 0000000002B8FA73 Module(sqlservr+0000000001B8FA73)
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,*
<Date Time> spid 22
<Date Time>,spid22s,Unknown,* BEGIN STACK DUMP:
<Date Time>,spid22s,Unknown,*
<Date Time>,spid22s,Unknown,* *******************************************************************************
<Date Time>,spid22s,Unknown,SqlDumpExceptionHandler: Process 22 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION.
SQL Server is terminating this process.
<Date Time>,spid22s,Unknown,***Stack Dump being sent to C:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
...
<Date Time>,spid22s,Unknown,An error occurred in the Service Broker internal activator while trying to scan the user queue '<User Queue>' for its status. Error: 2905<c/> State: 2.
These error messages describe the following sequence of events. An error occurs when SQL Server 2005 or SQL Server 2008 accesses the master key. This error causes the access violation. Additionally, other errors occur when SQL Server 2005 or SQL Server 2008 tries to scan the user queue.

Note A mini-dump file is generated in the SQL Server log folder.

CAUSE

This problem occurs because of a race condition between the alter operation for a queue whose status is "on" and the drop operation for the same queue. If the drop operation succeeds, the access violation occurs. Additionally, the queue cannot be scanned successfully as part of the alter operation.

RESOLUTION

SQL Server 2005

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
976951 Cumulative update package 7 for SQL Server 2005 Service Pack 3
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:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008

Release version of SQL Server 2008

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
977444 Cumulative update package 9 for SQL Server 2008
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 2008 fix release. We recommend 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 SP1

The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
977443 Cumulative update package 6 for SQL Server 2008 Service Pack 1
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 2008 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. 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.

REFERENCES

For more information about the Incremental Servicing Model for Microsoft 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 3 (SP3), 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 new features and improvements that are included in SQL Server 2005 SP3, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=131442
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: 976691 - Last Review: January 18, 2010 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup 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
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbexpertiseadvanced kbsurveynew kbqfe kbfix KB976691

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