VTS Beta 3 Refresh: I get the following error while viewing reports. - NOT RESOLVED

Question

This is related to the following post:

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

I'm getting the same error.  I have also done a full process on the analysis services (successfully) and followed the troubleshooting guide (successfully).  But still getting the same error.  Any assistance would be appreciated.

Thanks

EJ

Troubleshooting Results

===================

Last Cube Processing

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

12/20/2005 12:30:58 PM

(1 row(s) affected)

LastVCWHWrite

-----------------------

(0 row(s) affected)

LastWITWHWrite

-----------------------

2005-12-16 13:11:37.073

(1 row(s) affected)

WH Revisions

------------

43

(1 row(s) affected)

WIT Revisions

-------------

43

(1 row(s) affected)

WH Changeset

------------

4

(1 row(s) affected)

VC Changeset

------------

4

(1 row(s) affected)

Warehouse Identity Id

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

21

(1 row(s) affected)

Integration Identity Id

-----------------------

21

(1 row(s) affected)

Warehouse Structure Id

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

15

(1 row(s) affected)

Integration Structure Id

------------------------

15

(1 row(s) affected)

 

Answer 1

The warehouse troubleshooting guide is definitely the best place to start for error of this form:

• 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.

Since you have run through those steps, I'll assume that the warehouse adapters are running under the TFSScheduler service and that the cube is processing.  The error itself suggests that some of the dynamic schema changes introduced when new Work Item Types are created did not make it into the OLAP cube. One way to try to fix this problem is to rebuild the OLAP portion of the warehouse using the same command that is used by TFS setup to create warehouse in the first place.

·         First, verify that the dimension member referenced in the error message is actually missing from the OLAP cube:

·        1) Start SQL Server Management Studio

2) Select the menu item: File->Connect Object Explorer

3) Set the server type to Analysis Services and enter the TFS data tier server name

4) In the Analysis Server connection, expand Databases->TFSWarehouse->Dimensions

5) Confirm that Microsoft_VSTS_Common_Priority is not in the list of Dimensions

 

Next, verify that the dimension member is present in the relational part of the warehouse:

1) Using SQL Server Management Studio, select menu item: File->Connect Object Explorer

2) Set the server type to Database Engine and enter the TFS data tier server name

3) In the SQL Server node, expand Databases->TFSWarehouse->Tables->dbo.WorkItem->Columns

4) Confirm that Microsoft_VSTS_Common_Priority is in the column list

 

If both conditions are true, then rebuilding the OLAP portion of the warehouse should solve the problem.

Important: You should back up all OLTP and OLAP data before attempting this procedure.  Failure to back up your data may result in data loss.

1) Back up all data

2) Delete the TFSWarehouse database in Analysis Services

3) From  a command prompt on the TFS Application Tier machine, use the following command (substituting the correct values for your installation in place of the following values: ServerName, Domain\TFSService, Domain\TFSReports):

• %ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Tools\setupwarehouse.exe -o -s ServerName -d TfsWarehouse -c Warehouseschema.xml -a Domain\TFSService -ra Domain\TFSReports

 

Answer 2

Thanks Bill!  It worked.  I pretty sure my domain issues caused the install problem (refer to thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=159181&SiteID=1).

Thanks Again!

EJ

Answer 3

I have to say I have trying for some time now to resolve this on out TFS with no results. But this worked. I had prompted the question in the other TFS forum with no luck.

 

Likewise I had followed the troubleshooting guidance doc from bryanmac. But this did the trick.

 

I recommend this be added to the troubleshooting guide as a last step if nothing else seems to work.

 

THANK YOU!

 

Answer 4

Bill,

I have the same problem, except that the table "dbo.WorkItem" does not exists in TFSWarehouse. I have:

[Work Item Changeset]
[Work Item History]
[Work Item ID]
[Work Item with Result]

but not [WorkItem].

The TFS install completed successfully, so I suppose an error occured during the install but was not reported. I suppose the db created from scripts, not from a db restore. Can I safely find those scripts on the DVD, fix the damaged db, and then rebuild the OLAP db?

Thanks,

Eric

Answer 5

Eric,

 

I had the same circumstance... and still I followed the directions with success. I think perhaps this was in reference to an older schema.

 

 

