FIX: Error message when you run an MDX query by using the ADOMD.NET data provider in SQL Server 2005 Analysis Services: "Input string was not in a correct format"

Article translations Article translations
Article ID: 933266 - View products that this article applies to.
Bug #: 50000845 (SQL Hotfix)
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 develop a Microsoft .NET Framework 2.0-based application. The application uses the ADOMD.NET data provider in Microsoft SQL Server 2005 Analysis Services. You use the ADOMD.NET data provider to retrieve data from a SQL Server 2000 Analysis Services cube or from a SQL Server 2005 Analysis Services cube. You set the format setting in the Regional and Language Options of the client computer to German. You run a Multidimensional Expressions (MDX) query to select numeric data. In this scenario, you receive the following error message:
System.FormatException was unhandled Message="Input string was not in a correct format." Source="mscorlib" StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Decimal.Parse(String s, NumberStyles style, IFormatProvider provider)
at System.Xml.XmlConvert.ToDecimal(String s)
at Microsoft.AnalysisServices.AdomdClient.FormattersHelpers.ConvertToDecimal(String s)
at Microsoft.AnalysisServices.AdomdClient.FormattersHelpers.ConvertFromXml(String xmlValue, Type targetType, Boolean convertLocalTime)
at Microsoft.AnalysisServices.AdomdClient.FormattersHelpers.ReadRowsetProperty(XmlReader reader, String elementName, String elementNamespace, Type type, Boolean throwOnInlineError, Boolean isArray, Boolean convertToLocalTime)
at Microsoft.AnalysisServices.AdomdClient.AdomdDataReader.ReadColumnValue(Int32 ordinal)
at Microsoft.AnalysisServices.AdomdClient.AdomdDataReader.SequentialReadXmlValue(Int32 ordinal)
at Microsoft.AnalysisServices.AdomdClient.AdomdDataReader.InternalGetValue(Int32 ordinal)
at Microsoft.AnalysisServices.AdomdClient.AdomdDataReader.GetValue(Int32 ordinal)
at Microsoft.AnalysisServices.AdomdClient.AdomdDataReader.GetValues(Object[] values)
at System.Data.ProviderBase.DataReaderContainer.CommonLanguageSubsetDataReader.GetValues(Object[] values)
at System.Data.ProviderBase.SchemaMapping.LoadDataRow()
at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)
at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)
at System.Data.Common.DataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at ADOMDDataRetrivalTest.Form4.GetData() in E:\CustomerData\Edel_ADOMDFormatException\ADOMDDataRetrivalSample\ADOMDDataRetrivalSample\ADOMDDataRetrivalTest\Form4.cs:line 50
at ADOMDDataRetrivalTest.Form4..ctor() in E:\CustomerData\Edel_ADOMDFormatException\ADOMDDataRetrivalSample\ADOMDDataRetrivalSample\ADOMDDataRetrivalTest\Form4.cs:line 40
at ADOMDDataRetrivalTest.Program.Main() in E:\CustomerData\Edel_ADOMDFormatException\ADOMDDataRetrivalSample\ADOMDDataRetrivalSample\ADOMDDataRetrivalTest\Program.cs:line 17
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

RESOLUTION

Cumulative update information

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

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

