I have a reporting services application that is returning an error running a report which uses an MDX query. This same report is running successfully on other systems using Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64). But this system returning the error is using this version: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64). I'm inclined to think that R2 is using different rules for the parameter because the position indicated below (4,33) is date parameter (@Date), and the same report is running fine in SP1. When I run the report via the report manager, this syntax below returns the error shown at position (4,33) which is the position of @Date. linkmember(StrToMember(@Date).parent.lag(4).firstChild,[Origination Date].[Date]) ApplicationException: Error processing alert report ...: System.Web.Services.Protocols.SoapException: An error has occurred durning report processing. --> Microsoft .ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. --> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset '...'. --> Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseExceition: Query(4,33) Parser: The syntax for 'Date' is incorrect. At Microsoft.ReportingServices.WebServer.ReportExecution2005Impl.InternalRender(String format, String deviceInfo, PageCountMode pageCountMode, Stream &Result, String& Extension, Strint& Mimetype, String&Encoding, Warning[]& Warnings, String[]& StreamIds) I pulled the MDX out of the report definition and replaced the date parameter with a dimension member as shown below and the MDX query does run successfully in a query window. linkmember([Origination Date].[Date].&[20101004].parent.lag(4).firstChild,[Origination Date].[Date]) Note that these reports were created in a 2005 Reporting Services project and have not been opened or edited using VS 2008. This has been working fine using SQLServer 2008 SP1!

Do you happen to have an older RS server version on which you could try this out? Sometimes the data supplied to @Date might have changed causing it to no longer be valid input. Another way to check is to create a dummy report which outputs the value of @Date to a text box, and then paste that into the same function in an MDX query editor and see if the query runs. If you have ruled out input data as the cause, then I suggest you call Customer Support Services so they can investigate the root cause (I'm assuming this is a produciton system) and if it is a product bug you will be able to request a Hotfix for it. If it is not critical, then I suggest filing a bug on http://connect.microsoft.com and providing repro steps so we can investigate the root cause. Hope this helps, -LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights.