Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/926335

From BetaArchive Wiki

Article ID: 926335

Article Last Modified on 11/20/2007



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



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.

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 now 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 service pack that contains this hotfix.

To resolve this problem, 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 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:

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

File name File version File size Date Time Platform
Logread.exe 2005.90.2196.0 398,112 05-Oct-2006 13:11 x86
Microsoft.analysisservices.adomdclient.dll 9.0.2196.0 543,520 05-Oct-2006 13:11 x86
Microsoft.analysisservices.deploymentengine.dll 9.0.2196.0 138,016 05-Oct-2006 13:11 x86
Microsoft.analysisservices.dll 9.0.2196.0 1,215,264 05-Oct-2006 13:11 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2196.0 75,552 05-Oct-2006 13:11 x86
Microsoft.sqlserver.sqlenum.dll 9.0.2196.0 908,064 05-Oct-2006 13:11 x86
Msasxpress.dll 9.0.2196.0 22,304 05-Oct-2006 13:11 x86
Msgprox.dll 2005.90.2196.0 197,920 05-Oct-2006 13:11 x86
Msmdlocal.dll 9.0.2196.0 15,609,632 05-Oct-2006 13:11 x86
Msmdredir.dll 9.0.2196.0 3,990,304 05-Oct-2006 13:11 x86
Replprov.dll 2005.90.2196.0 547,616 05-Oct-2006 13:11 x86
Replrec.dll 2005.90.2196.0 782,112 05-Oct-2006 13:11 x86
Sqlaccess.dll 2005.90.2196.0 347,936 05-Oct-2006 13:11 x86
Sqlagent90.exe 2005.90.2196.0 319,264 05-Oct-2006 13:11 x86
Sqlservr.exe 2005.90.2196.0 28,964,696 05-Oct-2006 13:11 x86
Xpstar90.dll 2005.90.2196.0 292,640 05-Oct-2006 13:11 x86
Xpstar90.rll 2005.90.2196.0 152,864 05-Oct-2006 13:11 x86

SQL Server 2005, 64-bit version

File name File version File size Date Time Platform
Logread.exe 2005.90.2196.0 522,528 06-Oct-2006 13:26 x64
Microsoft.analysisservices.adomdclient.dll 9.0.2196.0 543,520 05-Oct-2006 13:11 x86
Microsoft.analysisservices.adomdclient.dll 9.0.2196.0 543,520 06-Oct-2006 13:26 x86
Microsoft.analysisservices.deploymentengine.dll 9.0.2196.0 138,016 05-Oct-2006 13:11 x86
Microsoft.analysisservices.dll 9.0.2196.0 1,215,264 05-Oct-2006 13:11 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2196.0 75,552 05-Oct-2006 13:11 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2196.0 91,424 06-Oct-2006 13:26 x64
Microsoft.sqlserver.sqlenum.dll 9.0.2196.0 875,296 06-Oct-2006 13:26 x86
Msasxpress.dll 9.0.2196.0 22,304 05-Oct-2006 13:11 x86
Msasxpress.dll 9.0.2196.0 27,424 06-Oct-2006 13:26 x64
Msgprox.dll 2005.90.2196.0 259,360 06-Oct-2006 13:26 x64
Msmdlocal.dll 9.0.2196.0 15,609,632 05-Oct-2006 13:11 x86
Msmdredir.dll 9.0.2196.0 3,990,304 05-Oct-2006 13:11 x86
Replprov.dll 2005.90.2196.0 745,248 06-Oct-2006 13:26 x64
Replrec.dll 2005.90.2196.0 1,008,416 06-Oct-2006 13:26 x64
Sqlaccess.dll 2005.90.2196.0 355,104 06-Oct-2006 13:26 x86
Sqlagent90.exe 2005.90.2196.0 390,944 06-Oct-2006 13:26 x64
Sqlservr.exe 2005.90.2196.0 39,351,584 06-Oct-2006 13:26 x64
Xpstar90.dll 2005.90.2196.0 540,960 06-Oct-2006 13:26 x64
Xpstar90.rll 2005.90.2196.0 153,376 06-Oct-2006 13:26 x64

SQL Server 2005, Itanium architecture version

File name File version File size Date Time Platform
Logread.exe 2005.90.2196.0 1,095,456 05-Oct-2006 17:15 IA-64
Microsoft.analysisservices.adomdclient.dll 9.0.2196.0 543,520 05-Oct-2006 13:11 x86
Microsoft.analysisservices.adomdclient.dll 9.0.2196.0 543,520 05-Oct-2006 17:15 x86
Microsoft.analysisservices.deploymentengine.dll 9.0.2196.0 138,016 05-Oct-2006 13:11 x86
Microsoft.analysisservices.dll 9.0.2196.0 1,215,264 05-Oct-2006 13:11 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2196.0 75,552 05-Oct-2006 13:11 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2196.0 163,104 05-Oct-2006 17:15 IA-64
Microsoft.sqlserver.sqlenum.dll 9.0.2196.0 875,296 05-Oct-2006 17:15 x86
Msasxpress.dll 9.0.2196.0 22,304 05-Oct-2006 13:11 x86
Msasxpress.dll 9.0.2196.0 55,072 05-Oct-2006 17:15 IA-64
Msgprox.dll 2005.90.2196.0 542,496 05-Oct-2006 17:15 IA-64
Msmdlocal.dll 9.0.2196.0 48,592,672 05-Oct-2006 17:15 IA-64
Msmdredir.dll 9.0.2196.0 6,244,640 05-Oct-2006 17:15 IA-64
Replprov.dll 2005.90.2196.0 1,617,184 05-Oct-2006 17:15 IA-64
Replrec.dll 2005.90.2196.0 2,141,472 05-Oct-2006 17:15 IA-64
Sqlaccess.dll 2005.90.2196.0 349,472 05-Oct-2006 17:16 x86
Sqlagent90.exe 2005.90.2196.0 1,143,584 05-Oct-2006 17:16 IA-64
Sqlservr.exe 2005.90.2196.0 72,240,928 05-Oct-2006 17:16 IA-64
Xpstar90.dll 2005.90.2196.0 951,072 05-Oct-2006 17:10 IA-64
Xpstar90.rll 2005.90.2196.0 152,352 05-Oct-2006 17:15 IA-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


Keywords: kbqfe kbpubtypekc kbhotfixserver kbsql2005engine KB926335