FIX: Lots of messages that have message ID 19030 and message ID 19031 are logged in the SQL Server 2005 Errorlog file when you use SQL Server Profile in SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by the hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

In SQL Server 2005, lots of messages that have message ID 19030 and message ID 19031 are logged in the SQL Server 2005 Errorlog file. This issue occurs when many SQL Server Profiler traces are started and then stopped. The messages resemble the following:

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: 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

There are no prerequisites for this hotfix.

Restart information

After you apply this hotfix, you do not have to restart the computer if the following conditions are true:

• If SQL Server 2005 Analysis Services is running as a named instance, you stop the SQL Server Browser service before you apply this hotfix.
• You exit all Analysis Services tools and all client applications before you apply this hotfix.
• You exit Microsoft Internet Information Services (IIS) before you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 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 hotfix, 32-bit

SQL Server 2005 hotfix, 64-bit

SQL Server 2005 hotfix, 64-bit for Itanium processors

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

After you apply this hotfix, trace flag 3688 must be turned on when you start the SQL Server service. When trace flag 3688 is turned on, error 19030 and error 19031 are not written to the SQL Server Errorlog file. If trace flag 3688 is not turned on when you start the SQL Server service, this problem still occurs. You must install hotfix build 9.00.2175.00 or a later hotfix build before you can turn on trace flag 3688.

In earlier versions of SQL Server, the sp_altermessage stored procedure can suppress system messages that have message IDs that are less than 50000. When these messages are suppressed, the messages are not written to the SQL Server Errorlog file. However, this behavior is not supported in SQL Server 2005.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: