Team System Developer Center > Visual Studio Team System Forums > Team Foundation Server - Setup > VTS Beta 3 Refresh: I get the following error while viewing reports.
Ask a questionAsk a question
 

AnswerVTS Beta 3 Refresh: I get the following error while viewing reports.

  • Wednesday, November 30, 2005 1:33 PMRoy Tore Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I installed the Beta 3 Refresh on a single computer using SQL Server 2005 Enterprise edition. My setup, service and report users are domain users. Everything seems to work, except Reporting Services.

    I get the same error when running reports from Visual Studio and from SharePoint. The error message looks like this.

    • An error has occurred during report processing. (rsProcessingAborted)
      • Query execution failed for data set 'dsPriorityParam'. (rsErrorExecutingCommand)
        • Query (1, 518) The dimension '[Microsoft_VSTS_Common_Priority]' was not found in the cube when the string, [Microsoft_VSTS_Common_Priority].[Microsoft_VSTS_Common_Priority].[Microsoft_VSTS_Common_Priority], was parsed.


    I have tryed to process the cube, but without any result. Does anyone know what I should do to make this work.

Answers

  • Friday, December 02, 2005 7:07 AMRoy Tore Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    The trick didn't correct the error.

    Processing the cube directly from SQL Server Management Studio was successfully, but it doesn't impact the error. I still get the same error message. I also get the same error when trying to run reports from Visual Studio or directly from SQL Server Reporting Services.

    When opening a report like the "Actual Quality vs Planned Velocity" the report view opens, but there are no values in the Iteration or Area dropdown boxes. If I in example open the "Bug Rates" insted, then I the error message occurs:

    • An error has occurred during report processing. (rsProcessingAborted)
      • Query execution failed for data set 'dsPriorityParam'. (rsErrorExecutingCommand)
        • Query (1, 518) The dimension '[Microsoft_VSTS_Common_Priority]' was not found in the cube when the string, [Microsoft_VSTS_Common_Priority].[Microsoft_VSTS_Common_Priority].[Microsoft_VSTS_Common_Priority], was parsed.

All Replies

  • Thursday, December 01, 2005 6:06 PMAlan Hebert - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    It sounds like there was an error when the system tried to process the cube, and you are stuck in an inconsistent state.  Can you try manually processing the cube from SQL Server Management Studio?  (After connecting to the Analysis Services database, right click on the Team System cube and select process.  You will want to do a full process).  Let me know if that doesn't do the trick.

  • Friday, December 02, 2005 7:07 AMRoy Tore Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    The trick didn't correct the error.

    Processing the cube directly from SQL Server Management Studio was successfully, but it doesn't impact the error. I still get the same error message. I also get the same error when trying to run reports from Visual Studio or directly from SQL Server Reporting Services.

    When opening a report like the "Actual Quality vs Planned Velocity" the report view opens, but there are no values in the Iteration or Area dropdown boxes. If I in example open the "Bug Rates" insted, then I the error message occurs:

    • An error has occurred during report processing. (rsProcessingAborted)
      • Query execution failed for data set 'dsPriorityParam'. (rsErrorExecutingCommand)
        • Query (1, 518) The dimension '[Microsoft_VSTS_Common_Priority]' was not found in the cube when the string, [Microsoft_VSTS_Common_Priority].[Microsoft_VSTS_Common_Priority].[Microsoft_VSTS_Common_Priority], was parsed.
  • Monday, December 12, 2005 6:57 PMAlan Hebert - MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Roy,
    If you are still experiencing the problem, take a look at the "Warehouse Trouble Shooting Guide" here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=154526&SiteID=1.  If you still have problems, let me know.
  • Wednesday, January 04, 2006 1:19 AMBill Essary MSFT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The problem raised in this thread has been identified and a workaround has been documented.  See this post:

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=177409&SiteID=1&mode=1

    The Warehouse Troubleshooting guide (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=154526&SiteID=1) has been updated with a topic describing this problem (OLAP Schema can become out of sync) and is where any updates to the description of symptoms or of the workaround will be posted.