FIX: SQL Server Profiler stops monitoring the instance after a time when you use SQL Server Profiler to monitor an instance of SQL Server 2005 Analysis Services

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

When you use SQL Server Profiler to monitor an instance of Microsoft SQL Server 2005 Analysis Services, SQL Server Profiler stops monitoring the instance after a time.

This problem occurs if the following conditions are true:

• The value of the AdminTimeout property for the instance is not 0.
• The value of the ServerTimeout property for the instance is larger than 0.

For example, if the value of the AdminTimeout property is 3,600, SQL Server Profiler stops monitoring the instance after 1 hour.

This problem occurs because SQL Server Profiler uses a time-out value that is the same as the value of the ServerTimeout property for the instance.

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.

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

To apply this hotfix, you must have SQL Server 2005 Service Pack 1 (SP1) installed. For information about how to obtain SQL Server 2005 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You must restart the SQL Server service 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 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 version

SQL Server 2005 x64-based version

SQL Server 2005 Itanium architecture version

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

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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the AdminTimeout property and the ServerTimeout property for an instance of Analysis Services, visit the following Microsoft Developer Network (MSDN) Web site: This hotfix is also included in the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base: