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”
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.
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
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:
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, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
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. To create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" section and the online request forms display 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 (http://support.microsoft.com/kb/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.
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.
Contact Microsoft Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
Back to the top