To apply this hotfix, you must have SQL Server 2005 Service Pack 1 installed. For more information about how to obtain SQL Server 2005 Service Pack 1, 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 do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.adomdclient.dll9.0.2223.0546,16020-Feb-200711:47x86
Microsoft.analysisservices.deploymentengine.dll9.0.2223.0140,65620-Feb-200711:47x86
Microsoft.analysisservices.dll9.0.2223.01,217,90420-Feb-200711:47x86
Microsoft.datawarehouse.dll9.0.2223.01,279,34420-Feb-200711:47x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2223.078,19220-Feb-200711:47x86
Microsoft.sqlserver.sqlenum.dll9.0.2223.0910,70420-Feb-200711:47x86
Msadomdx.dll9.0.2223.0495,47220-Feb-200711:47x86
Msasxpress.dll9.0.2223.024,94420-Feb-200711:47x86
Msmdlocal.dll9.0.2223.015,646,06420-Feb-200711:47x86
Msmdpump.dll9.0.2223.03,986,28820-Feb-200711:47x86
Msmdredir.dll9.0.2223.03,993,96820-Feb-200711:47x86
Msmdsrv.exe9.0.2223.014,627,69620-Feb-200711:47x86
Msmgdsrv.dll9.0.2223.06,000,49620-Feb-200711:47x86
Msolap90.dll9.0.2223.04,265,32820-Feb-200711:47x86
Msolui90.dll9.0.2223.0275,31220-Feb-200711:47x86
SQL Server 2005, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.adomdclient.dll9.0.2223.0546,16020-Feb-200711:47x86
Microsoft.analysisservices.adomdclient.dll9.0.2223.0546,16020-Feb-200701:56x86
Microsoft.analysisservices.deploymentengine.dll9.0.2223.0140,65620-Feb-200711:47x86
Microsoft.analysisservices.dll9.0.2223.01,217,90420-Feb-200711:47x86
Microsoft.datawarehouse.dll9.0.2223.01,279,34420-Feb-200711:47x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2223.078,19220-Feb-200711:47x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2223.0165,74420-Feb-200701:56IA-64
Microsoft.sqlserver.sqlenum.dll9.0.2223.0877,93620-Feb-200701:56x86
Msadomdx.dll9.0.2223.0495,47220-Feb-200711:47x86
Msasxpress.dll9.0.2223.024,94420-Feb-200711:47x86
Msasxpress.dll9.0.2223.057,71220-Feb-200701:56IA-64
Msmdlocal.dll9.0.2223.015,646,06420-Feb-200711:47x86
Msmdlocal.dll9.0.2223.048,718,70420-Feb-200701:56IA-64
Msmdpump.dll9.0.2223.06,733,68020-Feb-200701:56IA-64
Msmdredir.dll9.0.2223.06,249,32820-Feb-200701:56IA-64
Msmdsrv.exe9.0.2223.047,717,23220-Feb-200701:56IA-64
Msmgdsrv.dll9.0.2223.06,000,49620-Feb-200711:47x86
Msmgdsrv.dll9.0.2223.013,056,88020-Feb-200701:56IA-64
Msolap90.dll9.0.2223.04,265,32820-Feb-200711:47x86
Msolap90.dll9.0.2223.07,886,19220-Feb-200701:56IA-64
Msolui90.dll9.0.2223.0275,31220-Feb-200711:47x86
Msolui90.dll9.0.2223.0473,45620-Feb-200701:56IA-64
SQL Server 2005, Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.adomdclient.dll9.0.2223.0546,16019-Feb-200723:51x86
Microsoft.analysisservices.adomdclient.dll9.0.2223.0546,16020-Feb-200711:47x86
Microsoft.analysisservices.deploymentengine.dll9.0.2223.0140,65620-Feb-200711:47x86
Microsoft.analysisservices.dll9.0.2223.01,217,90420-Feb-200711:47x86
Microsoft.datawarehouse.dll9.0.2223.01,279,34420-Feb-200711:47x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2223.094,06419-Feb-200723:51x64
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2223.078,19220-Feb-200711:47x86
Microsoft.sqlserver.sqlenum.dll9.0.2223.0877,93619-Feb-200723:51x86
Msadomdx.dll9.0.2223.0495,47220-Feb-200711:47x86
Msasxpress.dll9.0.2223.030,06419-Feb-200723:51x64
Msasxpress.dll9.0.2223.024,94420-Feb-200711:47x86
Msmdlocal.dll9.0.2223.031,520,11219-Feb-200723:51x64
Msmdlocal.dll9.0.2223.015,646,06420-Feb-200711:47x86
Msmdpump.dll9.0.2223.05,163,37619-Feb-200723:51x64
Msmdredir.dll9.0.2223.03,993,96820-Feb-200711:47x86
Msmdsrv.exe9.0.2223.030,915,95219-Feb-200723:51x64
Msmgdsrv.dll9.0.2223.09,604,97619-Feb-200723:51x64
Msmgdsrv.dll9.0.2223.06,000,49620-Feb-200711:47x86
Msolap90.dll9.0.2223.05,828,97619-Feb-200723:51x64
Msolap90.dll9.0.2223.04,265,32820-Feb-200711:47x86
Msolui90.dll9.0.2223.0323,44019-Feb-200723:51x64
Msolui90.dll9.0.2223.0275,31220-Feb-200711:47x86

WORKAROUND

To work around this problem, use one of the following methods:
  • Set the format setting in the Regional and Language Options of the client computer to English.
  • Set the decimal symbol setting in the format setting in the Regional and Language Options to ".", and set the digital grouping symbol in the format setting in the Regional and Language Options to ",".

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

Properties

Article ID: 933266 - Last Review: June 6, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft SQL Server 2005 Analysis Services
Keywords: 
kbsql2005as kbautohotfix kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbhotfixserver KB933266

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