topic Scalability Tool Issue_ public key not resolved in Scalability

Scalability Tool Issue_ public key not resolved

Wed, 10 May 2017 09:08:23 GMT

When I try to execute one step I am getting the following error in Log file.

WARN ScenarioEditor:Assembly <Qlik.Engine, Version=12.4.1.0, Culture=neutral, PublicKeyToken=1a848309662c81e5> not resolved

2017-05-10 14:52:36.2848+10:00 ERROR Executor: Empty config file

Step: Select Acquisition dashboard sheet

Can any one help me what will be the issue and how to resolve it

Re: Scalability Tool Issue_ public key not resolved

Daniel_Larsson — Wed, 10 May 2017 10:57:05 GMT

Hi, the warning about public key not resolved can be ignored.

I'm assuming you are trying to use the executor tab in the sense scalability GUI. Not sure how you started the executor, (through menu or execute button in editor), but it seems you have not given it which scenario file to execute.

Re: Scalability Tool Issue_ public key not resolved

Thu, 11 May 2017 12:16:20 GMT

Hi Daniel,

Even if we ignore the Warning message we are still getting the following error while executing the scenario with the single user "Connect attempt failed" in the Executor tab. And we are using the Qlik scalaibility tool for the same.

And the log file is not much help full to drill down the issue. Is there any other way to check that the scenario has been executed.

Re: Scalability Tool Issue_ public key not resolved

Daniel_Larsson — Fri, 12 May 2017 06:58:38 GMT

Ok, this is a different issue for which you wouldn't get the logging above.

It is very likely you have a mismatch between the settings in the tool and QMC.

First thing would be to test the connection manually using the chosen authentication type. For header auth this could be done using firefox+modify header plugin, fiddler or other tools.

There's a section Appendix A, authentication to help guide you through the QMC settings. Marcus Spitzmiller also made a video series for an older version of the tool which might help; Qlik Sense Scalability Tool - Part 1 - Initial Setup - YouTube

Re: Scalability Tool Issue_ public key not resolved

Fri, 12 May 2017 07:16:54 GMT

Thanks Daniel. I will check the connectivity between the tool and QMC is correct. And let you know if i need anymore clarification on the same.

Re: Scalability Tool Issue_ public key not resolved

Tue, 16 May 2017 13:11:19 GMT

Hi Daniel,

This issue is occurring very frequently. For eg: if I am able to execute the script in the morning and in the mid noon its getting failed by the error

WARN ScenarioEditor:Assembly <Qlik.Engine, Version=12.4.1.0, Culture=neutral, PublicKeyToken=1a848309662c81e5> not resolved.

Can you please let me know what will be the exact issue. And why this error occurs very frequently despite of any interruption made manually? Or is there any permanent setting which can be made on the server side to avoid this issue in future.

Re: Scalability Tool Issue_ public key not resolved

Daniel_Larsson — Wed, 17 May 2017 06:46:10 GMT

Hi a script can never get failed by the error you post. this error is in the GUI log. For reasons why your scripts fails please check the result log for your script. If you experience differences depending on time, it's either a license issue (you used up login accesses allocated) or network issue, without any type of log from the script execution it is however hard to know.

Re: Scalability Tool Issue_ public key not resolved

Wed, 17 May 2017 07:24:32 GMT

Thanks Daniel, I have checked the Result logs and found the following error has been occured which running the scenarios "Qlik.engine.communication.CommunicationErrorException: Connect Failed to 2 attempts-->System.Exception:EngineWebsocketFailed[Fatal]"

Can you please provide your thoughts on the same.

Re: Scalability Tool Issue_ public key not resolved

Daniel_Larsson — Wed, 17 May 2017 07:56:49 GMT

This means the tool was refused connection by the server or somewhere between, unfortunately it's not possible to know the exact reason for a refused connection. During the time the connection is refused, can you connect manually using the exact same user and settings being simulated? I.e. if using ntlm, try connecting with that ntlm user, if using header try connecting using firefox+modify header to the virtual proxy.

Re: Scalability Tool Issue_ public key not resolved

Wed, 17 May 2017 08:37:25 GMT

We are using the header auth. and unfortunetly i m not able to get the correct URL to launch in the browser. can you let me know the format.

I have only the following details with me in the scalbility tool : Virtual proxy prefix, Header Name,App, server, Username prefix.

Can you please let me know how can I check the connectivity?

Re: Scalability Tool Issue_ public key not resolved

Daniel_Larsson — Wed, 17 May 2017 08:54:41 GMT

Did you use a tool to correctly inject the headers you are using? Such as fiddler or firefox+Modify Headers

It's worth to note that there exist a extension for chrome modifying headers, this won't work though because it doesn't properly inject headers on websockets.

you should connect to https://yourserver/yourvirtualproxyprefix

If you're having connection problems, connecting the same way manually to rule out the tool should always be the first thing to do. If you can't connect manually the tool of course won't be able to.

Re: Scalability Tool Issue_ public key not resolved

Thu, 18 May 2017 05:26:56 GMT

HI Daniel,

I checked with the License and Network connectivity. Everything is working as expected but still this issue is existing. Can you please guide me how to proceed further?

Re: Scalability Tool Issue_ public key not resolved

Daniel_Larsson — Thu, 18 May 2017 07:04:35 GMT

Since you don't specify it, did you test this as a header auth user, i.e. using firefox+modify header with the exact user name being simulated? And also did you do this after the tool had a failed connection (as you previously described it as differing between times).?