Hi all,
I'm (trying to) evaluate Qlik Nprinting. I've got a Qlik Sense production server (3.2.0) running since a long time, and a few days ago I followed the following guide to set up Qlik Nprinting (17.3): Installing Qlik NPrinting ‒ Qlik NPrinting
All services are working fine, and I followed Creating connections ‒ Qlik NPrinting to connect to my Sense app, created by the same account as I've setup and created everything in Nprinting with. I've exported the certificates from my Sense server and installed them, using the "QmcCertificatesInstaller". There's no firewall between the two servers, and I've disabled the Windows Firewall just to make sure none of my rules are messed up.
The Qlik Sense app I'm trying to get the Qlik Nprinting Connection to work against is based on a 100kb .csv, and consist of a single pie chart. I've been waiting for 3 days for the Qlik Nprinting Connection Cache to finish. I've restarted all the services, and the server several times and recreated the Connection.
I've reinstalled Qlik Nprinting and made sure I followed the guides fully. Since the Cache status is stuck on "Generating", no errors are logged anywhere in "C:\ProgramData\NPrinting\Logs". The latest entry in the logs are:
nprinting_webengine.txt: "
| Qlik.NPrinting.Repo | 17.3.0.0 | Qlik.NPrinting.Repo.Service.DataConnectionService | 20170509T110952.816+02:00 | INFO | NPRINTINGLAB | NprintingService | 0 | 0 | 9cabf2ac-b5c0-4ad5-a18b-e8a8d82c129d | b8eb3144-6835-4f11-82b0-a626f10abf3e | 0 | 0 | 0 | 0 | Reload metadata task b8eb3144-6835-4f11-82b0-a626f10abf3e sent to queue | | |
"
nprinting_engine: "
| Qlik.NPrinting.Engine | 17.3.0.0 | Qlik.NPrinting.Engine.EngineService | 20170509T101202.180+02:00 | INFO | NPRINTINGLAB | | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Slave Engine Service started successfully | | |
"
The engine is running according to Admin > Engine manager
I'm running out of both ideas and time, hopefully there's a helpful soul out there!
I guess the final thing I can mention is that both the Sense and Nprinting server is running Windows Server 2016, I guess that's not too common yet.
Best regards,
Melker
