Failed to enumerate SSL bindings error code 234

Question

Does anyone know how to solve this problem?

Replication when you enter the following command in PowerShell.

dir iis:\sslbindings 

I came across this page in Microsoft TechNet , which does not solve the problem.

Edit

When I call a command, I get an error

failed to list SSL bindings

Apparently due to a damaged registry?

Answer 1

Sorry for the delay, but I solved the problem with the following script (see below). For some bizarre reason (I don’t know why), something added two entries to my registry, and after fixing them, the problem disappeared. I realized this by comparing my registry with another machine that did not have this problem, and found the culprit.

 Remove-ItemProperty -Path "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters\SslBindingInfo\" -Name "[::1]:26143" -ErrorAction SilentlyContinue Remove-ItemProperty -Path "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters\SslBindingInfo" -Name "127.0.0.1:26143" -ErrorAction SilentlyContinue echo "Done." 

@Bewc I believe that you are on something there, although I think that this affects not only WCF services. We have a powershell script that builds and deploys a website on a machine (it sounds crazy that I know). Who or what creates these records, I have no idea, but maybe some background process in IIS?

Answer 2

In my case, I have an error when I had both SslCertStoreName and DefaultSslCtlStoreName in the registry. I deleted DefaultSslCtlStoreName and the error went away for a while. For some reason, DefaultSslCtlStoreName was again created in the registry, and I got an error again. So I wrote a simple powershell script that removes it.

This is part of my build script.

 function CleanupSslBindings() { $sslBindingsPath = 'hklm:\SYSTEM\CurrentControlSet\services\HTTP\Parameters\SslBindingInfo\' $registryItems = Get-ChildItem -Path $sslBindingsPath | Where-Object -FilterScript { ($_.Property -eq 'DefaultSslCtlStoreName')} If ($registryItems.Count -gt 0) { ForEach ($item in $registryItems) { $item | Remove-ItemProperty -Name DefaultSslCtlStoreName Write-Host "Deleted DefaultSslCtlStoreName in " $item.Name } } Else { Write-Host "No DefaultSslCtlStoreName found. The SSL Bindings registry is clean." } } 

Answer 3

In my case, I had built-in WCF services hosted as Windows services. When I did this, I apparently did not know (and still do not know) how to assign things like appid (noticeable when you netsh http show sslcert), and other things that arise ... including The item associated with this error.

Essentially, I read the same page as the OP: https://social.technet.microsoft.com/Forums/windowsserver/en-US/87b1252d-a6a0-4251-bbb6-38e104a8c07a/enumerating-iissslbindings-gives-failure -on-one-machine-works-on-another? forum = winserverpowershell

... and using regedit, went to the key: HKLM \ System \ Currentcontrolset \ services \ http \ parameters \ sslbindinginfo

I saw all the same entries that I see when I do the netsh command above. However, my wcf services are listed first, followed by my IIS sites. None of my wcf services had an SSLCertStoreName key (only on IIS sites had a key). Following the explanation of the article, the first entry should have this registry key (this, in my opinion, is an error), I executed the following PowerShell commands:

 Try { Get-ChildItem IIS:\SslBindings } Catch { $1stentry = Get-ChildItem HKLM:\SYSTEM\CurrentControlSet\services\HTTP\Parameters\SslBindingInfo | Select-Object -First 1 $1stentry | New-ItemProperty -Name "SslCertStoreName" -Value "MY" Get-ChildItem IIS:\SslBindings } 

This code works for me. And this article helped me find me and understand that my main reason for this 234 error code is the alleged self-inflicted wound, not installing my WCF services correctly. YMMV. Hope this helps.