Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I know that this topic was discussed here multiple times, and there are different reasons every time this issue is occuring, but I hope you will be able to guide me through with my setup.
Quick recap:
1. All NPrinting applications and services were installed and seems to be running successfully.
2. I have QS and NPrinting running on the same server (I know that it's not "recommended" configuration, but I am just validating a tool right now).
3. The setup was done using local user, who was included into all Admin groups (all groups I was able to find in the Installation documentation) and has a token assigned to it.
4. All services are up and running:
5. I am trying to create a connection to a published app, but I am receiving an error after system spends some time "Generating" the connection:
6. The app I am using does not have a Section Access activated.
7. Security settings are updated and Certificates are installed (https://help.qlik.com/en-US/nprinting/17.3/Content/DeployingQVNprinting/Installing-sense-certificate...) and I've used QMCCertificatesInstaller.....
8. Not much info from the logs:
From: nprinting_webengine.log
Reload metadata task 5aa80aec-b378-4fdf-ae0c-53857428a3ff sent to queue
From: nprinting_scheduler.log
Connection navigator=qliksense;proxyurl=https://qlik_AA/;appid=49ea27f0-807b-4c67-8db5-0797b40d490d;identity=qlik_AA\QlikAdmin has reached ERROR status
I would appreciate any suggestions and/or recommendations about handling this issue....
Best regards,
Vlad
Lech,
Yes, this user was set as RootAdmin, so it was not the reason.
I've found what was missing: the App was published in the stream which this Admin account has no access to.
I need to check system's security rules (because I believe all streams should be accessible for all RootAdmins)....
Another strange thing is that I've also tried to connect to the app published in "Everyone" stream, and it was not successful....
Will keep investigating, but thanks for your note, it helped me to find the problem.
Regards,
Vlad
Hi Vladimir
Is NPrinting user set as a "Root Admin" in QMC?
In the QMC you must give the RootAdmin authorization to the Windows user that runs the Qlik NPrinting Engine and Qlik NPrinting Scheduler Windows services. That Windows user must also be a domain user
I understand that using NPrinting user you are able to open QlikSense hub and browse application - right? RDP to NPrinting engine box and test it using NPrinitng user.
If you want to create connections to Qlik Sense apps, the user that runs the Qlik NPrinting Engine service must be a Windows domain user. To create a domain user, refer to the Microsoft documentation (in English) Create a New User Account.
cheers
Lech
---------------------------------------------
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 as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
Lech,
Yes, this user was set as RootAdmin, so it was not the reason.
I've found what was missing: the App was published in the stream which this Admin account has no access to.
I need to check system's security rules (because I believe all streams should be accessible for all RootAdmins)....
Another strange thing is that I've also tried to connect to the app published in "Everyone" stream, and it was not successful....
Will keep investigating, but thanks for your note, it helped me to find the problem.
Regards,
Vlad
No worries mate,
What you saying about RootAdmin user not beeing able to access some streams is weird. It should have an access to everything (except other users Work folders).
Also remember to completly delete unsuccesful NPrinting connections to your QlikSense document and start over with new ones when testing further (just in case there is a stale generate metadata task sitting in background).
cheers
Lech
Thanks, will do that!
Vlad
hi Vladimir - did you find a root cause of your issue and why Root admin could not see this certain stream?
I am curious what was it.
cheers
Lech