Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Stefan Goßner — Fri, 21 Sep 2012 07:03:01 GMT

Hi Chen,

yes - the Debugger will no longer kick in when an application crashes.

So if this is your development machine and you would like to debug application crashes you should Keep the registry keys.

Cheers,

Stefan

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Chen — Fri, 21 Sep 2012 00:07:30 GMT

Hi Stefan,

Is there any side effect if we delete those two registry keys?

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Stefan Goßner — Mon, 19 Sep 2011 06:08:42 GMT

Hi Barkingdog,

I assume you are talking about the dialog box. The dialog box does not talk about the keyset.

The number in "[" "]" is the process id. So that will be different any time you get it.

Cheers,

Stefan

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Barkingdog — Mon, 19 Sep 2011 04:14:26 GMT

I had the same question as Rober. My error is "An unhandled exception:

(‘System.Security.Cryptography.Cryptographicexception’) occurred in OWSTIMER.EXE [1620])

Note his error number was 6832, mine is 1620, and further I have never received a message related to "KeySet does not exist". So are all these actually the same error despite the different error numbers?

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Stefan Goßner — Fri, 20 May 2011 13:41:23 GMT

@Scott: correct. The error is not related to FIM.

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Scott Marcus — Fri, 20 May 2011 12:56:09 GMT

"This error comes when you don't have "Forefront Identity Manager Service" started. Just go to services.msc console and start the Forefront Identity Manager Service. This error will go. -Anupam"

I am getting this error and Forefront Identity Manager Service is running on my box.

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Stefan Goßner — Wed, 04 May 2011 12:02:35 GMT

Hi Rober,

what exactly do you mean? That is exactly the message I talked about in this article.

Cheers,

Stefan

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Rober — Wed, 04 May 2011 10:54:43 GMT

Hi Stefan,

Thanks for your solution but my system show me ('System.Security.Cryptography.CryptographicException') in OWSTIMER.EXE [6832]. What do you think about this?

Rober

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Stefan Goßner — Sun, 10 Apr 2011 15:07:51 GMT

Hi Philo,

I'm not exactly sure what you mean.

The keyset exists in memory of OWSTIMER.EXE. During shutdown of this process the keyset should be cleaned up to avoid the problem but it is not to avoid the exception. After the process is terminated the keyset no longer exists - so there is nothing to be cleaned up.

Cheers,

Stefan

re: Common problem with SharePoint 2010: System.Security.Cryptography.CryptographicException - Keyset does not exist

Philo Janus — Sun, 10 Apr 2011 12:29:02 GMT

I'm really bothered by the suggested solution - hiding the debugger popup doesn't solve the problem; it just masks it. And there may be other reasons a user wants the JIT debugger available.

Given your position, may I politely recommend coming up with a solution to clear the keyset? The articles you reference are talking about when custom code creates a keyset and don't clean up after themselves; but it seems that in this case SharePoint is doing it. So take the time to figure out *why* SharePoint is doing it, and how we out here can clean up after it.

Thanks.