Installing SCOM 2016 (1801) on SQL 2016 Cluster with Cluster Shared Volumes RRS feed

  • Question

  • Hi,

    We're attempting to install SCOM 2016 (1801) to a named instance on a Windows 2016 failover cluster which is using cluster shared volumes and SQL 2016. When I attempt to install the first management server the installation stalls on Configuring Operational Database. When I check the logs I can see

    Error: :Could not create valid path: \\[SQLCLUTERNAME]\C$\ClusterStorage\Database\MSSQL13.SCOM\MSSQL\DATA\: Threw Exception.Type: System.IO.IOException, Exception Error Code: 0x80070043, Exception.Message: The network name cannot be found.

    I can't browse to \\SQLCLUSTERNAME\C$\ClusterStorage however I can to both of the physical nodes \\SQLPHYSICALNODE\C$\ClusterStorage. The SQL Instance will happily failover between nodes from within failover cluster manager and the cluster validation utility is healthy.

    I've confirmed that required firewall ports are open and have local admin access etc. Any help on this would be gratefully received

    Wednesday, March 27, 2019 2:57 PM


All replies

  • Hi,

    You cannot browse to \\SQLCLUSTERNAME\C$... you will need to use the SQL Server cluster role name as the database name, when you are assigning a database during the SCOM installation.

    Here's the steps in high-level:

    - Install SQL Server on the first cluster node (New SQL Server failover cluster installation).

    - During the SQL Server installation, you will select the cluster disk that you want the database instance on.

    - During the SQL Server installation, you will the configure the cluster network configuration (SQL Server cluster role).

    - Install SQL Server on the other cluster node(s) (Add node to a SQL Server failover cluster).

    - When you install SCOM, you will need to select the SQL Server cluster role name as the database server.

    Here's a step-by-step guide on installing SQL Server on a failover cluster with CSV disks:

    Deploy SQL Server with Cluster Shared Volumes – part 2

    Best regards,

    Blog: LinkedIn:

    Wednesday, March 27, 2019 3:28 PM
  • Hi Leon,

    Thanks for the reply, that is the name I'm using which you pointed out in the screenshot above. So using that example I'm unable to browse to 



    • Edited by Bootch_1980 Wednesday, March 27, 2019 3:46 PM
    Wednesday, March 27, 2019 3:46 PM
  • I believe you actually need to install the SCOM DB & DW on normal disks first, because of the error you’re receiving. You should be able to move once it has been installed on a normal disk/NTFS shared disk.

    Is there any specific reason to why you want the SCOM DB & DW stored on a CSV?

    Blog: LinkedIn:

    Wednesday, March 27, 2019 4:04 PM
  • By using CSV's we can have multiple SQL instances on the cluster using the same CSV storage. If we were to use traditional cluster disks we would have to provision new storage for each instance created.
    Wednesday, March 27, 2019 4:21 PM
  • I’ve been advised this issue is because the SCOM installer does a check of the disks on the SQL servers via a remote connection to get back size and path data. It’s unable to complete this against CSV’s. To get round this I completed the SCOM Management Server installs by pointing the install at a temporary single SQL server. Once the install was completed I then migrated the SCOM databases over to the SQL cluster
    Thursday, March 28, 2019 8:53 PM
  • Yes sorry for not getting back to you earlier, this is what I meant by my earlier reply, SCOM requires the SQL Server to be on normal disks, but as mentioned this can later be moved.

    I'm happy to hear you got it as you wanted!

    Blog: LinkedIn:

    Thursday, March 28, 2019 8:57 PM
  • Hi,

    did manage to resolve this one? We would really appreciate your feedback.

    Thanks in advance!


    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: Twitter: @StoyanChalakov

    Tuesday, October 15, 2019 7:19 AM