none
Formula member name xxx is not valid. RRS feed

  • Question

  • Hi,

    I'm bringing a simple, yet strange problem.

    We use reporting services to acess analysis services 2000. one simple dataset of a report has been working for years, however not working recently. And I have no clue what happened.

    The query is as simple as below:

    "

    With

    MEMBER Measures.DateKey as '[Financial Calendar].CurrentMember.UniqueName'

    MEMBER Measures.DateName as 'Space([Financial Calendar].CurrentMember.Level.Ordinal*0) + [Financial Calendar].CurrentMember.Name'

    Select

    {Measures.DateKey, Measures.DateName} on Columns,

    [Week].Members on Rows

    FROM [Product Sales and Inventory]

    "

    What is strange is that the report is still working if run on demand, but not as scheduled. Even if the corresponding sql job is manually called, the error is found in the SSRS log file:

    "

    ReportingServicesService!processing!1d8!10/05/2010-12:04:14:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing., ;
     Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'paramWeek'. ---> System.Data.OleDb.OleDbException: Formula member name Measures.DateKey is not valid.
       at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(Int32 hr)
       at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForMultpleResults(tagDBPARAMS dbParams, Object& executeResult)
       at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)
       at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)
       at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
       at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior)
       at System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
       at Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(CommandBehavior behavior)
       at Microsoft.ReportingServices.ReportProcessing.a1.v()
       --- End of inner exception stack trace ---

    "

     

    It shows the calculated member "Measures.DateKey" is not valid. But why it's working if the report is run manually? and why it has been valid for so many years??

    btw, the mdx query is perfectly working if run in report design mode or ProClarity.

     

    Any thoughts would be much appreciated.

    Monday, May 10, 2010 5:01 AM

Answers

  • The problem has been sorted out finally..The root cause was actually one of the base cubes didn't get processed correctly, which caused that member to be invalid in the context, thus failed report rendering.
    • Marked as answer by WII Tuesday, May 11, 2010 3:37 AM
    Tuesday, May 11, 2010 3:37 AM

All replies

  • Should I post it to Reporting Services forum?
    Monday, May 10, 2010 11:06 PM
  • The problem has been sorted out finally..The root cause was actually one of the base cubes didn't get processed correctly, which caused that member to be invalid in the context, thus failed report rendering.
    • Marked as answer by WII Tuesday, May 11, 2010 3:37 AM
    Tuesday, May 11, 2010 3:37 AM