Unable to Configure NPrinting On Demand connection in Qliksense

[fashid]

Hi Experts,

I am trying to Configure "On demand reporting" custom object provided with the extension bundle in Qliksense for On demand reporting through Nprinting .however i am not able to configure the connection and i am gettinng ERR_CONNECTION_TIMED_OUT when i check in the debug mode of the browser under networks. 

Apart from this Nprinting is working fine and reports and tasks are getting executed without any problems. Only problem is arising with the ODAG connection. 

I have checked the Services user account on NPrinting server which is same as the one on Qliksense server.

Any help is greatly appreciated.

Thanks .

[Frank_S]

https://community.qlik.com/t5/Official-Support-Articles/Qlik-NPrinting-and-ODAG-apps-On-Demand-App-G...

When a new ODAG app is created, it will have a different object ID and so the already created Qlik NPrinting report templates will not work, as they use the Qlik Sense object IDs of the first app. There is no way to mass update them and the user will have to re-create the report templates.

[fashid]

Hi Franks,

Thanks for the reply.

I am bit confused here. I am using the "On demand reporting" custom object in qliksense and just trying to just configure it . This is even before connecting to any nprinting app or report template. 

I am attaching a screenshot of the issue .

Thanks

[Frank_S]

No worries...

But keep in mind that ODAG is not the correct term to use in your description.

It's a purely NPrinting On Demand issue you are experiencing. (ODAG - On Demand App Generation is a separate pure Qlik Sense feature. More about that can be found here: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/LoadData/enabling-OnDema...

In any case the error you share - and solution - are covered here;

STT - NPrinting On-Demand with Qlik Sense Troubles... - Qlik Community - 1953198

Please review it carefully as there are a few reasons that you are seeing the issue you are encountering.

Kind regards...

ps: i've updated the 'subject' of your post to more closely reflect the issue you are encountering.

[Lech_Miszkiewicz]

Hi @fashid, 

how did you go with this?

Frank has provided you with all the required details. Have you been able to meet all the configuration requirements and setup the OnDemand with Qlik Sense and NPrinting?

let us know how you went.

thanks

Lech

[fashid]

Hi @Frank_S ,

Thanks a lot for giving the clarity on that . I have followed the video and also tried to fix the user . I have added the  URL in the trusted origin in the Nprinting web console which is same as the one that pops up in the error.

Also i have corrected the user but when i try to start a new session  and click on the windows logo to start a fully NT authenticated session it does not accept the user name and password and forces me to put in the credentials on the login screen itself .

I am attaching screenshots for reference .

Basically im still stuck ...

Regards,

Nadeem Shaikh 

[fashid]

Hi @Lech_Miszkiewicz ,

Thanks for checking out yes i have gone through the video and im still stuck . Still trying to figure out ..

[Lech_Miszkiewicz]

so @fashid

Lets just go through the basic checklist:

• are both NPrinting and Qlik Sense in the same domain?
• are you using FQDN (Fully Qualified Domain Names) for both servers?
• did you install and configure SSL  certificates for both sides (Qlik Sense and NPrinting) so there are no SSL errors when browsing Qlik Sense and NPrinting. I normally use 3rd party trusted certificates!!!
  • that means that your Qlik Sense and NPritning address have format like:
    • https://yourqliksense.yourdomain
    • https://yournprinitng.yourdomain:4993
• Are both sites added to your intranet or trusted addresses?
• Does your GPO allow to sign in to those sites with current user name and password?
• Did you configure Trusted Origins in NPrinting for FQDN address?
• Have you configured NPrinting users so they can use NTLM windows login authentication to access NPrinting?
  • populate NPrinting users with Domain name
  • populateNPrinting users with role allowing them to use OnDemand - you may need to create one if you have not done it yetusers should be able to login to NPrinting by using blue button without having to put any other details
• When configuring Qlik Sense extension object are you using FQDN address?

Answer each of the questions (all of them have to be done and operational without exceptions)

Let us know how you go. 

cheers

[Frank_S]

Your images show that you appear to be using a Qlik Sense server domain address that is external and trying to connect to an internal NPrinting server.

That is a complex deployment that may or may not work .

You can try to use the xxxxxx...xxxx..com address but you still need to add it as a trusted origin on the NP server>admin>ondemand>trusted origins - see the video. (not sure that will work since your www.QSserver.com is outside the network but you can give it a try.

As Lech and the video mentions, both MUST be in the same domain and ideally use the FQDN path. (you don't even have the NP server address using the full FQDN according to the images.

I suggest you rewatch the video and recommend contacting Qlik Professional services or a trusted Qlik Partner to try help you set this complex deployment up.

If used purely internally (inside your network on the same active directory domain with FQDN for both the NP and QS server and the QS server is in the trusted origins) this all works very nicely (also as shown in the video.).

[Lech_Miszkiewicz]

That url does not look like FQDN!!!

As Frank mentioned there are inconsistencies in what you are doing:

• you are trying to use some DNS name rather than FQDN
• the fact that you are getting popup for Windows authentication indicates that you didnt configure properly windows authentication or your GPO does not allow for SSO or you are trying to login from outside domain.

Before even talking about OnDemand make sure you can login to NPrinting using blue button without having to put any password through. Once you go through that hurdle we can start troubleshoot rest.

cheers