I am in the process of installing System Center 2012 R2 Service Manager and running into an issue installing the data warehouse. I have been following the guidance posted to TechNet,but have gotten stuck.
Some background on the environment.
- Running Server 2012 R2 Hyper-V
- The Service Manager topology is four servers: Management Server, Data Warehouse, SQL Cluster
- Management Server is 2012 R2
- Data Warehouse server is 2012 R2
- SQL 2012 SP1 two node cluster with CU 7 installed on the Service Manager Instance
- The instance for Service Manager is a named instance (Not the default)
- Cluster Validation tests have completed with no errors
I was able to successfully install the Management Server with no errors. When I attempt to install the data warehouse server, I get to the point of selecting the SQL server for Analysis Services for OLAP cubes and can not connect to the database server.
I enter the NETBIOS name for the cluster instance as I did in the previous screens, and I get an error that "The server is not available."
Troubleshooting steps taken:
- I have confirmed that the Analysis Service is running and that I can connect to it from Management Studio, both from the SQL cluster nodes and a remote machine. (I had to install CU 7 in order to be able to see permissions from a server running 2012 R2.)
- I've confirmed that the account that the installation is being run from has permissions to both the database engine and analysis services.
- I've restarted the Analysis Services from Failover Cluster Manager.
- I've restarted the SQL Browser Service.
- I've tried moving the instance to the other node (for S&Gs)
- I've rebooted the entire SQL cluster and restarted the installation
- I've performed the manual steps to prepare the remote SQL as outlined in the deployment guide
- I've tried entering the server names in the cluster as apposed to the cluster name and other variations
The only thing I can see in the event viewer that looks related is the following error:
- Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc. (Upon researching this specific error, I'm seeing suggestions to contact Microsoft Support)
Any suggestions of things to check would be greatly appreciated. I'm hoping there's a step I've missed somewhere