Keyset does not exist, CryptographicException error in OWSTIMER.EXE

SHAREPOINT TIPS & TRICKS

Applies To: Ontolica Search for SP2010

If you encounter the Visual Studio Just-In-Time Debugger?error “An unhandled exception (‘System.Security.Cryptography.CryptographicException’ )?occurred?in OWSTIMER.EXE [5152]” and the following message is logged in the Event Viewer:

An unhandled exception occurred and the process was terminated.
Application ID: DefaultDomain
Process ID: 6148
Exception: System.Security.Cryptography.CryptographicException
Message: 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()

then this might be raised when SharePoint 2010 and Visual Studio 2010 are both installed on the same machine. It may appear every 24 hours.
Does it occur because?the OWSTimer service has a regular process recycle and when the old process is shut down?an exception is raised. The exception doesn’t? interfere with the normal process shutdown and recycle and is only ever seen if you have a JIT debugger installed on the machine.
Can you?choose to?ignore these exceptions and close the window, or leave it there. Can you debug the indicated? the process, because it will already have been closed by the time you click the button and start your debugger.

To prevent this pop up message one can disable JIT debugging on the affected machine, but, please keep in mind that, this operation will deactivate?JIT debugging for all applications on the machine. To configure the server to no longer show a dialog when an unhandled exception occurs, use the registry editor to delete the following registry keys:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows NT\CurrentVersion\AeDebug\Debugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
.NETFramework\DbgManagedDebugger

On a 64-bit operating system also delete the following registry keys:
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\
Windows NT\CurrentVersion\AeDebug\Debugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\
.NETFramework\DbgManagedDebugger

More details are available here:
http://blogs.msdn.com/b/pandrew/archive/2010/05/25/benign-owstimer-unhandled-exception-popup-system-security-cryptographic-cryptographicexception.aspx

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment