Article ID: 935360 - Last Review: November 4, 2007 - Revision: 1.4 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"
Bug #: 50000926 (SQL Hotfix) NoticeMicrosoft 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.On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSConsider the following scenario:
An error occurred while the dimension, with the ID of 'DatabaseName', Name of 'DimensionName' was being processed. [Teradata Database] [3939] There is a mismatch between the number of parameters specified and the number of parameters required. CAUSEThis 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. RESOLUTIONHotfix informationA 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
(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
Restart informationYou 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 informationThis hotfix is not replaced by any other hotfixes.Registry informationYou do not have to change the registry.Hotfix file informationThis 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 versionCollapse this table
SQL Server 2005, x64-based versionCollapse this table
SQL Server 2005, Itanium architecture versionCollapse this table
STATUSMicrosoft 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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/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.
| Article Translations
|

Back to the top
