See also https://techcommunity.microsoft.com/t5/IIS-Support-Blog/Keyset-does-not-exist-exception-from-HRESULT-0x8009000D-or-or/ba-p/342955 for a more detailed explanation, I ran the iisreset command and my problem was sovled.

Everything worked as expected on the developer machine, yet in the test environment the same code only throws this exception: System.Security.Cryptography.CryptographicException: Keyset does not exist.

Hello highlight.js! I also have Windows 2012, but in my case I had gone from a workgroup to join a domain. your coworkers to find and share information. rev 2020.9.28.37683, Sorry, we no longer support Internet Explorer, Stack Overflow works best with JavaScript enabled, Where developers & technologists share private knowledge with coworkers, Programming & related technical career opportunities, Recruit tech talent & build your employer brand, Reach developers & technologists worldwide. Then I removed everything in %ALLUSERSPROFILE%\Microsoft\Crypto\RSA\MachineKeys, I ran iissetup.exe /install SharedLibraries from the inetsrv directory, which resulted in a "Failed = 0x80070005". This solved the issue for me and saved me from deleting files and registry keys as being recommended in other quoted solutions. How seriously should I take Fulcrum Racing 6DB tubeless tire compatibility warning? I tried to change the Identity of Application Pool on a remote server and it failed with the above error. I just wasted 3 hours until I read your comment! Enter your email address to subscribe to this blog and receive notifications of new posts by email. Looks like the keys themselves were in corrupted state. First open the mmc tool by typing mmc in the search box: Add the certificates snap-in and select Computer account: Expand the tree on the left side (Certificates (Local Computer) / Personal / Certificates), select the Certificates node and locate your certificate. Learn how your comment data is processed.

You should post it as an answer. I gave everyone full control to MachineKeys just to see if that would make a difference. Unfortunately, this didn't work for me. But when I open a command prompt in.

If it does not show up, you are probably in the wrong location. System.Security.Cryptography.CryptographicException: Keyset does not exist. Try this First! That was our problem, but no one explained this as a possible source for the exception. You might also get the below error codes Important: The option to manage private keys is only available for the machine store, not your personal store.

If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. How to force filename completion in shell buffers to use quotes instead of backslashes. I was able to open IIS Management and to change settings, but when I clicked on the "OK" or "Save" button - I got the "Keyset does not exist" - error message. Details: Keyset does not exist (Exception from HRESULT: 0x80090016). Why do I hear water flowing in a floor drain near commercial bathroom fixtures?

Could you please elaborate more your answer adding a little more description about the solution you provide? Especially when you are sure that everything is correctly configured. Once the keys were exported, move them to non-working server and import them using the below commands (we should run these in all the 4 folders mentioned above): 400 Error in ASP.NET Core Project because of 8 KB cookie limit in Angular, What’s new for SQL Server 2019 Reporting Services RC1, App in a Day – SHIFT Consulting – Saudi Arabia, Using Azure Update Management to Automate On-Premises Server Patching, Announcing Windows 10 Insider Preview Build 20185, Power Platform – Power Automate Partner Airlift: Building Automated Flows with Common Data Service. As a workaround we can follow the below article to fix the error by regenerating the machine keys: So I had the same issue as you ebol2000.

After I followed the steps here I started to receive another error..."Value does not fall within the expected range" There is a post here in Stack Overflow: @Dean Marsden - wow!