locked
System.Security.Cryptography.CryptographicException An unhandled exception occurred and the process was terminated. RRS feed

  • Question

  • After an installation of SP2010 beta 2 on Windows 2008 R2 I have this error in the event log after start up.

    I had setup a self-signed code-signing certificate for Infopath and this seems to work fine. Nothing else comes to mind.

    Any ideas on where to look next, ULS settings etc?

    Log Name:      Application
    Source:        ASP.NET 2.0.50727.0
    Date:          12/01/2010 15:31:28
    Event ID:      1334
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Sharepoint2010.Winsmoor.local
    Description:
    An unhandled exception occurred and the process was terminated.

    Application ID: DefaultDomain

    Process ID: 3816

    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()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ASP.NET 2.0.50727.0" />
        <EventID Qualifiers="49152">1334</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-01-12T15:31:28.000Z" />
        <EventRecordID>8247</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Sharepoint2010.Winsmoor.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>An unhandled exception occurred and the process was terminated.

    Application ID: DefaultDomain

    Process ID: 3816

    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()</Data>
      </EventData>
    </Event>

    Tuesday, January 12, 2010 4:09 PM

Answers

  • This issue came up frequently in Windows 2000; however, I have not seen it in some time - in previous versions of Windows this error was generated when the Protect Storage service did not start, you can verify the service is started or start the service through the Service Manager (Start | Run | Services.msc).  A failed DCOM or RPC service may also cause the problem since they are services on which Protect Storage has dependancies.
    Bill Baer, Technical Product Manager - US-SharePoint http://blogs.technet.com/wbaer
    Friday, January 15, 2010 4:20 PM

All replies

  • This issue came up frequently in Windows 2000; however, I have not seen it in some time - in previous versions of Windows this error was generated when the Protect Storage service did not start, you can verify the service is started or start the service through the Service Manager (Start | Run | Services.msc).  A failed DCOM or RPC service may also cause the problem since they are services on which Protect Storage has dependancies.
    Bill Baer, Technical Product Manager - US-SharePoint http://blogs.technet.com/wbaer
    Friday, January 15, 2010 4:20 PM
  • Thanks Bill

    Protected Storage was set to Manual. Started it up and the problem was gone.
    Sunday, January 17, 2010 5:27 PM
  • Thanks,

    same issue here on clean 2008 R2.

    Regards,

    Robin

    Monday, February 7, 2011 9:29 AM