System Center Service Manager: Reporting Data Warehouse Management Server is currently unavailable
June 13, 2011
Posted by on
Having just completed a day of patching all of the Windows servers, I was somewhat dismayed to fire up my Service Manager Console and get an advisory from the application that the Reporting Data Warehouse Management Server was unavailable.
A quick RDP to the server showed that it was alive and kicking, and had good network connectivity to the Service Manager server and the SQL server.
Reading the SCSM Engineering Team’s blog on troubleshooting the RDWMS had as its first suggestion: Start with the Operations Manager event log on the Data Warehouse server.
Opening up the event log allowed me to quickly spot this error:
OpsMgr Config Service has lost connectivity to the OpsMgr database, therefore it can not get any updates from the database. This may be a temporary issue that may be recovered from automatically. If the problem persists, it usually indicates a problem with the database. Reason:
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: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)
I then remembered that I had been working on the SQL server last of all. Clearly there are some applications that require a restart after the SQL server has been unavailable. A reboot of the data warehouse server and Service Manager was much happier.