FIX: Error message when you trace the Audit Database Management event and you try to bring a database online in SQL Server 2005: “Msg 942, Level 14, State 4, Line 1”

Article translations Article translations
Article ID: 926335 - View products that this article applies to.
Bug#: 481813 (SQLBUDT )
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

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for applying the hotfix package
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package

SYMPTOMS

In Microsoft SQL Server 2005, you may receive the following error message:
Msg 942, Level 14, State 4, Line 1
Database <DatabaseName> cannot be opened because it is offline.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed
This problem occurs if the following conditions are true:
  • In SQL Server Profiler, you are running a trace on the Audit Database Management event.

    Note C2 audit also collects the Audit Database Management event.
  • You run the following Transact-SQL query to bring an offline database online:
    alter database <DatabaseName> set online

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have SQL Server 2005 Service Pack 1 (SP1) installed on the computer. For more information about how to obtain SQL Server 2005 Service Pack 1, 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

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005, 32-bit versions

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2196.0398,11205-Oct-200613:11x86
Microsoft.analysisservices.adomdclient.dll9.0.2196.0543,52005-Oct-200613:11x86
Microsoft.analysisservices.deploymentengine.dll9.0.2196.0138,01605-Oct-200613:11x86
Microsoft.analysisservices.dll9.0.2196.01,215,26405-Oct-200613:11x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2196.075,55205-Oct-200613:11x86
Microsoft.sqlserver.sqlenum.dll9.0.2196.0908,06405-Oct-200613:11x86
Msasxpress.dll9.0.2196.022,30405-Oct-200613:11x86
Msgprox.dll2005.90.2196.0197,92005-Oct-200613:11x86
Msmdlocal.dll9.0.2196.015,609,63205-Oct-200613:11x86
Msmdredir.dll9.0.2196.03,990,30405-Oct-200613:11x86
Replprov.dll2005.90.2196.0547,61605-Oct-200613:11x86
Replrec.dll2005.90.2196.0782,11205-Oct-200613:11x86
Sqlaccess.dll2005.90.2196.0347,93605-Oct-200613:11x86
Sqlagent90.exe2005.90.2196.0319,26405-Oct-200613:11x86
Sqlservr.exe2005.90.2196.028,964,69605-Oct-200613:11x86
Xpstar90.dll2005.90.2196.0292,64005-Oct-200613:11x86
Xpstar90.rll2005.90.2196.0152,86405-Oct-200613:11x86

SQL Server 2005, 64-bit version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2196.0522,52806-Oct-200613:26x64
Microsoft.analysisservices.adomdclient.dll9.0.2196.0543,52005-Oct-200613:11x86
Microsoft.analysisservices.adomdclient.dll9.0.2196.0543,52006-Oct-200613:26x86
Microsoft.analysisservices.deploymentengine.dll9.0.2196.0138,01605-Oct-200613:11x86
Microsoft.analysisservices.dll9.0.2196.01,215,26405-Oct-200613:11x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2196.075,55205-Oct-200613:11x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2196.091,42406-Oct-200613:26x64
Microsoft.sqlserver.sqlenum.dll9.0.2196.0875,29606-Oct-200613:26x86
Msasxpress.dll9.0.2196.022,30405-Oct-200613:11x86
Msasxpress.dll9.0.2196.027,42406-Oct-200613:26x64
Msgprox.dll2005.90.2196.0259,36006-Oct-200613:26x64
Msmdlocal.dll9.0.2196.015,609,63205-Oct-200613:11x86
Msmdredir.dll9.0.2196.03,990,30405-Oct-200613:11x86
Replprov.dll2005.90.2196.0745,24806-Oct-200613:26x64
Replrec.dll2005.90.2196.01,008,41606-Oct-200613:26x64
Sqlaccess.dll2005.90.2196.0355,10406-Oct-200613:26x86
Sqlagent90.exe2005.90.2196.0390,94406-Oct-200613:26x64
Sqlservr.exe2005.90.2196.039,351,58406-Oct-200613:26x64
Xpstar90.dll2005.90.2196.0540,96006-Oct-200613:26x64
Xpstar90.rll2005.90.2196.0153,37606-Oct-200613:26x64

SQL Server 2005, Itanium architecture version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.2196.01,095,45605-Oct-200617:15IA-64
Microsoft.analysisservices.adomdclient.dll9.0.2196.0543,52005-Oct-200613:11x86
Microsoft.analysisservices.adomdclient.dll9.0.2196.0543,52005-Oct-200617:15x86
Microsoft.analysisservices.deploymentengine.dll9.0.2196.0138,01605-Oct-200613:11x86
Microsoft.analysisservices.dll9.0.2196.01,215,26405-Oct-200613:11x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2196.075,55205-Oct-200613:11x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2196.0163,10405-Oct-200617:15IA-64
Microsoft.sqlserver.sqlenum.dll9.0.2196.0875,29605-Oct-200617:15x86
Msasxpress.dll9.0.2196.022,30405-Oct-200613:11x86
Msasxpress.dll9.0.2196.055,07205-Oct-200617:15IA-64
Msgprox.dll2005.90.2196.0542,49605-Oct-200617:15IA-64
Msmdlocal.dll9.0.2196.048,592,67205-Oct-200617:15IA-64
Msmdredir.dll9.0.2196.06,244,64005-Oct-200617:15IA-64
Replprov.dll2005.90.2196.01,617,18405-Oct-200617:15IA-64
Replrec.dll2005.90.2196.02,141,47205-Oct-200617:15IA-64
Sqlaccess.dll2005.90.2196.0349,47205-Oct-200617:16x86
Sqlagent90.exe2005.90.2196.01,143,58405-Oct-200617:16IA-64
Sqlservr.exe2005.90.2196.072,240,92805-Oct-200617:16IA-64
Xpstar90.dll2005.90.2196.0951,07205-Oct-200617:10IA-64
Xpstar90.rll2005.90.2196.0152,35205-Oct-200617:15IA-64

WORKAROUND

To work around this problem, use one of the following methods:
  • Do not run SQL Server Profiler to capture the Audit Database Management event when you try to bring the DatabaseName database online.

    Note This event is also included in the C2 audit trace, and it cannot be removed if you turn on the C2 audit trace. Therefore, you must turn off the C2 audit trace.
  • Run the sp_detach_db stored procedure to detatch the database, and then run the sp_attach_db stored procedure to attach the database.

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, 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: 926335 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
Keywords: 
kbautohotfix kbsql2005engine kbHotfixServer kbqfe KB926335

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