Team foundation server 2010 warehouse rebuilt

Few days ago suddenly I realised that warehouse database is not being synchronized with latest changes. Tried to rebuilt it using warehouse services. These can be found at url http://localhost:8080/tfs/teamfoundation/administration/v3.0/warehousecontrolservice.asmx of the TFS application server.

Though it didn’t work (This used to work). This time I got following when I checked for GetProcessingStatus

<?xml version=”1.0″ encoding=”utf-8″ ?>

–
<WarehouseProcessingStatus xmlns:xsd=”http://www.w3.org/2001/XMLSchema“ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance“ xmlns=”http://schemas.microsoft.com/TeamFoundation/2005/06/Services/Controller/03“>

<RequestTimeUtc>2010-05-10T12:42:24.4621235Z</RequestTimeUtc>

<WarehouseProcessingOnlineStatus>Started</WarehouseProcessingOnlineStatus>

<AnalysisProcessingOnlineStatus>Started</AnalysisProcessingOnlineStatus>

<JobProcessingStatus>Idle</JobProcessingStatus>

<JobsRunning>0</JobsRunning>

<JobsQueued>0</JobsQueued>

–
<Instance Name=”TEAM FOUNDATION“ JobProcessingStatus=”Idle“ JobsRunning=”0“ JobsQueued=”0“>

–
<Jobs>

–
<Job Name=”Full Analysis Database Sync“ JobProcessingStatus=”Idle“>

–
<LastRun QueueTimeUtc=”2010-05-10T01:00:00Z“ ExecutionStartTimeUtc=”2010-05-10T01:00:01.51Z“ EndTimeUtc=”2010-05-10T01:01:02.72Z“ Result=”Failed“>

<ResultMessage>[Full Analysis Database Sync]: —> AnalysisDatabaseProcessingType=Full. —> Microsoft.TeamFoundation.Server.WarehouseException: TF221122: An error occurred running job Full Analysis Database Sync for team project collection or Team Foundation server TEAM FOUNDATION. —> Microsoft.TeamFoundation.Server.WarehouseException: Failed to Process Analysis Database ‘Tfs_AnalysisServer’. —> Microsoft.TeamFoundation.Server.WarehouseException: Error during OLE DB operation. Error Code = 0xC1060000, External Code = 0x80004005: Login timeout expired HYT00 A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. 08001 SQL Server Network Interfaces: Error getting enabled protocols list from registry [xFFFFFFFF]. 08001. Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘Tfs_AnalysisDataSource’, Name of ‘Tfs_TAnalysisDataSource’. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘Configuration’, Name of ‘Test Configuration’ was being processed. Errors in the OLAP storage engine: An error occurred while the ‘Configuration ID’ attribute of the ‘Test Configuration’ dimension from the ‘Tfs_Analysis’ database was being processed. Internal error: The operation terminated unsuccessfully. Internal error: The operation terminated unsuccessfully. Server: The operation has been cancelled. Error during OLE DB operation. Error Code = 0xC1060000, External Code = 0x80004005: Login timeout expired HYT00 A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. 08001 SQL Server Network Interfaces: Error getting enabled protocols list from registry [xFFFFFFFF]. 08001. Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘Tfs_AnalysisDataSource’, Name of ‘Tfs_AnalysisDataSource’. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘Configuration’, Name of ‘Test Configuration’ was being processed. Errors in the OLAP storage engine: An error occurred while the ‘Configuration Name’ attribute of the ‘Test Configuration’ dimension from the ‘Tfs_Analysis’ database was being processed. Internal error: The operation terminated unsuccessfully. Internal error: The operation terminated unsuccessfully. Error during OLE DB operation. Error Code = 0xC1060000, External Code = 0x80004005: Login timeout expired HYT00 A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. 08001 SQL Server Network Interfaces: Error getting enabled protocols list from registry [xFFFFFFFF]. 08001. Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘Tfs_AnalysisDataSource’, Name of ‘Tfs_AnalysisDataSource’. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘Result’, Name of ‘Test Result’ was being processed. Errors in the OLAP storage engine: An error occurred while the ‘Outcome’ attribute of the ‘Test Result’ dimension from the ‘Tfs_Analysis’ database was being processed. Internal error: The operation terminated unsuccessfully. Internal error: The operation terminated unsuccessfully. Error during OLE DB operation. Error Code = 0xC1060000, External Code = 0x80004005: Login timeout expired HYT00 A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. 08001 SQL Server Network Interfaces: Error getting enabled protocols list from registry [xFFFFFFFF]. 08001. Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘Tfs_AnalysisDataSource’, Name of ‘Tfs_AnalysisDataSource’. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘Result’, Name of ‘Test Result’ was being processed. Errors in the OLAP storage engine: An error occurred while the ‘Resolution State’ attribute of the ‘Test Result’ dimension from the ‘Tfs_Analysis’ database was being processed. Internal error: The operation terminated unsuccessfully. Internal error: The operation terminated unsuccessfully. at Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ExecuteXmla(String finalXmla) at Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ProcessOlap(AnalysisDatabaseProcessingType processingType, WarehouseChanges warehouseChanges) — End of inner exception stack trace — at Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ProcessOlap(AnalysisDatabaseProcessingType processingType, WarehouseChanges warehouseChanges) at Microsoft.TeamFoundation.Warehouse.AnalysisDatabaseSyncJobExtension.RunInternal(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage) at Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.Run(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage) — End of inner exception stack trace —</ResultMessage>

</LastRun>

<NextRun
QueueTimeUtc=”2010-05-10T13:00:00Z“ JobState=”QueuedScheduled” />

</Job>

–
<Job Name=”Incremental Analysis Database Sync“ JobProcessingStatus=”Idle“>

<LastRun
QueueTimeUtc=”2010-05-10T12:32:11.053Z“ ExecutionStartTimeUtc=”2010-05-10T12:32:12.35Z“ EndTimeUtc=”2010-05-10T12:33:35.503Z“ Result=”Succeeded” />

<NextRun
QueueTimeUtc=”2010-05-10T13:02:11.053Z“ JobState=”QueuedScheduled” />

</Job>

</Jobs>

……

…..

So I tried another option to rebuild the warehouse database from scratch using “Team foundation server admin console” utility from application server box. Go to reporting section and click rebuild. This is supposed to rebuild Warehouse and Analysis database.

Using this step warehouse database was rebuilt successfully but Analysis database is not completely rebuild yet. I am able to see only “Team System” cube in the database. Though I am expecting at least five cubes in this database. So I went to Edit option of the above screen, Navigate to Analysis tab and specify new database name.

This step successfully created analysis database as expected with all the cubes etc. Surprisingly this step also changed report server data source connection definition as well and they are pointing to newly created database.