Skip to main content
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

A call to SSPI failed (Qlik Sense Proxy)

No ratings
Showing results for 
Search instead for 
Did you mean: 

A call to SSPI failed (Qlik Sense Proxy)

Last Update:

Jun 8, 2022 5:42:29 AM

Updated By:


Created date:

Jan 15, 2017 8:04:40 AM

You may get the errors, "A call to SSPI failed, see inner exception" and "The certificate chain was issued by an authority that is not trusted". While they should have no impact on your end-users, you'd still like to clean them up from the logs.

Qlik Sense otherwise functions without issues.

Example error:

System.Proxy.Qlik.Sense.Communication.Communication.Tcp.StreamFactory 16 c2972806-6ae3-4559-8ebf-c7c2201335f3 xx\xxx Failed to authenticate stream as Server The client and server cannot communicate, because they do not possess a common algorithm↵↓A call to SSPI failed, see inner exception. NO-STACKTRACE↵↓ at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)

These, unfortunately, are not Qlik Sense errors, but rather errors from Windows that Qlik Sense reports.  You should also be able to see them in your Windows Application logs. For more information, please search out Windows Support.

See Security Support Provider Interface Architecture for additional details. 

Possible root causes:

  1. A possible root cause for Windows reporting these errors is a missing or wrong certificate thumbprint.

    If a third party certificate is being used in the environment, verify that the correct thumbprint is added to the Qlik Sense Proxy.

  2. It may also be related to the load balancer.   

    A common behaviour for a load balancer is a quite constant interval between two SSPI failures on Sense,  generally because the basic load balances HTTPS health check doesn't complete the HTTPS handshake.  The error "because they do not possess a common algorithm" is for this reason.  The fast check can be done by changing the frequency of HTTP health check on the load balancer and seeing the corresponding interval change on the Qlik Sense side pay attention if multiple LB nodes are present.


Labels (2)
Partner - Contributor III
Partner - Contributor III

Hi Chris,

We are also getting these errors in our log and I checked our Thumbprint, it is correct only then we these errors then?


Digital Support
Digital Support

Hello @tauceef as this is an error logged by Windows, this might be able to provide you with more information on what the root cause is:

Should this not help you locate the problem, I'd recommend posting on our forums to get the input from our larger customer and engineer base! 

Partner - Contributor III
Partner - Contributor III

Hi @Sonja_Bauernfeind 

We are facing this issue on a large number of machines in various locations, various windows-version, Sense-versions and setup.

AFAIK none of them are behind a load balancer. Most of them are single nodes. Some have a valid wildcard cert, with the correct thumbprint, some use the self-signed Sense cert.

All of them "work" but are feel sluggish. All logs are littered with messages that seems to have something with tls.

What do you recommend?


Partner - Specialist
Partner - Specialist

Hi @Skage ,

Did you find a solution to that issue?
I'm seeing a similar behaviour running the latest QS. I suspected Windows or external factors at this stage in the investigation.


Partner - Contributor III
Partner - Contributor III

Hi @peter_turner 

No I have not.

The root cause is afik related to Kerberos but I have no clear picture of how to solve it.

Partner - Specialist
Partner - Specialist

For me it seemed that somehow the existing SSL cert had been changed/removed. We re-added the correct one and updated the Proxy thumbprint, and will monitor the Proxy logs.

Other possible leads were a change to the servers TLS settings, IISCrypto would be best to check that but wasn't needed for me at this stage.


Version history
Last update:
‎2022-06-08 05:42 AM
Updated by: