Respondida Error Processing the TFS OLAP cube

  • dimanche 1 mai 2011 18:35
     
     

    Getting the below error, please help :

    Errors and Warnings from Response
        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.
       .....

    I am not sure if it is related to having a custom database name.

    Thanks


Toutes les réponses

  • mardi 3 mai 2011 07:00
    Modérateur
     
     

    Hello p_shah,

    Thanks for your post.

    Could you please try following steps to deal with the issue you are facing?

    1). Please make sure the SQL Server service’s status is “Running”. And then enable TCP/IP in SQL Server Configuration, and at the same time, enable the Remote Connection in the SSMS.

    Please see the following blog for the detailed steps information:

    http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

    2). And what edition of SQL Server are you using? SQL Express 2008 or SQL Standard or some other edition? If you have the SQL Express 2008 for the load testing database, you may get that error. The solution is to uninstall SQL Express 2008 and then rebuild the SQL Analysis database. Please refer to this thread:

    http://social.msdn.microsoft.com/Forums/en-US/tfsreporting/thread/8a740601-3623-442a-ab1b-a14f983c3488

    3). Please try using the SQL Analysis Administrator in the TFS to access the SQL Analysis database. Go to the TFS Administration Console, and go to Reporting node, click Edit link and on the Analysis Services tab, change the access account.

    I hope it can help you. If you still have anything unclear, welcome back.

    Thanks,


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • mardi 3 mai 2011 14:25
     
     
    Thanks Vicky. I will report back after trying the steps you mentioned.
  • mardi 3 mai 2011 14:34
     
     

    Oddly enough, we're experiencing the same thing as of about a week ago, I'm finally able to look into the issue. I'm looking for a TFS 2010 Data Warehouse troubleshooting guide, does one exist?

     

    -Kelly

  • mardi 3 mai 2011 15:59
     
     

    I installed the TFS 2010 Reporting Admin pack, tried pulling up the Cube Status report and I get this:

    An error has occurred during report processing. (rsProcessingAborted)

    Query execution failed for dataset 'dsProcessingStatus'. (rsErrorExecutingCommand)

    Invalid object name 'tbl_jobqueue'. 

     

    Any ideas?

  • mercredi 4 mai 2011 12:55
     
     

    I'm the prior two posts, not sure if it will reflect that. I'm still trying to troubleshoot why our dashboards quit showing data and when I tried to do a rebuild from the TFS Admin Console, reporting is now totally down.

    When I call WarehouseControlService.asmx/GetProcessingStatus, here is the beginning of the response I get:

    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_Analysis'. ---> Microsoft.TeamFoundation.Server.WarehouseException: Internal error: The operation terminated unsuccessfully. 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; SSL Provider: The requested security package does not exist ; 08001; Client unable to establish connection; 08001; Encryption not supported on the client.; 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'.

    Locally on the server, if I open up SQL Server Management Studio, Analysis Services, Databases, Tfs_Analysis, Data Sources, I see the Tfs_AnalysisDataSource and it's set to the domain account we are running the TFS server under which has local admin privs (so we should be covered in priviledges). I've retyped the account & password to no avail. I can't see anything wrong with the data source. Any ideas?

     

  • vendredi 6 mai 2011 17:48
     
     

    We ran into this exact issue a couple of months back.  For our issue, the root cause was with how the SQL service account passwords were entered.  Working w/ MS, they asked us to reset our passwords from with SQL Configuration Manager on both the SQL Server and SSAS.  Restarted the corresponding serivces and the warehouse started processing again.

    I can't find the exact reason, but I believe it had to do with the encryption of the password did not work properly if the password was set through the services console.  Once we set the passwords in SQL Config Manager and restarted services all of the warehouse errors went away.

     


    Trevor
  • mardi 10 mai 2011 08:44
    Modérateur
     
     

    Hello p_shah,

    What about your issue now? Does my suggestion help you?

    Thanks,


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

  • mardi 10 mai 2011 15:17
     
      A du code

    No but we upgraded the RAM to 8GB now and we are getting a  different error:

     <?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>2011-05-09T17:41:15.1133581Z</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="Common Structures Warehouse Sync" JobProcessingStatus="Idle">
    
     <LastRun QueueTimeUtc="2011-05-09T17:20:51.023Z" ExecutionStartTimeUtc="2011-05-09T17:20:51.303Z" EndTimeUtc="2011-05-09T17:20:51.563Z" Result="Succeeded" />
    
     <NextRun QueueTimeUtc="2011-05-09T17:50:51.023Z" JobState="QueuedScheduled" />
    
     </Job>
    
    - <Job Name="Full Analysis Database Sync" JobProcessingStatus="Idle">
    
    - <LastRun QueueTimeUtc="2011-05-09T06:00:00Z" ExecutionStartTimeUtc="2011-05-09T06:00:00.987Z" EndTimeUtc="2011-05-09T06:00:07.643Z" Result="Failed">
    
     <ResultMessage>[Full Analysis Database Sync]: ---> AnalysisDatabaseProcessingType=Full, needCubeSchemaUpdate=True. ---> 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_Analysis'. ---> Microsoft.TeamFoundation.Server.WarehouseException: OLE DB error: OLE DB or ODBC error: Invalid column name 'System_ChangedBy__Name'.; 42S22; Invalid column name 'System_ChangedBy__SID'.; 42S22. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'System_ChangedBy' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. Internal error: The operation terminated unsuccessfully. Server: The operation has been cancelled. OLE DB error: OLE DB or ODBC error: Operation canceled; HY008. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'Area Path' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. OLE DB error: OLE DB or ODBC error: Operation canceled; HY008. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'System_Reason' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. OLE DB error: OLE DB or ODBC error: Operation canceled; HY008. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'System_CreatedBy' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. OLE DB error: OLE DB or ODBC error: Operation canceled; HY008. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'Iteration Path' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. OLE DB error: OLE DB or ODBC error: Operation canceled; HY008. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'System_State' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. OLE DB error: OLE DB or ODBC error: Operation canceled; HY008. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'System_AssignedTo' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. OLE DB error: OLE DB or ODBC error: Operation was canceled.. Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'vDimTestCaseOverlay', Name of 'Test Case' was being processed. Errors in the OLAP storage engine: An error occurred while the 'System_Revision' attribute of the 'Test Case' dimension from the 'tfs_Analysis' database was being processed. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, FactCurrentWorkItem', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, FactWorkItemHistory', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, v Fact WorkItem To Tree', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, v Fact Linked Current WorkItem', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact WorkItem To Category', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, v Fact WorkItem Changeset', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact Build Project', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact Build Details', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact Code Churn', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, v Fact Test Result Overlay', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact Build Changeset', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact Build Coverage', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, v Fact WorkItem Test Result', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, v Fact Linked Current Work Item Test Case', has been specified but has not been used. Warning: Parser: Out of line object 'Binding', referring to ID(s) 'tfs_Analysis, Team System, Fact Run Coverage', has been specified but has not been used. at Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ExecuteXmla(String finalXmla) at Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ProcessOlap(AnalysisDatabaseProcessingType processingType, WarehouseChanges warehouseChanges, Boolean lastProcessingFailed, Boolean cubeSchemaUpdateNeeded) --- End of inner exception stack trace --- at Microsoft.TeamFoundation.Warehouse.TFSOlapProcessComponent.ProcessOlap(AnalysisDatabaseProcessingType processingType, WarehouseChanges warehouseChanges, Boolean lastProcessingFailed, Boolean cubeSchemaUpdateNeeded) 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="2011-05-10T06:00:00Z" JobState="QueuedScheduled" />
    
     </Job>
    

  • vendredi 13 mai 2011 02:50
     
     Traitée
  • jeudi 22 mars 2012 18:42
     
     

    Identify the service/account under which the Analysis & Reporting services are running.
    Log onto App-Tier with this account.
    Launch the “SQL Server Management Studio”;
    Connect to the “Database Engine” on the Data Tier. (ensure successful connectivity); Disconnect.
    Connect to the “Analysis Services” on the App Tier. (ensure successful connectivity);Disconnect.

    Logout & then log back in, with say, the admin account of the box. (anything *but* the service account that you just used to log in earlier)

    Manually process the Warehouse & the Analysis using this procedure:
    http://msdn.microsoft.com/en-us/library/ff400237.aspx

    If this does still not work, then ensure that this service/account is a member of “TfsWarehouseDataReader” role.
    Note: This role exists for both the Tfs_Analysis cube as well as Tfs_Warehouse database.

    Next, ensure that this service account is also a member of “TFSEXECROLE” role within the TFS_Warehouse database.

    If all else fails, take a break & contemplate on rebuilding the Warehouse & Anaylsis cube using this procedure:
    http://msdn.microsoft.com/en-us/library/cc668753.aspx

    And remember:
    "Holding on to anger is like grasping a hot coal with the intent of throwing it at someone else; you are the first one who gets burned." - Buddha

  • jeudi 22 mars 2012 18:44
     
     

    Tis link always hangs the browser.. have tried it on several occassions, with both firefox & IE9:

    http://sstjean.blogspot.com/2010/07/tfs-2010-rtm-throws-tf221122-error-when.html

    Please try at your own risk. (My Apologies Vicky).

  • jeudi 22 mars 2012 19:05
     
     
    Just tried it using FF and chrome. Loaded in under a second.