Skip to content

Quick Links

My Account
Welcome Guest
Knowledge

NPrinting Schedule service goes down after an upgrade to NPrinting 2018 November release

Article Number: 000062393 | Last Modified: 2019/06/11

Description

After the upgrade to NPrinting 2018 November release, the NPrinting Scheduler service will not stay up and running in the Windows 'Services' panel.  
  • It is possible to restart it, but then it goes down again after few minutes. As a result, NPrinting will not function normally and the NPrinting Engine will remain in an 'Offline' status in the NPrinting Web Console>Engine Manager
The scheduler logs show the following message:
 
FATAL    ITGREZSTAP010        0    0    0    0    0    0    0    0    Unable to start Scheduler service. ERROR: System.AggregateException: One or more errors occurred. ---> System.TimeoutException: The operation requested on PersistentChannel timed out↓↓   at EasyNetQ.Producer.PersistentChannel.InvokeChannelAction(Action`1 channelAction)↓↓   at Qlik.NPrinting.Common.EasyNetQ.NPrintingClientCommandDispatcherThreaded.Invoke(Action`1 channelAction, CancellationToken cancellationToken) in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Common\EasyNetQ\NPrintingClientCommandDispatcher.cs:line 136↓↓   at Qlik.NPrinting.Common.EasyNetQ.NPrintingClientCommandDispatcherThreaded.Invoke(Action`1 channelAction) in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Common\EasyNetQ\NPrintingClientCommandDispatcher.cs:line 174↓↓   at EasyNetQ.RabbitAdvancedBus.ExchangeDeclare(String name, String type, Boolean passive, Boolean durable, Boolean autoDelete, Boolean internal, String alternateExchange, Boolean delayed)↓↓   at Qlik.NPrinting.Common.Messages.RabbitTopologyBase.InternalPrepareQueue(String exchangeName, String queueName, Boolean useHashAsRoutingKey, Boolean queueDurability, Nullable`1 maxPriority, IExchange& exchange, String& routingKey) in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Common\Messages\RabbitTopologyBase.cs:line 89↓↓   at Qlik.NPrinting.Common.Messages.ContentResolutionRabbitTopology.PrepareEngineStatusQueue(IExchange& engineExchange) in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Common\Messages\ContentResolutionRabbitTopology.cs:line 53↓↓   at Qlik.NPrinting.Common.Messages.ContentResolutionRabbitTopology.RegisterSchedulerForAllocationStatus(Action`2 allocationStatusMessageProcessor) in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Common\Messages\ContentResolutionRabbitTopology.cs:line 123↓↓   at Qlik.NPrinting.Scheduler.Service.LoadBalancer.Start() in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Scheduler\Service\LoadBalancer.cs:line 200↓↓   at Autofac.ContainerBuilder.StartStartableComponents(IComponentContext componentContext)↓↓   at Autofac.ContainerBuilder.Build(ContainerBuildOptions options)↓↓   at Qlik.NPrinting.Scheduler.SchedulerHttpService.Start(String[] args) in C:\Jws\release-18.39.x-w104zyghT\server\NPrinting\src\Scheduler\SchedulerHttpService.cs:line 150↓↓   at System.Threading.Tasks.Task.Execute()↓↓   --- End of inner exception stack trace
​​​​​​
  • Open Control Panel>Internet Options>Advanced on the NPrinting Server machine. Verify that TLS 1.0 is not enabled.
 
Environment:
  • NPrinting 2018 November release

Cause

The problem is due to a bug (OP-8195) that is completely fixed in NPrinting February 2019 SR 1.

Resolution

    The problem is completely solved in Qlik NPrinting February 2019 SR1. Upgrade to this or to an higher release.

    If the upgrade is not possible, it will be necessary to Enable TLS 1.0.
    It is also necessary to Ensure that at least one of the following cypher suites is enabled.
     


    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