Common eSync issues caused by incorrect certificates

  • Updated

The following errors are caused by missing or incorrectly applied certificates.

  1. Click on sync profile and the Uh ohh error appears.

    sync uh oh

  2. Cryptography error : Exception Details: System.Security.Cryptography.CryptographicException: 
    The parameter is incorrect.

    Cryptography Error   

  3. Sync gets all the way to the end but then fails.

    Sync fails at end

  4. Identity Check error:  Exception Details: System.ServiceModel.Security.MessageSecurityException: The identity check failed for the outgoing message.

    Identity Check Error

  5. No security certificates found:   "No security certificates were found for synchronization. Please configure the certificates and try again." 

    No security certificates

  6. EWS started up BUT is NOT fully functional.   

    EWS started up BUT is NOT fully functional

  7. Requested Security Token: "the requested security token could not be satisfied because authentication failed."

    the requested security token could not be satisfied

The Ektron Windows Service (EWS) cannot reconcile the certificates because they are incorrect.

Follow the steps in the Knowledge Base link. 
EWS started up BUT is NOT fully functional

If on versions earlier than 9.1SP3 and TLS 1.0 is disabled, regenerating certificates will not be enough. We recommend upgrading to 9.1SP3+ or if there is no other option re-enabling TLS 1.0(though this can be a major security risk so we don't condone it).

If you have further issues, contact Ektron Support.