Impact 2023 (Dynamic Constraints Edition) release is available for download, bringing with it a host of new features. Available here.

A call to SSPI failed

PROBLEM: A call to SSPI failed

Example: An error message "A call to SSPI failed, see inner exception." is displayed when starting the real time synchronization monitor.



SOLUTION: 

This error is generated when using a TCP/IP endpoint for the ISynchronizationSubscription. It relates to how Windows authenticates a user for the running service using Kerberos. More information can be found on the web by searching for 'SSPI SPN WCF'. 


Modify the EnterpriseServicesClient.exe.config file client endpoint section for the ISynchronizationSubscription by either


1. Using a numeric IP address for the TCP/IP endpoint rather than a server name.  


2. Or, by adding an <identity> section for the net.tcp client endpoint and specifying an empty servicePrincipalName as below 


<client>

  <endpoint

    address="net.tcp://SABRE01:8002/SynchronizationSubscriptionService" 

    binding="netTcpBinding" 

    bindingConfiguration="netTcpBindingSubscriptionService" 

    contract="Arden.Enterprise.Services.Interface.ISynchronizationSubscription" >


    <identity>

      <servicePrincipalName value=""/>

    </identity>


  </endpoint>

</client>

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.

You may like to read -