Qlik Sense Scalability Tools Connection Troubleshooting Tips

[Daniel_Larsson]

I put together check lists as a help troubleshooting connection settings problems when using Qlik Sense Scalability Tools.

Using header auth

1. Is the app published?
2. Can you connect manually to the virtual proxy with header auth using modify header plugin in firefox, fiddler or similar.
   1. If it works, make sure the user which get logged in is the one from the header not your ntlm user.
   2. Can the header user access the app you want to simulate?
3. If manual connection (1) with header works, make sure all these settings correspond to your tool settings
   1. VirtualProxyPrefix settings same as Prefix defined in QMC on the virtual proxy
   2. HeaderName same as Header authentication header name on the virtual proxy
   3. ConnectionType set to Header.
   4. Server is set to the same server name as the certificate, default fully qualified domain name, without defining protocol etc, i.e. myserver not https://myserver/hub.
   5. A default sense installation uses https and a self-signed certificate. Make sure the SSL checkbox is checked when using SSL or TLS (default) and the AllowUntrustedCertificate checkbox is checked if using the self-signed or any other “untrusted” certificate.
4. If Connect to App doesn’t work, try doing a simple scenario of 1 user 1 iteration with only a small timerdelay in the scenario, then execute this using the executor (i.e. not connect to app). Does this get any errors?
5. If you are getting license access denied, make sure the header users have an appropriate amount of tokens allocated.

Using NTLM auth

1. Make sure the user has access to the app by manually connecting to it.
2. If manual connection (1) with header works, make sure all these settings correspond to your tool settings
   1. VirtualProxyPrefix settings same as Prefix defined in QMC on the virtual proxy or blank if using root (default)
   2. ConnectionType set to NTLM.
   3. Server is set to the same server name as the certificate, default fully qualified domain name, without defining protocol etc, i.e. myserver not https://myserver/hub.
   4. A default sense installation uses https and a self-signed certificate. Make sure the SSL checkbox is checked when using SSL or TLS (default) and the AllowUntrustedCertificate checkbox is checked if using the self-signed or any other “untrusted” certificate.
3. If Connect to App doesn’t work, try doing a simple scenario of 1 user 1 iteration with only a small timerdelay in the scenario. Does this get any errors?
4. If you are getting license access denied, make sure the header users have an appropriate amount of tokens allocated.

[Daniel_Larsson]

One, more question, is the tool started from a shared drive? If so could you try copying it locally?

[krishnakumars7]

Thanks It worked!!!