Home Dashboard Directory Help
Search

SQL Server Clustered Instance SSL Certificate removal by Miron contrib


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 789923
Opened: 6/11/2013 11:47:49 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Had to manually remove certificate entry at

\\computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERvER\MSSQLServer\SuperSocketNetLib

Certificate entry.

Clearing certificate settings using Sql Server Configuration Manager turned out to have no effect.
Certificate was failing clustered instance startup.
Hence, seeing instance failing startup after clearing certificate settings using Sql Server Configuration Manager brought about additional check.
After clearing registry entry manually instance started with no issues.
It would be nice if Sql Server Configuration Manager could handle the task.
Details
Sign in to post a comment.
Posted by Microsoft on 11/8/2013 at 12:13 PM
I have not been able to repro this on build 11.0.2100.60.
Step 1. Create cert
Step 2. Install cert
Step 3. Open SQL-CM and select cert.
Step 4. Apply and close -- verify in regedit... it's there.
Step 5. Open SQL-CM and press [clear]
Step 6. Apply and close -- verify in regedit... it's gone.

Have not been able to repro on older and newer builds as well. Right now I cannot follow up, so closing this. Please reactivate if you have more data on this. Also please check whether you have suffient rights.
Thanks,
Michiel
Posted by Microsoft on 11/6/2013 at 5:42 PM
Hi, I have not been able to reproduce this issue on a recent build. Can you verify that you indeed have the rights to the registry entry for removal? I presume you are aware of the steps -- you need to click clear, apply, and then exit, and restart the service.
Thanks,
Michiel
Posted by Microsoft on 6/17/2013 at 11:08 AM
Hello Miron. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Sign in to post a workaround.