M
Mark Sweat
Guest
I'm trying to connect a SSL cert to my http listener application. I'm running on Windows Server 2008 SP2.
I'm using the netsh http command such as the following to do this.
add sslcert ipport=10.0.0.1:443 certhash=somelongcerthash appid={somelongappid}
When I use the command I get the following error message.
SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.
I'm logged onto the server as a domain admin when I run the command.
I previously had this application setup to use SSL on a different port with the same cert, the application ran fine for a few weeks.
I was in the process of switching the application onto port 443 when this error started to occur.
As part of the switch I found the cert was also defined for a web site. I undefined the SSL and port binding for the web site. I reconnected to cert to the old Port and successfully test the application again, then deleted the binding using the "delete sslcert" command and attempt to use the same "add sslcert" command with port 443 and got the failure. Now I can't use the add sslcert command no matter what port I specify without getting the failure message.
Microsoft has a fix for this error message for Windows 7 and Windows Server 2008 R2, but not Windows Server 2008 SP2.
Googling around I see a number of other people that have run into this issue but don't see any remedies that work for me.
--Mark
Continue reading...
I'm using the netsh http command such as the following to do this.
add sslcert ipport=10.0.0.1:443 certhash=somelongcerthash appid={somelongappid}
When I use the command I get the following error message.
SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.
I'm logged onto the server as a domain admin when I run the command.
I previously had this application setup to use SSL on a different port with the same cert, the application ran fine for a few weeks.
I was in the process of switching the application onto port 443 when this error started to occur.
As part of the switch I found the cert was also defined for a web site. I undefined the SSL and port binding for the web site. I reconnected to cert to the old Port and successfully test the application again, then deleted the binding using the "delete sslcert" command and attempt to use the same "add sslcert" command with port 443 and got the failure. Now I can't use the add sslcert command no matter what port I specify without getting the failure message.
Microsoft has a fix for this error message for Windows 7 and Windows Server 2008 R2, but not Windows Server 2008 SP2.
Googling around I see a number of other people that have run into this issue but don't see any remedies that work for me.
--Mark
Continue reading...