Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
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 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.
This article describes the following about this hotfix release:
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.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 System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
Cumulative update informationThe 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:
936305Note 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:
(http://support.microsoft.com/kb/936305/LN/ )Cumulative update package 2 for SQL Server 2005 Service Pack 2
937137Microsoft 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.
(http://support.microsoft.com/kb/937137/LN/ )The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Hotfix 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=supportNote 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.
PrerequisitesTo 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:
(http://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.
Registry informationYou do not have to change the registry.
Hotfix file informationThe 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
SQL Server 2005, x64-based version
Collapse this tableExpand this table
SQL Server 2005, Itanium architecture version
Collapse this tableExpand this table
To work around this problem, use one of the following methods:
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:
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates