FIX: The Cluster Discrimination tab is empty when you browse a clustering model of SQL Server 2005 Analysis Services in SQL Server BIDS

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 browse a clustering model in Microsoft SQL Server Business Intelligence Development Studio (BIDS), the Cluster Discrimination tab is empty. Additionally, minidump files are generated in the Microsoft SQL Server 2005 Analysis Services log folder. When you trace the Analysis Services service, you receive the following error message:Note In this error message, the word "occured" is a misspelling for the word "occurred."

This problem occurs if the following conditions are true:

• You create a SQL Server 2005 Analysis Services project by using BIDS.
• You create a clustering model that contains one or more input columns.
• In the mining structure, the content type for the input columns is Continuous.
• The training data contains a null value for the input columns.

This issue occurs because the procedure that is used to calculate cluster discriminations for the continuous input columns does not correctly handle the null data.

Cumulative update information

To resolve this problem, obtain cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175). For more information about how to obtain cumulative update package 2 (build 3175), click the following article number to view the article in the Microsoft Knowledge Base:

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

You must have SQL Server 2005 Service Pack 2 installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix. However, the Analysis Services service automatically stops and then restarts when you apply this hotfix.

If the computer on which you apply this hotfix is configured for HTTP access, you must stop Internet Information Services (IIS) before you apply this hotfix. After you apply this hotfix, you must restart IIS.

If Analysis Services is installed as a named instance, you must stop the SQL Server Browser service when you apply this hotfix. You must stop this service because this hotfix updates the Msmdredir.dll component of the SQL Server Browser service.

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.

Microsoft SQL Server 2005 32-bit version

Microsoft SQL Server 2005 x64-based version

Microsoft SQL Server 2005 Itanium-based version

To work around this issue, use one of the following methods:

• Change the content type to Discrete for the input column that contains null training data. You must also change the underlying data from continuous data to discrete data.
• Eliminate the null training data. For example, replace the null values with 0. Or, replace the null values with other values that make sense in the context of the data.

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: