Skip to main content

NPrintring Web Engine and Scheduler Service start then stop after a few seconds

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

NPrintring Web Engine and Scheduler Service start then stop after a few seconds

Last Update:

Sep 9, 2021 4:52:56 AM

Updated By:

Sonja_Bauernfeind

Created date:

Aug 21, 2019 10:14:41 AM

Qlik NPrinting Scheduler service and Web Engine service go down.
The services run for some seconds, then they stop automatically.
Tasks and reports cannot be executed.
The Qlik NPrinting Web Console cannot be started.
On restart of the NPrinting services the Scheduler service and WebEngine service fail immediately.


Following or similar error(s) in RabbitMQ log:


=ERROR REPORT==== 19-Aug-2019::16:07:55 ===
Channel error on connection <0.356.0> ([FE80::D0DD:64:E4D8:30C7]:49858 -> [FE80::D0DD:64:E4D8:30C7]:5672, vhost: '/', user: 'remote'), channel 3:
{amqp_error,not_found,
"no queue '0ad3a42a8818435686ac4f71adafc1c7' in vhost '/'",
'basic.consume'}

[error] <0.641.0> Error on AMQP connection <0.641.0> ([fe80::1879:13f7:4814:751d]:49992 -> [fe80::1879:13f7:4814:751d]:5672 - Qlik.NPrinting.Engine.exe, vhost: '/', user: 'remote', state: running), channel 0:
operation none caused a connection exception connection_forced: "broker forced connection closure with reason 'shutdown'"
[error] <0.650.0> Error on AMQP connection <0.650.0> ([fe80::1879:13f7:4814:751d]:49993 -> [fe80::1879:13f7:4814:751d]:5672, vhost: '/', user: 'remote', state: running), channel 0:


Error reported by the Scheduler and Webengine retrieved from the application events (Source: .NET Runtime)


Application: Qlik.NPrinting.Scheduler.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: NHibernate.StaleStateException
at NHiberApplication: Qlik.NPrinting.Scheduler.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.nate.AdoNet.Expectations+BasicExpectation.VerifyOutcomeNonBatched(Int32, System.Data.IDbCommand)
at NHibernate.Persister.Entity.AbstractEntityPersister.Delete(System.Object, System.Object, Int32, System.Object, NHibernate.SqlCommand.SqlCommandInfo, NHibernate.Engine.ISessionImplementor, System.Object[])
at NHibernate.Persister.Entity.AbstractEntityPersister.Delete(System.Object, System.Object, System.Object, NHibernate.Engine.ISessionImplementor)
at NHibernate.Action.EntityDeleteAction.Execute()
at NHibernate.Engine.ActionQueue.Execute(NHibernate.Action.IExecutable)
at NHibernate.Engine.ActionQueue.ExecuteActions(System.Collections.IList)
at NHibernate.Event.Default.AbstractFlushingEventListener.PerformExecutions(NHibernate.Event.IEventSource)
at NHibernate.Event.Default.DefaultFlushEventListener.OnFlush(NHibernate.Event.FlushEvent)
at NHibernate.Impl.SessionImpl.Flush()
at Qlik.NPrinting.Repo.Service.SessionManager.WithSession[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Func`2<NHibernate.ISession,Boolean>, System.Data.IsolationLevel, Boolean)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

 

Environments:

NPrinting April 2018
NPrinting June 2018
NPrinting September 2018
Nprinting November 2018
NPrinting February 2019

 

Resolution:

Please Upgrade to Latest version of NPrinting
Issue ID OP-8072 was resolved in the Qlik NPrinting April 2019 release.
It is not recommended to attempt a manual repair since the issue is resolved by upgrading to a supported version of NPrinting.


An issue was discovered where the user audit table was growing exponentially due to a high number of daily task executions and the many users associated with those task. (One example of high volume was where 1000 tasks were executed per hour with several hundred user recipients in each task.) Also we discovered some cases where Qlik NPrinting Web Engine and Scheduler Service start then stop after a few seconds due to audit table was growing too big.

Labels (1)
Version history
Last update:
‎2021-09-09 04:52 AM
Updated by: