Usually these issues are due to connection settings not being correct, so to first verify:
* Are you able to connect to the app manually using a header user (e.g. using modify headers plugin in firefox)? - (I see you did this, but as a reference to others)
* If you change the script to only be a timerdelay of maybe 10s (i.e. the user will connect to the app, wait 10s and disconnect) do you get any errors or will it connect when you execute it (i.e not "connect to app")?
Are you able to connect to the app manually using a header user (e.g. using modify headers plugin in firefox)?
Yes, connecting to the application in Firefox works without problems
If you change the script to only be a timerdelay of maybe 10s (i.e. the user will connect to the app, wait 10s and disconnect) do you get any errors or will it connect?
I attached the log file of the execution result, but it didn't work either. I'm actually not able to connect to the application using the "App structure -> Connect to app" entry from the menu.
ok, so since not even that simple execution works we can rule out it being any issue with the connect to app functionality.
Connection gets refused. Do you have IIS running or any other application which would use the port 80? In that case try changing it to a different port, i.e. 81 in both QMC and scalability tool.
If there is no such program, the issue is either with settings in the script or in the proxy. Does the server allow ntlm users? In that case, running the tool as a user with access to the app, change to a virtualproxyprefix which allows ntlm users (or removing it if it's the root) and change the connection type to ntlm. If the ntlm user can connect, the issue is either with the headname, the virtualproxyprefix name or token allocation/access rules.
If also the ntlm user fails the problem is most likely with server name or token allocation/access rules.
Shame on me.
For some reason Windows' "IIS World Wide Web Publishing Service (W3SVC)" was listening on port 80, preventing Qlik from serving content on this port. I never noticed this as I usually access Qlik over https. However https did not work because of the self-signed certificate I configured in the QMC.
I'm now able to execute scenarios with the ScalabilityTool. Thanks for the quick support!