topic Re: NPrinting September 2019 Connection bug in Qlik NPrinting

NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 08:47:21 GMT

I updated NPrinting to September 2019 and when connecting to QlikSense it says as attached that the "Installed certificates are valid to connect to Qlik Sense"

I imported the certificates again and it is not working. The QlikSense server is also September 2019

Re: NPrinting September 2019 Connection bug

Ruggero_Piccoli — Wed, 16 Oct 2019 09:00:39 GMT

Hi,

Please check this help site page https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/Troubleshooting/NP-wont-read-QS-certificates.htm

Be sure that you followed all the instructions in the page https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm. I think you miss something or did something wrongly.

Best Regards,

Ruggero

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 09:57:14 GMT

Hi Ruggero,

I can't understand why certificates are lost in 2019 September version.

I had to copy the client certificate in C:\Program Files\NPrintingServer\Settings\SenseCertificates as mentioned.

However I get the "Get ProxyId from QRS on the "Proxy Address"" error

An issue occurred in MashupServer.GetAuthenticationCookiesAndConsumeQlikTicket. Proceeding anyway by using Windows authentication to load the mashup page.. ERROR: System.Exception: No valid Sense Certificate found or Unauthorized user in Header 'X-Qlik-User'=UserDirectory=xxxx;UserId=xxx. ERROR: System.Net.WebException: The remote server returned an error: (403) Forbidden.↓↓ at System.Net.HttpWebRequest.GetResponse()↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.TryGetResponse(HttpWebRequest request)↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.DoGet(QlikSenseConnectionString connectionString, String port, String urlChunk, Boolean addQlikCertificate, Boolean impersonateService)↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.DoGet(QlikSenseConnectionString connectionString, String port, String urlChunk, Boolean addQlikCertificate, Boolean impersonateService)↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.LoadProxyData(QlikSenseConnectionString connectionString)↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.LookupQpsRestPort(QlikSenseConnectionString connectionString)↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.GetQlikTicket(QlikSenseConnectionString conn)↓↓ at Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator.GetAuthenticationCookiesAndConsumeQlikTicket()↓↓ at Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator.RefreshAuthCookies()

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 09:59:54 GMT

Hi Ruggero,

I can't understand why certificates are lost in 2019 September version.

I had to copy the client certificate in C:\Program Files\NPrintingServer\Settings\SenseCertificates as mentioned.

However I get the "Get ProxyId from QRS on the "Proxy Address"" error

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 10:26:48 GMT

Hi Ruggero,

I can't understand why certificates are lost when installing NPrinting April 2019.

I copied to the Qlik NPrinting installation folder client.pfx and no I am having the following error, when ports are correctly opened and reachable

Re: NPrinting September 2019 Connection bug

Ruggero_Piccoli — Wed, 16 Oct 2019 12:44:22 GMT

Hi,

The upgrading procedure should not delete the certificate installed with the old QmcCertificateInstaller in April 2019. In any case, exporting again and install them in the new folder as documented in the September 2019 help site resolves and that folder will not be deleted by future upgrades. In case you need to delete it manually.

In case of errors in the Run Verification list you must start to solve from the first error. The reason it that following errors could be consequences of the first. Some suggestions are available in the page https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/Troubleshooting/Verify-connection-to-Sense-errors.htm

Best Regards,

Ruggero

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 13:49:50 GMT

I can't understand why NPrinting upgrades are so inestable.

Everything was ok yesterday with the previous version. Now whith the September 2019 version I lost the certificates and can't use NPrinting, with the respective issue with the client.

Meanwhile, Qlik doesn't give a solution...

With Microstrategy these issues don't happen

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 13:53:15 GMT

by the way, in the web that you provided there is a bug for the issue that I'm experiencing, it mentions:

Verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Repository Service on port 4242.

when is the same point being mentioned in the previous point that is working correctly...

Re: NPrinting September 2019 Connection bug

Ruggero_Piccoli — Wed, 16 Oct 2019 14:07:38 GMT

Hi,

Before upgrading I suggest you to read the official Release Notes of the new versions. You are upgrading from April 2019 to September 2019 and the way certificates are managed was changed with the June 2019 release because we added the new feature that lets you to connect to many Qlik Sense servers.

The solution is the one I mentioned in my previous message: export the Qlik Sense certificate again and install them in the Qlik NPrinting Server by following the new documented procedure.

As Qlik we supply a support service to all our customers. If something went wrong you can open a support ticket and a skilled colleague will help you directly.

Best Regards,

Ruggero

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 14:12:20 GMT

The solution of the certificates is for the first issue, now we have the previously mentioned.

We already gotin touch qith Qlik without any answer.

Thank you.

Re: NPrinting September 2019 Connection bug

Ruggero_Piccoli — Wed, 16 Oct 2019 15:02:52 GMT

Hi,

If you opened a support ticket a colleague will contact you.

In the meantime be sure you met all the requirements to connect to Qlik Sense from Qlik NPrinting https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/GettingStarted/HowCreateConnections/Connect-to-QlikSense-apps.htm. In particular be sure that you are using the right user, because from the logs it seems a problem with the user.

Best Regards,

Ruggero

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 15:48:00 GMT

Hi,

I have just solved the issue based on this article

https://support.qlik.com/articles/000085285

Re: NPrinting September 2019 Connection bug

lanlizgu — Wed, 16 Oct 2019 16:38:57 GMT

with the upgrade to September 2019, the certificates of the servers and data of NPrinting users were lost in the QMC, needing to configure again these points.

Re: NPrinting September 2019 Connection bug

Lech_Miszkiewicz — Thu, 17 Oct 2019 09:11:35 GMT

I am not Qlik employee but I spent a lot of time learning NPrinting and teaching NPrinting.

So I would not blame Qlik for not reposnding or not working, or installers being unstable.

If you have not followed all required steps you simply broke something or you maybe assumed that everything will be ok if you just keep pressing Next-->Next--> Next during installation...

As I have done many upgrades already, I know that correctly done upgrade procedure works correctly and everything works as it should. In your case I can only say that you did not meet all requirements / did not follow all required steps. It is common mistake and you are not the only one who made it.

By the way - properly done upgrade procedure requires you to take backup first.

So just roll back using backup!

Re: NPrinting September 2019 Connection bug

lanlizgu — Thu, 17 Oct 2019 09:19:01 GMT

Hi Lech,

I have also done many upgrades, and as you can expect I had also the backup available.

What I mean is that, although it is mentioned, when a software feature (certificates in this case) work correctly, it doesn't have much sense this feature to stop working after an upgrade. I understand that Qlik should ensure that things that were working correctly to continue working correctly with the upgrade.

I can understand that I should configure new features with the upgrades, but not being persistent with current features is not a behaviour that should be defended.

Thank you.

Best regards.