Hello Yesterday we I had a DR with the SCOM Database Server. This Server also holds the Data Warehouse and Reporting Server. The DBA Team brought the Server back on an Alternative Database Server. They brought back the OperationsManager and OperationsManagerDW databases, they could not bring back the Reporting Database SCOM is working in as much the SCOM Console is working and Alerts being received from Server in the normal way. However I have an issue related to the Data Warehouse Server (see the errors below) . I googled these as the advise thus far was to do the following 1: Check firewalls 2: Run the SP_Updatestates stored procedure on the Data Warehouse 3: Check the Run As Profiles The RMS and SQL Server are normally at the same site. As the SQL Server failed the new SQL Server is at another site, although the site is connected by a fast WAN link. The new SQL Server is also hosting the OperationsManager database which appears to to be working OK, i.e. SCOM Console OK and alerts working. Therefore I do not think it is a Firewall issue. I am wondering if it is a performace issue as the SQL Server is now on the otherside of a WAN. Could the issue eb because the Reporting Database was not brought back, even though the Dataware House database was I would be grateful for any advice on how to resolve the this issue I have xxxxxxx out some information below. Thanks in advance Ernie ---------------------------------------------------------------------------------------------------------------------------- Event ID 31561 Failed to enumerate (discover) Data Warehouse objects and relationships among them. The operation will be retried. Exception 'SqlException': A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Discovery.DataSet Instance name: xxxxxxxxxxxxxx Instance ID: {9EBC5397-4F8B-9AF7-D7CA-1E3E88DC51D1} Management group: xxxxxxxxxxxxxx ---------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------- Event ID 31552 Failed to store data in the Data Warehouse. Exception 'SqlException': A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.StandardDataSetMaintenance Instance name: Alert data set Instance ID: {4D6765C1-5C91-B99B-38B6-D1367AB45B74} Management group: xxxxxxxxxxxxxx ---------------------------------------------------------------------------------------------------------------------------- Event ID 31557 Failed to obtain synchronization process state information from Data Warehouse database. The operation will be retried. Exception 'SqlException': A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Synchronization.DomainSnapshot Instance name: xxxxxxxxxxxxxx Instance ID: {9EBC5397-4F8B-9AF7-D7CA-1E3E88DC51D1} Management group: xxxxxxxxxxxxxx ----------------------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------------- Event ID 31569 Report deployment process failed to request management pack list from Data Warehouse. The operation will be retried. Exception 'SqlException': A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report Instance name: xxxxxxxxxxxxxx Instance ID: {9EBC5397-4F8B-9AF7-D7CA-1E3E88DC51D1} Management group: xxxxxxxxxxxxxx ---------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------- Event ID 8000 A subscriber data source in management group LV has posted items to the workflow, but has not received a response in 80 minutes. Data will be queued to disk until a response has been received. This indicates a performance or functional problem with the workflow. Workflow Id : Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData Instance : xxxxxxxxxxxxxx Instance Id : {9EBC5397-4F8B-9AF7-D7CA-1E3E88DC51D1} ----------------------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------------- Event ID 2115 A Bind Data Source in Management Group LV has posted items to the workflow, but has not received a response in 4920 seconds. This indicates a performance or functional problem with the workflow. Workflow Id : Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData Instance : xxxxxxxxxxxxxx Instance Id : {9EBC5397-4F8B-9AF7-D7CA-1E3E88DC51D1} ----------------------------------------------------------------------------------------------------------------------------

HI Check the below troubleshooting guide http://support.microsoft.com/kb/2573329 http://blogs.technet.com/b/kevinholman/archive/2010/08/30/the-31552-event-or-why-is-my-data-warehouse-server-consuming-so-much-cpu.aspx http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/2fe53bbe-65ca-4456-8ca3-547f5fcfcd20/ With the above description, i see there is a network break and the RMS is not able to make the SQL connection. Check in the system log, what happend during those times when the event occured. "Exception 'SqlException': A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections."============================================================ Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Chandan Thanks for the reply much appreciated, I resolved the issue as follows I found the answer (see below) I repoint SCOM to the new SQL Server as far as the OperationsManager database was concerned, but I did not repoint SCOM as far as the OperationsManagerDW database was concerned (hence the errors receive above). Solution as follows 1. Configure the Operations Manager database with the name of the new Data Warehouse server as follows: a. On the server that hosts the Operations Manager database, open SQL Server Management Studio and navigate to Databases, OperationsManager, and then to Tables. b. Right-click dbo.MT_DataWarehouse, and then select Open Table if you are using SQL Server 2005 or select Edit Top 200 Rows if you are using SQL Server 2008. c. Change the value in the MainDatabaseServerName_16781F33_F72D_033C_1DF4_65A2AFF32CA3 column to the name of the new Data Warehouse server. d. Close SQL Server Management Studio to save your changes. 2. Configure the OperationsManagerDW database with the name of the new Data Warehouse server as follows: a. On the new Data Warehouse server, open SQL Server Management Studio and navigate to Databases, OperationsManagerDW, and then to Tables. b. Right-click dbo.MemberDatabase table and select Open Table if you are using SQL Server 2005 or select Edit Top 200 Rows if you are using SQL Server 2008. c. Change the value in the ServerName column to the name of the new Data Warehouse server. d. Close SQL Server Management Studio to save your changes. 3. Restart services as follows: a. On the root management server, restart the System Center Management Configuration Service. b. On all management servers, restart the System Center Management Service. 4. Verify that the database move was successful as described in the following procedures. For more information see http://technet.microsoft.com/en-us/library/cc540368.aspx

Hi Ernie, I was going to suggest to follow those same guides. Worked for you. :-) You can actually re-install sql reporting services, configure it, install SCOM reporting (without the DW database of course) and get the SCOM reporting working again. That is I assume you still have that component down and probably get an alert on that one as well. Most reports come from the management packs anyway and they will automagically load again. Only reports not stored in managemet packs and schedules and stuff will not be there anymore. I have been doing a migration scenario test this week and we hit a lot of these things and also disaster-recovery parts. Very useful. In our case there were not customizations on reporting (we had some reports in custom MP's, happy they were in MP's...). In our case we wanted to do a clean reportserver db config as we were also moving up a version.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient

Hi Bob, Thanks for the good advice as always, The DBA are going to get the original SQL Server back again, and we should get the original reporting services back (we will see). Thanks for the advise, regarding reinstalling the reporting services etc Best regards Ernie

Thanks for this, after weeks of troubleshooting my environment turns out another person had moved the Operations Manager DW DB to another SQL server, all I had to do was:- 2. Configure the OperationsManagerDW database with the name of the new Data Warehouse server as follows: a. On the new Data Warehouse server, open SQL Server Management Studio and navigate to Databases, OperationsManagerDW, and then to Tables. b. Right-click dbo.MemberDatabase table and select Open Table if you are using SQL Server 2005 or select Edit Top 200 Rows if you are using SQL Server 2008. c. Change the value in the ServerName column to the name of the new Data Warehouse server. d. Close SQL Server Management Studio to save your changes. 3. Restart services as follows: a. On the root management server, restart the System Center Management Configuration Service. b. On all management servers, restart the System Center Management Service. 4. Verify that the database move was successful as described in the following procedures.