In another one of those “oh heck, I just spent a couple hours of my life chasing my tail” and in an effort to ‘prepare everyone for RTM’, you might notice the following error pop up from time to time.
And in the NT Event Log you might seen entries like:
An unhandled exception occurred and the process was terminated.
Application ID: DefaultDomain
Process ID: 1852
Exception: System.Security.Cryptography.CryptographicExceptionMessage: Keyset does not exist
StackTrace: at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
at System.Security.Cryptography.SafeProvHandle._FreeCSP(IntPtr pProvCtx)
at System.Security.Cryptography.SafeProvHandle.ReleaseHandle()
at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
at System.Runtime.InteropServices.SafeHandle.Finalize()
There is a known problem with SharePoint RTM. The warning happens whenever the SharePoint Timer Service OWSTIMER.EXE recycles, typically every 24 hours, but it’s just a warning and can be safely ignored. The underlying exception happens on all systems but is only noticeable with the development tools installed since it causes the JIT debugger to fire. The underlying issue is being caused by the GC and has no bad impact unless you have a debugger installed which will trigger the popup.
So is there a fix to this? Or MS decided that it is good enough?
Hi Robert:
Sorry, I honestly don’t know. I work in the SQL Server PowerPivot group, not SharePoint. SharePoint has released two CU (customer upgrades) via CSS Support services. I do not know if this issue is addressed in either. You might try on one of the SharePoint forums.
It’s not fixed in the latest CU but you disable the popup with some registry keys: http://blogs.technet.com/b/stefan_gossner/archive/2010/05/10/common-problem-with-sharepoint-2010-system-security-cryptography-cryptographicexception-keyset-does-not-exist.aspx