FIX: Error message when you run an MDX query that retrieves data from an Analysis Services database: "An error occurred while the dimension, with the ID of '<DatabaseName>', Name of '<DimensionName>' was being processed"

Article translations Article translations
Article ID: 935360 - View products that this article applies to.
Bug #: 50000926 (SQL Hotfix)
Notice
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.
Expand all | Collapse all

On This Page

SUMMARY

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

SYMPTOMS

Consider the following scenario:
  • You run a Multidimensional Expressions (MDX) query in Microsoft SQL Server 2005 Analysis Services.
  • The query retrieves data from an Analysis Services database that has a relational online analytical processing (ROLAP) partition.
  • The Analysis Services database uses a Teradata database as the relational data source.
In this scenario, you receive the following error message:
An error occurred while the dimension, with the ID of 'DatabaseName', Name of 'DimensionName' was being processed.
In the Teradata database, you receive the following error message:
[Teradata Database] [3939] There is a mismatch between the number of parameters specified and the number of parameters required.

CAUSE

This issue occurs because the Teradata .NET provider cannot process the parameter that is generated by Analysis Services. When the MDX query retrieves data from a ROLAP partition, Analysis Services may generate parameterized SQL queries to retrieve data. If the relational data source is a Teradata database and the data source uses the Teradata .NET provider to connect to the Teradata database, the parameter marker is generated as "@PARAMn." The Teradata .NET provider cannot process parameter markers that have this syntax.

