Yesterday evening I had finally some time to install the Beta 2 of SCCM2012. I created my own VNEXT.LOCAL network and I was ready for the installation.
I followed the wizard and started the installation. After 0,5 hour waiting on the following status:
I canceled the installation and started my investigation in the ConfigMgr Setup Log file on the C:. The last 2 entries were:
Creating SQL Server machine certificate for Server [VNEXT-DB01]…
INFO: VNEXT-CM01.VNEXT.LOCAL’ is a valid FQDN.
So the installation was doing with my SQL server and that action had broken my SQL server. See the status below:
In the Event Viewer on the SQL server I found the following errors:
Unable to load user-specified certificate. The server will not accept a connection. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online.
For more information, see Help and Support Center at http://support.microsoft.com.
TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
For more information, see Help and Support Center at http://support.microsoft.com.
I removed the SSL Certificate from the SQL Server, after that I was able to start the SQL Server. So the problem was the certificate. I searched the Microsoft Connect site for a solution and found one. The solution was to grant the SQL Server service account read rights on the private key of the certificate. To do this follow the steps below:
2. Add the Certificates snap-in (Note: Select computer account and Local computer in the two pages on the wizard that appears.
4. Expand Certificates (Local Computer) -> Personal -> Certificates and find the SSL certificate which SCCM created.
5. Right click on the imported certificate and click All Tasks -> Manage Private Keys.
6. Click the Add button and add the SQL service account name with Read permissions.
When the SQL server is started the installation of SCCM will continue..
Thanks heaps
I've been attempting to install for 2 days now with no joy.
I originally had an SQL 2008R2 server with another instance of SQL 2008 SP1 U13 (U10 failed prereq checks). This never finished installing, hanging at a point and saying
“Setup failed to configure SQL Service Broker. Possible cause: Each Configuration Manager site must have its own SQL Server instance. Verify that the SQL Server instance is not in use by another Configuration Manager site.”
I then created a new SQL server running only SQL 2008 SP1 U13 and during install had the error you mentioned. Your fix worked, and the install completed, so I very happy.
I think I can conclude that the install works only onto a SQL server with only one instance of SQL running (or maybe several instances of the same version?), and that the install needs a fix so that the SQL service account has the correct permissions to the certificate.
Cheers