Ssl certificate add failed error 1312

«SSL Certificate add failed, Error: 1312» error message when you try to add a CTL in Windows Server 2008 R2 or in Windows 7

Symptoms

You try to run the following netsh command on a computer that is running Windows Server 2008 R2 or Windows 7:

netsh http add sslcert ipport= certhash= appid= slctlstorename= sslctlidentifier= Note This command adds a certificate trust list (CTL) to a secure sockets layer (SSL) binding.

However, the operation fails, and you receive an error message that resembles the following:

SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.

Cause

This issue occurs because the Unicode strings in the struct parameters are incorrectly truncated when these strings are passed to a remote procedure call (RPC). Therefore, the authentication operation fails.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Источник

«SSL Certificate add failed, Error: 1312» error message when you try to add a CTL in Windows Server 2008 R2 or in Windows 7

Symptoms

You try to run the following netsh command on a computer that is running Windows Server 2008 R2 or Windows 7:

netsh http add sslcert ipport= certhash= appid= slctlstorename= sslctlidentifier= Note This command adds a certificate trust list (CTL) to a secure sockets layer (SSL) binding.

However, the operation fails, and you receive an error message that resembles the following:

SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.

Cause

This issue occurs because the Unicode strings in the struct parameters are incorrectly truncated when these strings are passed to a remote procedure call (RPC). Therefore, the authentication operation fails.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Источник

«SSL Certificate add failed, Error: 1312» error message when you try to add a CTL in Windows Server 2008 R2 or in Windows 7

Symptoms

You try to run the following netsh command on a computer that is running Windows Server 2008 R2 or Windows 7:

netsh http add sslcert ipport= certhash= appid= slctlstorename= sslctlidentifier= Note This command adds a certificate trust list (CTL) to a secure sockets layer (SSL) binding.

However, the operation fails, and you receive an error message that resembles the following:

SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.

Cause

This issue occurs because the Unicode strings in the struct parameters are incorrectly truncated when these strings are passed to a remote procedure call (RPC). Therefore, the authentication operation fails.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Источник

Ssl certificate add failed error 1312

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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=

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.

Источник

«SSL Certificate add failed, Error: 1312» error message when you try to add a CTL in Windows Server 2008 R2 or in Windows 7

Symptoms

You try to run the following netsh command on a computer that is running Windows Server 2008 R2 or Windows 7:

netsh http add sslcert ipport= certhash= appid= slctlstorename= sslctlidentifier= Note This command adds a certificate trust list (CTL) to a secure sockets layer (SSL) binding.

However, the operation fails, and you receive an error message that resembles the following:

SSL Certificate add failed, Error: 1312
A specified logon session does not exist. It may already have been terminated.

Cause

This issue occurs because the Unicode strings in the struct parameters are incorrectly truncated when these strings are passed to a remote procedure call (RPC). Therefore, the authentication operation fails.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Источник

Getting error
«SSL Certificate add failed, Error: 1312 A specified logon session does not exist. It may already have been terminated»

windows_certificate "C:/tmp/cert/certpfx.pfx" do
  pfx_password "12345"
  user_store false
end
windows_certificate_binding 'Binding' do
  action :create
  name 'CN=www.demo.com'
  name_kind :subject
  store_name "MY"
  port 443
  address '0.0.0.0'
end

After googling find that this is not working due to «Allow Export » is not setting true while import certificate
I can able to install same certificate manually with allow export true

Please help how to resolve this.

also same thing working fine using powershell script

powershell_script 'Cert_install' do
  code <<-EOH
    $securePWD = ConvertTo-SecureString "#{node.run_state['path_values']['certpwd']}" -AsPlainText -Force
    Import-PfxCertificate -FilePath "#{node['br_ics_ppi_app_app']['cert']}/pfx.txt" -CertStoreLocation cert:\LocalMachine\My -Password $securePWD
    Import-Certificate -FilePath "#{node['br_ics_ppi_app_app']['cert']}/certchain.txt" -CertStoreLocation Cert:\LocalMachine\CA
    Import-Certificate -FilePath "#{node['br_ics_ppi_app_app']['cert']}/certroot.txt" -CertStoreLocation Cert:\LocalMachine\Root
    & {iisreset}
  EOH
  notifies :run, 'powershell_script[add_cert_website]', :immediately
  not_if "[bool](dir cert:\LocalMachine\My | ? { $_.subject -like '*#{node.run_state['path_values']['r53privzone']}*'})"
end
powershell_script 'add_cert_website' do
  code <<-EOH
    $cert_name = "#{node.run_state['path_values']['r53privzone']}"
    $cert_name = "*" + $cert_name.Trimend('.') + "*"
    $ssl_web_site_name = "#{node['br_ics_ppi_app_app']['site_name']}"
    $hostname = "#{node.run_state['path_values']['r53privzone']}"
    $hostname = $cert_name.Trimend('.')
    $ssl_web_site_port = 443
    $guid_value = [GUID]::NewGUID().ToString('B')
    $cert_thumb = $null
    $cert_thumb = (Get-ChildItem cert:\LocalMachine\My | where-object { $_.Subject -like $cert_name } | Select-Object -First 1).Thumbprint
    Get-WebBinding -Port $ssl_web_site_port -Name "$ssl_web_site_name" | Remove-WebBinding
    New-WebBinding -Name "$ssl_web_site_name" -IP "*" -Port $ssl_web_site_port -Protocol https
    netsh http show sslcert ipport=0.0.0.0:$ssl_web_site_port
    if ($LASTEXITCODE -eq 1) {
	    netsh http add sslcert ipport=0.0.0.0:$ssl_web_site_port certhash=$cert_thumb appid=$guid_value
    }
    Import-Module WebAdministration
    Stop-WebSite $ssl_web_site_name
    Start-WebSite $ssl_web_site_name
  EOH
  action :nothing
end

We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack.

• Chef Community Slack at http://community-slack.chef.io/.
• Chef Mailing List https://discourse.chef.io/

Support issues opened here will be closed and redirected to Slack or Discourse.