I am getting a DuplicateNameException in the latest version of ADOMD.NET with
the latest patch applied. I thought this was a bug that was fixed in this
release. Does anyone know what causes this? The full message I get is:

A DataTable named 'Order Date' already belongs to this DataSet

the query I'm running is:

with set [Autoship 6+] as '{[Autoship Cycle].[6]:[Autoship Cycle].[49]}'
set [Date Range] as 'Generate( {[Shipped Date].[Fiscal].[2005-09-01
00:00:00]:ClosingPeriod( [Shipped Date].[Fiscal].[Date], [Shipped
Date].[Fiscal])}, {Ancestor( [Shipped Date].[Fiscal].CurrentMember, [Shipped
Date].[Fiscal].[Week])} )'
member [Autoship Cycle].[6+] as 'aggregate( [Autoship 6+] )'
member [Measures].[Shipped] as '( [Measures].[Count], [Order
Status].[Shipped] )'
select
{[Autoship Cycle].[0]:[Autoship Cycle].[5], [Autoship Cycle].[6+]} on columns,
non empty [Date Range]
properties [Shipped Date].[Fiscal].[Week].[Week], [Shipped
Date].[Fiscal].[Week].[Year]
on rows
from Orders
where ( [Measures].[Shipped] )

The query runs fine in the MDX sample application. The full stack trace is:

[DuplicateNameException: A DataTable named 'Order Date' already belongs to
this DataSet.]
System.Data.DataTableCollection.RegisterName(Strin g name) +208
System.Data.DataTableCollection.BaseAdd(DataTable table) +127
System.Data.DataTableCollection.Add(DataTable table) +50

Microsoft.AnalysisServices.AdomdClient.MDDatasetFo rmatter.ReadAxesInfo(XmlReader reader) +299

Microsoft.AnalysisServices.AdomdClient.MDDatasetFo rmatter.ReadMDDataset(XmlReader reader) +116

Microsoft.AnalysisServices.AdomdClient.SoapFormatt er.ReadDataSetResponsePrivate(XmlReader reader) +83

Microsoft.AnalysisServices.AdomdClient.SoapFormatt er.ReadExecuteResponsePrivate(XmlReader reader, Boolean throwOnInlineErrors) +86

Microsoft.AnalysisServices.AdomdClient.SoapFormatt er.ReadResponse(XmlReader
reader, Boolean throwOnInlineErrors) +352

Microsoft.AnalysisServices.AdomdClient.XmlaClientP rovider.Microsoft.AnalysisServices.AdomdClient.IEx ecuteProvider.ExecuteMultidimensional(ICommandCont entProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters) +515
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() +60
Intranet.Utility.MyMdCommand.ExecuteReader(Command Behavior behavior) +116
System.Data.Common.DbDataAdapter.FillFromCommand(O bject data, Int32
startRecord, Int32 maxRecords, String srcTable, IDbCommand command,
CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord,
Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior
behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36
Intranet.Reports.ReportBase.Exec(String strQuery, String srcTable,
CommandType cmmType) +284
Intranet.Reports.Accounting.ShippedAndProjectedOrd ers..ctor(HttpContext
context, String sDate, String OrderType) +796

Intranet.Selection.Accounting.ShippedAndProjectedO rders.SetReportObject(Object sender, ReportArgs& e) +65
Intranet.UserControls.ViewerSubmit.GetReport(Repor tArgs& e) +21
Intranet.UserControls.ViewerSubmit.btnSubmit_Click (Object sender,
EventArgs e) +744
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108

System.Web.UI.WebControls.Button.System.Web.UI.IPo stBackEventHandler.RaisePostBackEvent(String eventArgument) +58
System.Web.UI.Page.RaisePostBackEvent(IPostBackEve ntHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCol lection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292