After installing TFS 2010 RC the project dashboard shows a reporting services error “Default value or value provided for the report parameter ‘StateParam’ is not a valid value. (rsInvalidReportParameter)”.
A brief search pointed to the resolution which is to Process the Analysis Database.
There are 2 ways to complete this task.
Using the TFS webservice
1. Logon to the Application Tier for TFS.
2. Browse to http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx or Use IIS Manager to navigate to this URL.
3. Select Process Analysis Database and Invoke a Full processing Type.
Using SQL Management Studio
1. Login to SQL Management Studio
2. Select your TFS Analysis Server under Databases.
3. Right Mouse Click on the Database and select Process.
4. Select Ok.
18 Comments
Carl P
May 10, 2010 at 7:46 pmThanks- This solved an issue I had after a fresh single server installation of TFS.
David
May 10, 2010 at 8:09 pmYour Welcome! Glad to see it was useful to someone else.
Chris
May 11, 2010 at 9:30 amThanks David!!
This is a great article. Saved me hours of hassle! Cheers
Maximilian Raditya
July 2, 2010 at 9:10 amThank you for this! It really works.
Attila
September 1, 2010 at 6:53 pmI do not appear to have a TFS Analysis Server database. Does this imply a problem with the installation of TFS? As far as I can tell the other parts of TFS are working just fine.
FYI SharePoint, TFS, and SQL are all running on the same box.
sevedd
September 10, 2010 at 5:31 pmHi Attila,
Yes you will need to have Analysis Services installed as a prerequisite for installing TFS. I would recommend downloading the TFS Installation Guide and go through all of the items for Installing Prerequisites for Team Foundation Components. The Manually Installing SQL Server for TFS section provides the requirements. Hope this helps.
Victor Gutierrez
September 8, 2010 at 10:34 pmThank you!!!
This is a great article.
Debarghya
October 20, 2010 at 6:57 amThanks a lot. It worked like a charm.
Jeff
December 2, 2010 at 4:06 pmI got this error:
OLE DB error: OLE DB or ODBC error: 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; Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.
sevedd
December 2, 2010 at 4:49 pmHi Jeff,
I am not sure if you have tried a few other resolutions from the web yet, however one that I have come across is the following below from Steve St. Jean. http://sstjean.blogspot.com/2010/07/tfs-2010-rtm-… . This may not be the same for your issue, however it's worth a shot.
Nathan
March 9, 2011 at 5:03 pmThis step should be added to the TFS installation guide! Just went through a clean installation of TFS2010 RTM and of course leave it to Microsoft to not do this step for you and leave you to search the internet. Thank you for alleviating many possible hours of Report Server digging (especially when the issue was in the SSAS!)
Nick
August 30, 2011 at 11:24 amFantastic. Thank you for this.
Igor.Tsyselsky
October 16, 2011 at 2:38 amThanks a lot David.
s.m.
February 17, 2013 at 2:47 amThank You !!
siva
May 22, 2013 at 6:23 amHi david,
I tried both ways but still the issue was not resolved.
what i did:
Procedure one : Invoked Full in ProcessAnalysisDatabase it results follwing
true
then i tried second procedure after some time, but when i click on ” OK ” as specified i got below errors and warning and the status is showing Process Failed.
Tfs_Analysis
ProcessFull
UseExisting
Processing Database ‘Tfs_Analysis’ completed.
Processing Cube ‘Team System’ completed.
Start time: 5/22/2013 6:43:37 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:20
Processing Measure Group ‘Build Changeset’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Build Changeset’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Build Coverage’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Build Coverage’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Build Details’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Build Details’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Build Project’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Build Project’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Code Churn’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Code Churn’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Current Work Item’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:02
Processing Partition ‘Fact Current Work Item’ completed.
Start time: 5/22/2013 6:43:57 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:00
Processing Measure Group ‘Linked Current Work Item’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:02
Processing Partition ‘v Fact Linked Current Work Item’ completed.
Start time: 5/22/2013 6:43:57 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:00
Processing Measure Group ‘Linked Current Work Item Test Case’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:02
Processing Partition ‘v Fact Linked Current Work Item Test Case’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:01
Processing Measure Group ‘Run Coverage’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Run Coverage’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Test’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:02
Processing Partition ‘v Fact Test Result Overlay’ completed.
Start time: 5/22/2013 6:43:57 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:00
Processing Measure Group ‘Work Item’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:02
Processing Partition ‘Fact Work Item History’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Work Item Changeset’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘v Fact Work Item Changeset’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Work Item To Category’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘Fact Work Item To Category’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Work Item To Tree’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:57 PM; Duration: 0:00:02
Processing Partition ‘v Fact Work Item To Tree’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Measure Group ‘Work Item With Result’ completed.
Start time: 5/22/2013 6:43:55 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:01
Processing Partition ‘v Fact WorkItem Test Result’ completed.
Start time: 5/22/2013 6:43:56 PM; End time: 5/22/2013 6:43:56 PM; Duration: 0:00:00
Processing Dimension ‘Test Suite’ completed.
Start time: 5/22/2013 6:44:39 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:00:57
Processing Dimension ‘Work Item’ completed.
Start time: 5/22/2013 6:44:34 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:02
Processing Dimension Attribute ‘(All)’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:44:36 PM; Duration: 0:00:00
Processing Dimension Attribute ‘Area Path’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘Area Team Project Collection’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘Iteration Path’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘Iteration Team Project Collection’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘Previous State’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_AssignedTo’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_ChangedBy’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_ChangedDate__Year’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_CreatedBy’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_Reason’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_Revision’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_State’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_Title’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘System_WorkItemType’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘TeamProjectCollectionSK’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Processing Dimension Attribute ‘TeamProjectSK’ completed.
Start time: 5/22/2013 6:44:36 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:00
Start time: 5/22/2013 6:43:57 PM; End time: 5/22/2013 6:45:36 PM; Duration: 0:01:39
Errors and Warnings from Response
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_WorkItemType’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_ChangedDate__Year’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_Reason’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Previous State’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_Revision’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Area Team Project Collection’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Iteration Team Project Collection’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘TeamProjectCollectionSK’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_AssignedTo’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_CreatedBy’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Area Path’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘TeamProjectSK’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_Title’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Iteration Path’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_ChangedBy’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: 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 ‘vDimWorkItemOverlay’, Name of ‘Work Item’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘System_State’ attribute of the ‘Work Item’ dimension from the ‘Tfs_Analysis’ database was being processed.
Need your Valuable inputs.
David
May 31, 2013 at 5:31 amHi Siva,
The error you are receiving can be related to a number of things, however I would start by verifying that the service account has the correct permissions.
siva
June 10, 2013 at 2:34 amFinally found the solution and now i can generate reports…
The main problem was with SCHEMA CONFLICTS.
First identify which fields are causing schema conflicts, invoke GetWarehouseStatus and observe the XML which fields got conflicted, and in which collection. once you found the filed names then rename the fields with the help of below link.
http://geekswithblogs.net/Natalia/Default.aspx
http://msdn.microsoft.com/en-us/library/ee921480(v=VS.100).aspx
then rebuild your warehouse from tfs admin console, take a back up of old database in sql database and delete it .wait for some time (depends on warehouse time to refresh the cube or check the GetWarehouseStatus next day and check the xml ). to check this use below link
http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus
I spend lot of time to resolve this issue, that’s why posting the solution here, this may help some one… any queries related schema conflicts and Reporting services feel free to post me… iam not a expert but for sure i can help you out in this issues….
Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful.
David
June 11, 2013 at 11:47 amThanks Siva for the update!