Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi @ all,
does anybody knows if it is possible to check that an user has downloaded his NPrinting report from NewsStand?
Regards
Hi,
This is the PostgreSQL error when you try to connect from Qlik Sense? You could check https://community.qlik.com/t5/Qlik-NPrinting-Discussions/NPrinting-Repository-Database-Name/td-p/133... and that port 4992 is opened on Qlik Sense and PostgreSQL servers.
Best Regards,
Ruggero
Hi,
You have to activate the Audit Trail https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/AdministeringQVNprinting/Audit-trail...
Then you will find the NewsStand Download event in the audit_event table.
Best Regards,
Ruggero
Hi @Ruggero_Piccoli ,
thank you. Can I load the data from a Qlik Sense script?
Every access by REST or webfile was forbidden.
Thank you
Hi,
The Audit Trail has its own database different than the one used as Qlik NPrinting Repository. You can connect Qlik Sense to the Audit Trail database and load the data via script. You could also manage the storage of audit trail data via Qlik Sense script because the database is deleted based on the settings.
Best Regards,
Ruggero
I posted about this here: https://nprintingadventures.com/2021/02/06/nprinting-audit-logs/
Hi,
There are also APIs to get Audit Trail results. Refer to https://help.qlik.com/en-US/nprinting/May2022/APIs/NP+API/index.html?page=9 and related pages.
Best Regards,
Ruggero
Hi @Lech_Miszkiewicz ,
thank you for your documentation.
But after editing the pg_hba_conf file, my services won't start (at the end, all logs show me that RabbitMq is not connected or reachable).
Any ideas? I just added the IPv4 and IPv6 lines.
Regards
Hi,
Check that the Qlik NPrinting Messaging Windows service is running.
Best Regards,
Ruggero
yes, the service is running
at the moment, audit service, scheduler and web engine starts and stops after a few seconds.
Regards
Hi,
Try to restore the pg_hba_conf file to the previous settings and start the services again. Maybe they are not more able to connect with the Repository.
Best Regards,
Ruggero