Answer 6

Michael,

You are absolutely RIGHT! It fixed the problem, so dbo.WorkItem was probably from an old version of the schema.

 

Thanks again.

 

Eric

Answer 7

The Warehouse Troubleshooting Guide has been updated with a description of the symptoms of this problem and the workaround.

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

Answer 8

I'm also running Beta 3 Refresh, and none of the solutions proposed so far get rid of the error with Reporting Services. I've had a look at the warehouseschema.xml and compared it with the dimensions created during installation, and there are a number of dimensions that do not appear in the XML file (e.g. System_WorkItemType). Needless to say, when I rebuild the OLAP database, I no longer get an error regarding [Microsoft_VSTS_Common_Priority], but instead one regarding [System_WorkItemType] (since that dimension no longer exists in the recreated OLAP DB).

I think it's pretty clear that the schema expected by the reporting services is not the same as that initially in the OLAP DB which, in turn, is not the same as the one in warehouseschema.xml. I'm tempted to have a look at the December CTP to see if those issues have been resolved, but the lack of an upgrade path from the CTP to the RTM is stopping me so far.

FWIW, this is the second time I'm installing TFS - the first time everything worked fine, but it was all running on a VM that was accidentally deleted.

Any ideas on what I can do to solve this?

Regards,

Daniel

Answer 9

I am having the same error but with RTM:

 

Here is output after doing the processing on the Analysis cube:

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
  <Parallel>
    <Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <Object>
        <DatabaseID>TfsWarehouse</DatabaseID>
        <CubeID>Team System</CubeID>
      </Object>
      <Type>ProcessFull</Type>
      <WriteBackTableCreation>UseExisting</WriteBackTableCreation>
    </Process>
  </Parallel>
</Batch>
 Processing Dimension 'Microsoft_VSTS_Common_ResolvedBy' completed successfully.
  Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute '(All)' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute 'Microsoft_VSTS_Common_ResolvedBy' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
 Processing Dimension 'Outcome' completed successfully.
  Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute '(All)' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute 'Outcome Passing' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
 Processing Dimension 'Microsoft_VSTS_Common_Discipline' completed successfully.
  Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute '(All)' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute 'Microsoft_VSTS_Common_Discipline' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
 Processing Dimension 'Machine' completed successfully.
  Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute '(All)' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
  Processing Dimension Attribute 'Machine' completed successfully.
   Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
 Processing Dimension 'Build Quality' completed successfully.
  Start time: 4/11/2006 6:34:50 PM; End time: 4/11/2006 6:34:50 PM; Duration: 0:00:00
Errors and Warnings from Response
 Errors in the high-level relational engine. The data source view does not contain a definition for the '__ID' column in the 'Microsoft_VSTS_Common_ResolvedBy' table or view.
 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Microsoft_VSTS_Common_ResolvedBy', Name of 'Resolved By' was being processed.
 Errors in the OLAP storage engine: An error occurred while the 'Microsoft_VSTS_Common_ResolvedBy' attribute of the 'Microsoft_VSTS_Common_ResolvedBy' dimension from the 'TfsWarehouse' database was being processed.
 Errors in the high-level relational engine. The data source view does not contain a definition for the '__ID' column in the 'Microsoft_VSTS_Common_Discipline' table or view.
 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Microsoft_VSTS_Common_Discipline', Name of 'Discipline' was being processed.
 Errors in the OLAP storage engine: An error occurred while the 'Microsoft_VSTS_Common_Discipline' attribute of the 'Microsoft_VSTS_Common_Discipline' dimension from the 'TfsWarehouse' database was being processed.
 Errors in the high-level relational engine. The data source view does not contain a definition for the '__ID' column in the 'Machine' table or view.
 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Machine', Name of 'Machine' was being processed.
 Errors in the OLAP storage engine: An error occurred while the 'Machine' attribute of the 'Machine' dimension from the 'TfsWarehouse' database was being processed.
 Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure.
 Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Outcome', Name of 'Outcome' was being processed.
 Errors in the OLAP storage engine: An error occurred while the 'Outcome Passing' attribute of the 'Outcome' dimension from the 'TfsWarehouse' database was being processed.