FIX: The metadata of the Description object of a Key Performance Indicator appears in the default language after you define a translation for the Description object in SQL Server 2005 Business Intelligence Development Studio

This article describes the following about this hotfix release:

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

Consider the following scenario. You have a SQL Server 2005 Analysis Services project in SQL Server 2005 Business Intelligence Development Studio. You define a translation for the Description object of a Key Performance Indicator (KPI). Then, you deploy the project to an instance of SQL Server 2005 Analysis Services. In Control Panel, you open Regional and Language Options. Under Standards and formats, you specify the same language that you specify for the translation of the Description object. You try to retrieve the metadata of the Description object. In this scenario, you notice that the metadata always appears in the default language.

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 1 (SP1) installed to apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You have to restart the computer if the installer must replace files that are being used. To avoid restarting the computer, you must close all SQL Server Analysis Services tools and clients. Additionally, you must stop Microsoft Internet Information Services (IIS) if the server is configured to provide HTTP access. If SQL Server Analysis Services is installed as a named instance, you must also stop the SQL Server Browser service because the Msmdredir.dll component of the SQL Server Browser service is updated when you install 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 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.

Steps to reproduce the problem

1. Open the Adventure Works DW Enterprise Edition sample project in SQL Server Business Intelligence Development Studio.
   
   Note For more information about how to install the sample project, visit the following Microsoft Developer Network (MSDN) Web site:
   http://msdn2.microsoft.com/en-us/library/ms143804.aspx (http://msdn2.microsoft.com/en-us/library/ms143804.aspx)
2. Deploy the sample project to an instance of SQL Server 2005 Analysis Services.
3. In Control Panel, open Regional and Language Options.
4. Click the Regional Options tab.
5. Under Standards and formats, select French (France), and then click OK.
6. Open SQL Server Management Studio, and then connect to the instance of SQL Server 2005 Analysis Services.
7. In SQL Server Management Studio, open a new Analysis Services XMLA Query window.
8. Run the following XMLA query:

   <Discover xmlns="urn:schemas-microsoft-com:xml-analysis">
   <RequestType>MDSCHEMA_KPIS</RequestType>
   <Restrictions>
   <RestrictionList xmlns="urn:schemas-microsoft-com:xml-analysis">
   <CUBE_NAME>Adventure Works</CUBE_NAME>
   <KPI_NAME>Growth in Customer Base</KPI_NAME>
   </RestrictionList>
   </Restrictions>
   <Properties>
   <PropertyList>
   <Catalog>Adventure Works DW</Catalog>
   </PropertyList>
   </Properties>
   </Discover>

   Notice that the metadata in the KPI_DESCRIPTION column appears in English.

For more information about the naming schema for Microsoft 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: