Skip to main content

IIS Manager Error: A specified logon session does not exist. It may already have been terminated.

Last week I was configuring a TFS 2012 server to support https. I installed a wildcard SSL certificate on our Windows 2008 Server trying to install a wildcard SSL cert.  I launched the Certificate Snap-in inside MMC and placed the SSL certificate into the local computer repository without problems.

But when I opened the IIS manager to use this certificate, the problems started. I wanted to enable SSL for the TFS website, so I selected the web site and choose the Bindings option from the action menu.

image

The site bindings window was loaded. I clicked Add… to add a new binding and choose https from the Type dropdown.

image

But when I tried to select the certificate from the SSL certificate dropdown, I got the following error message:

A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520)

I could click OK but the binding didn’t work.

On the IIS forums I found the following post mentioning two possible solutions:

  • Deleting the certificate and reinstalling it via mmc certificate snap-in
  • Installing the certificate with ‘Mark exportable’ is true

I already used the first option, so I tried the second solution and it worked!

Remark: In the same post someone mentions that making your private key exportable is a security risk. So if someone has a better solution, feel free to let me know.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...