Qlik Sense compatibility with Qlik NPrinting The following Qlik Sense versions are supported when connecting to Qlik NPrinting. Note that your Qlik NPrinting version must be equal to or higher than your Qlik Sense version
cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
I just tried with a new app, with one table and 1 chart but the error is here again.
ERROR Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator - Engine.Navigator.QlikSense.SDK 18.104.22.168 Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator 20200922T092654.523+02:00 ERROR QLIK03 0 0 0 0 0 0 0 0 An issue occurred in MashupServer.GetAuthenticationCookiesAndConsumeQlikTicket. Proceeding anyway by using Windows authentication to load the mashup page. ERROR: System.Net.WebException: The remote server returned an error: (400) Bad Request.↓↓
What is the meaning of that trace of log (nprinting_engine_cef.log)?
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
I'm interesting in this thread because we're also facing a behavior like that, but even stranger.
If we configure Nprinting Connection with proxy address = 'https://nodename' it works fine. Verification runs, chace loads, etc.
But if we configure proxy address = 'https://proxyaddress-qlik/' and modify c:\windows\system32\drivers\etc\hosts file with the line 'node.interconnection.ip proxyaddress-qlik #nodename' it doesn't work. This config ran before upgrade to Sept 2020 in QS and NP (later, que use QS sept 2018 & NP June 2019).
Why we want to use hosts file? because we have 2 QS central nodes and we want a easy-to-use NP proxy address change method if the server referenced in NP Proxy address stops suddenly. I mean, If we use "traditional" NP connection config, if the QS node referenced in all NP connections gets down, we must change by hand all connections in order to reference to the other QS node. But, if we use hosts file, it's only to comment a line and uncomment another one.