Error executing reports in RTM Trial

Error executing reports in RTM Trial

• Jacobus

  I have this error, after upgrading from RC to RTM
  any suggestions
  
  

  • An error has occurred during report processing.
    • Query execution failed for data set 'dsWorkItemHistory'.
      • The '20060402' string cannot be converted to the date type.

  
  

• Hilton123

  Hi Florin,

  We changed the format used to store the dates in the warehouse and updated the reports to work properly with the new warehouse date definition; so my guess is that you are trying to open a report from a project that was created with RC(containing the old report definition). Check out the following post for more information on how to update the old reports: http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=331859&SiteID=1

  If you create a new project using the RTM bits(and the latest methodology), you should not be seeing this issue.

  Thanks,
  Othmane

  
  

• Ahmad El Kerdi

  In order to manually run the adapters, do the following:

  Log onto the application tier. Browse to http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
  Click on GetWarehouseStatus, and then click the Invoke button. Wait for it to be idle. It should return ProcessingAdapters (pulling data), ProcessingOlap (processing the cube), or Idle.

  Browse to http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
  Click on Run, and then click the Invoke button. This will start the processing of the warehouse. it will return true or false as to whether is started processing (asynchronously).

  You can repeat GetWarehouseStatus to monitor the processing.

  Thanks,
  Othmane

  
  

• Amarendra Behera

  Did this and has resolved errors!!

  "Back up the contents of C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data and then delete it. Run SetupWarehouse -o to recreate the cube, run the adapters, wait and check again"

  Thanks very much

  Giles

  
  

• HLD77

  Are you viewing reports from a project you just created using the new methodology which is part of TFS RTM or are you having this issue with reports from a project you created using TFS Beta3 Refresh

  Either way, ensure that you are using the latest version of the reports.

  Thanks,
  Othmane

  
  

• David Carr

  Thank you, I got it.
  I have to reload all rdl files into each existing project, I did it for one project and it works.
  
  
  
  

• eburke56

  I am having this same problem. I am attempting to go through this proposed solution. The first portion did not solve the problem, and when I delete the contents of C:\PRogram Files\Microsoft SQL Server\MSSQL.2\OLAP\Data, the SetupWarehouse command fails, claiming an error opening a file in that directory...

  Any ideas

  
  

• zoya

  I am also getting this TFSWarehouse Error in the Event Log:

  TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
  Technical Information (for the administrative staff):
  Date (UTC): 25/04/2006 06:57:48
  Machine: UK-DEVTEAM1
  Application Domain: /LM/W3SVC/3/Root/Warehouse-1-127904218554609118
  Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
  Process Details:
  Process Name: w3wp
  Process Id: 5796
  Thread Id: 2072
  Account name: ALGSOFTWARE\TFSSERVICE

  Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: Microsoft.AnalysisServices.OperationException: The following system error occurred: No mapping between account names and security IDs was done. .

  at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
  at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
  at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
  at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
  at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
  at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options)
  at Microsoft.TeamFoundation.Warehouse.OlapCreator.CreateOlap(WarehouseConfig whConf, String accessUser, String dataReaderAccount, Boolean dropDB)
  at Microsoft.TeamFoundation.Warehouse.AdapterScheduler.EnsureCubeIsUpToDate()

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  
  

• Loise

  Othmane,

  I get the same error as for the Builds report when I execute the SQL you suggested.

  Executing the query ...
  Query (18, 3) The ALLMEMBERS function expects a hierarchy expression for the argument. A member expression was used.
  Execution complete
  

  Results from Running some of the reports:

  Actual Quality vs Planned Velocity-No Errors, but no data

  Bug Rates-An error has occurred during report processing. (rsProcessingAborted)
  Query execution failed for data set 'PriorityParam'. (rsErrorExecutingCommand)
  Query (19, 3) The ALLMEMBERS function expects a hierarchy expression for the argument. A member expression was used.

  Bugs by Priority-No errors but no data

  Bugs Found Without Corresponding Tests-An error has occurred during report processing. (rsProcessingAborted)
  Query execution failed for data set 'PriorityParam'. (rsErrorExecutingCommand)
  Query (19, 3) The ALLMEMBERS function expects a hierarchy expression for the argument. A member expression was used.

  Project Velocity-An error has occurred during report processing. (rsProcessingAborted)
  Query execution failed for data set 'WorkItemTypeParam'. (rsErrorExecutingCommand)
  Query (19, 3) The ALLMEMBERS function expects a hierarchy expression for the argument. A member expression was used.

  Thanks for your help any other suggestions

  Giles

  
  

• K.Sathishkumar

  Giles,

  Thank you for the details, you seem to have the latest version of the reports. Could you try to run the following MDX query:

  WITH
  MEMBER [Measures].[ParameterCaption] AS
  Iif([Work Item].[Microsoft_VSTS_Common_Priority].CURRENTMEMBER IS [Work Item].[Microsoft_VSTS_Common_Priority].[All],
  "All (No Filter)",
  [Work Item].[Microsoft_VSTS_Common_Priority].CURRENTMEMBER.MEMBER_CAPTION
  )
  MEMBER [Measures].[ParameterValue] AS
  [Work Item].[Microsoft_VSTS_Common_Priority].CURRENTMEMBER.UNIQUENAME
  MEMBER [Measures].[ParameterLevel] AS
  [Work Item].[Microsoft_VSTS_Common_Priority].CURRENTMEMBER.LEVEL.ORDINAL
  SELECT
  {
  [Measures].[ParameterCaption],
  [Measures].[ParameterValue],
  [Measures].[ParameterLevel]
  } ON COLUMNS,
  {
  [Work Item].[Microsoft_VSTS_Common_Priority].AllMembers
  } ON ROWS
  FROM [Team System]

  In order to do that, open SQL Server Management Studio and connect to Analysis services on your DT. Click on the TFSWarehouse database and press "New Query" in the toolbar. Then paste the query and run it.

  What results are returned

  Also are any other reports working

  Thanks,
  Othmane
  

  
  

• leahcimp

  I am trying to view reports created from a new project based on MSF Agile Develoment Version 4 on a fresh install of TFS RTM on a new server, this is not an upgrade from the Beta Refresh 3.

  How do I determine whether I am using the latest version of the reports

  Best Regards

  Giles

  
  

• gogson

  Giles,

  From the details posted above, your reports are fine, the issue you are seeing is around the cube which is not able to process certain changes (including setting up the priority dimension attribute which is what the reports are complaining about). Let's try the following:

  - Stop and restart SQL Server Analysis Services Service and then re-run the adapters and ensure that they are done running and processing the OLAP and check to see if it is working and if you see any errors in the event log.

  If this does not solve it, try this:

  - Back up the contents of C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data and then delete it. Run SetupWarehouse -o to recreate the cube, run the adapters, wait and check again.

  Let me know how this goes or if you need more detailed steps.

  Thanks,
  Othmane

  
  

• A.G

  Sorry, how do I re-run the adapters
  
• Error executing reports in RTM Trial