Note The placeholder n represents a number.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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

  • SQL Server 2005 Service Pack 2

    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:
    913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You may have to restart the computer after you apply this hotfix if the Windows Installer must replace files that are being used. Therefore, we recommend that you exit all SQL Server Analysis Services tools and clients. These tools and clients include Internet Information Services (IIS) if the computer is configured to provide HTTP access. Additionally, if you are applying this hotfix to a named SQL instance, we recommend that you stop the SQL Browser service before you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any other hotfixes.

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, x86-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
As80.xslNot applicable16,80109-Apr-200717:53Not applicable
As80.xslNot applicable16,80109-Apr-200718:53Not applicable
As90.xslNot applicable18,29109-Apr-200717:53Not applicable
As90.xslNot applicable18,29109-Apr-200718:53Not applicable
Db2v0801.xslNot applicable29,49709-Apr-200717:53Not applicable
Microsoft.datawarehouse.dll9.0.3162.01,279,34410-Apr-200700:55x86
Msjet.xslNot applicable28,51909-Apr-200717:53Not applicable
Msjet.xslNot applicable28,51909-Apr-200718:53Not applicable
Msmdlocal.dll9.0.3162.015,942,00010-Apr-200700:55x86
Msmdlocal.dll9.0.3162.015,942,00010-Apr-200701:55x86
Msmdspdm.dll9.0.3162.0202,09610-Apr-200700:55x86
Msmdsrv.exe9.0.3162.014,910,32010-Apr-200700:55x86
Msmgdsrv.dll9.0.3162.06,045,55210-Apr-200700:55x86
Msmgdsrv.dll9.0.3162.06,045,55210-Apr-200701:55x86
Msolap90.dll9.0.3162.04,299,63210-Apr-200701:55x86
Orcl7.xslNot applicable32,05809-Apr-200717:53Not applicable
Sql2000.xslNot applicable33,62109-Apr-200717:53Not applicable
Sql2000.xslNot applicable33,62109-Apr-200718:53Not applicable
Sql70.xslNot applicable31,69909-Apr-200717:53Not applicable
Sql70.xslNot applicable31,69909-Apr-200718:53Not applicable
Sql90.xslNot applicable38,95309-Apr-200717:53Not applicable
Sql90.xslNot applicable38,95309-Apr-200718:53Not applicable
Trdtv2r41.xslNot applicable26,91409-Apr-200717:53Not applicable
SQL Server 2005, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
As80.xslNot applicable16,80109-Apr-200717:53Not applicable
As80.xslNot applicable16,80109-Apr-200718:53Not applicable
As90.xslNot applicable18,29109-Apr-200717:53Not applicable
As90.xslNot applicable18,29109-Apr-200718:53Not applicable
Db2v0801.xslNot applicable29,49709-Apr-200717:53Not applicable
Microsoft.datawarehouse.dll9.0.3162.01,279,34410-Apr-200700:55x86
Msjet.xslNot applicable28,51909-Apr-200717:53Not applicable
Msjet.xslNot applicable28,51909-Apr-200718:53Not applicable
Msmdlocal.dll9.0.3162.015,942,00010-Apr-200700:55x86
Msmdlocal.dll9.0.3162.030,826,86410-Apr-200712:14x64
Msmdlocal.dll9.0.3162.015,942,00010-Apr-200701:55x86
Msmdspdm.dll9.0.3162.0202,09610-Apr-200712:14x86
Msmdsrv.exe9.0.3162.030,155,12010-Apr-200712:14x64
Msmgdsrv.dll9.0.3162.09,125,74410-Apr-200712:14x64
Msmgdsrv.dll9.0.3162.06,045,55210-Apr-200701:55x86
Msolap90.dll9.0.3162.05,849,96810-Apr-200712:14x64
Msolap90.dll9.0.3162.04,299,63210-Apr-200701:55x86
Orcl7.xslNot applicable32,05809-Apr-200717:53Not applicable
Sql2000.xslNot applicable33,62109-Apr-200717:53Not applicable
Sql2000.xslNot applicable33,62109-Apr-200718:53Not applicable
Sql70.xslNot applicable31,69909-Apr-200717:53Not applicable
Sql70.xslNot applicable31,69909-Apr-200718:53Not applicable
Sql90.xslNot applicable38,95309-Apr-200717:53Not applicable
Sql90.xslNot applicable38,95309-Apr-200718:53Not applicable
Trdtv2r41.xslNot applicable26,91409-Apr-200717:53Not applicable
SQL Server 2005, Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
As80.xslNot applicable16,80109-Apr-200717:53Not applicable
As80.xslNot applicable16,80109-Apr-200718:53Not applicable
As90.xslNot applicable18,29109-Apr-200717:53Not applicable
As90.xslNot applicable18,29109-Apr-200718:53Not applicable
Db2v0801.xslNot applicable29,49709-Apr-200717:53Not applicable
Microsoft.datawarehouse.dll9.0.3162.01,279,34410-Apr-200700:55x86
Msjet.xslNot applicable28,51909-Apr-200717:53Not applicable
Msjet.xslNot applicable28,51909-Apr-200718:53Not applicable
Msmdlocal.dll9.0.3162.049,870,19210-Apr-200708:09IA-64
Msmdlocal.dll9.0.3162.049,870,19210-Apr-200709:09IA-64
Msmdlocal.dll9.0.3162.015,942,00010-Apr-200701:55x86
Msmdspdm.dll9.0.3162.0202,09610-Apr-200708:09x86
Msmdsrv.exe9.0.3162.048,821,61610-Apr-200708:09IA-64
Msmgdsrv.dll9.0.3162.013,167,98410-Apr-200708:09IA-64
Msmgdsrv.dll9.0.3162.013,167,98410-Apr-200709:09IA-64
Msmgdsrv.dll9.0.3162.06,045,55210-Apr-200701:55x86
Msolap90.dll9.0.3162.07,909,74410-Apr-200709:09IA-64
Msolap90.dll9.0.3162.04,299,63210-Apr-200701:55x86
Orcl7.xslNot applicable32,05809-Apr-200717:53Not applicable
Sql2000.xslNot applicable33,62109-Apr-200717:53Not applicable
Sql2000.xslNot applicable33,62109-Apr-200718:53Not applicable
Sql70.xslNot applicable31,69909-Apr-200717:53Not applicable
Sql70.xslNot applicable31,69909-Apr-200718:53Not applicable
Sql90.xslNot applicable38,95309-Apr-200717:53Not applicable
Sql90.xslNot applicable38,95309-Apr-200718:53Not applicable
Trdtv2r41.xslNot applicable26,91409-Apr-200717:53Not applicable

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 about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, 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
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Properties

Article ID: 935360 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Analysis Services
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB935360

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com