Knowledge

After NPrinting upgrade, tasks are not running

Article Number: 000051238 | Last Modified: 2018/10/31

Description

Environments:

NPrinting all versions 17
NPrinting all versions 18

After NPrinting upgrade, none of the task is running, cache connection can't be generated.

Cause

When upgrade on NPrinting 17/18 is performed, all components must be on same version

Resolution

Performed upgrade on Server component: QlikNPrintingServer_x64 (ver 18.9.5.0):

NPrinting DB (ver. 18.9.5.0)2018-05-08 12:13:59,068 [1] INFO Qlik.NPrinting.Repo.UpgradeDb.NPrinting17UpgradeHelper - Qlik.NPrinting.Repo.UpgradeDb 18.9.5.0 Qlik.NPrinting.Repo.UpgradeDb.NPrinting17UpgradeHelper 20180508T121359.068+00:00 INFO NPRINTING 0 0 0 0 0 0 0 0 Database successfully upgraded to version 18.9.5.0.
Scheduler (ver. 18.9.5.0) Qlik.NPrinting.Scheduler 18.9.5.0 Qlik.NPrinting.Scheduler.SchedulerHttpService 20180508T121401.782+00:00 INFO NPRINTING 0 0 0 0 0 0 0 0 Starting up scheduler service
WebEngine (ver. 18.9.5.0) Qlik.NPrinting.WebEngine 18.9.5.0 Qlik.NPrinting.WebEngine.Engine 20180508T121359.652+00:00 INFO NPRINTING 0 0 0 0 0 0 0 0 The service is starting

NOT performed upgrade on Engine component: QlikNPrintingEngine_x64 (17.6.0.0)

Unexpected socket error: 10053
Caller: OnStreamEndRead, file path: d:\WorkShop\SuperSocket\v1.6\SocketEngine\AsyncStreamSocketSession.cs, line number: 162
The server instance QlikSensePrintingWebSocketProxy has been stopped!
Qlik.NPrinting.Engine 17.6.0.0 Qlik.NPrinting.Engine.EngineService 20180508T095151.734+00:00 INFO NPRINTING 0 0 0 0 0 0 0 0 Engine service stopped

Upgrade Engine component is resolving the issue

Get Answers

Find Answers

Qlik Community

Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.

Join Us

Get Support

Have a Question?

Search Qlik's Support Knowledge database or request assisted support for highly complex issues.

Submit a case

Talk with a Representative

Critical Issues

Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.

Call Us