Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

habermst
New Contributor II

NPrinting 17 - Cache rebuild not stable

Hello Community

I have an Issue with thet triggers for the cache rebuild. I am currently running the june version (17.4). I've created a trigger (daily, once at 06:00 AM). Sometimes the rebuild works, sometimes it fails... For example, here 4 times in a row:

fails.png

From the Log File: (I guess sometimes NPrinting can't lock the DB? -> ...Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Qlik.NPrinting.Repo.Model.DataConnection#8a63d5c8-3933-4699-aead-47c0380fe1e7] occurred)

Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob20170714T060000.000+02:00INFOKSL-VW2K251000b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask20170714T060000.022+02:00INFOKSL-VW2K251008a63d5c8-3933-4699-aead-47c0380fe1e7b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Common.Task.BaseEngineTask`1[[Qlik.NPrinting.Common.Task.GenerateConnectionCacheTaskConfig, Qlik.NPrinting.Common, Version=17.4.0.0, Culture=neutral, PublicKeyToken=null]]20170714T060000.037+02:00WARNKSL-VW2K25100007d6099a7-4fab-4161-8260-784a05b64e41000Cannot run Scheduler task 7d6099a7-4fab-4161-8260-784a05b64e41, exception Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Qlik.NPrinting.Repo.Model.DataConnection#8a63d5c8-3933-4699-aead-47c0380fe1e7] occurred
Qlik.NPrinting.Repo17.4.0.0Qlik.NPrinting.Repo.Plan.ReportFailurePlanNodeExecutor20170714T162823.181+02:00ERRORKSL-VW2K25100000000000-0000-0000-0000-0000000000000865dc91e-0b80-4be1-ab16-9418f0db147b00Failed report generation for report 865dc91e-0b80-4be1-ab16-9418f0db147b user ddd17ebe-6260-4faf-91b2-f2de9ac721a0 exception Qlik.Reporting.Reports.Tree.Exceptions.FailedReportException: Report generation failed. Error in node of type Qlik.Reporting.Reports.Tree.Template.DatasetNode for request 72b28838-1b77-4f8a-af91-1a63b7834416↓unknown↓Failed object: O\Document\CH622↓Template id: CH622_Level, template level: root↓Request filter: Filters: [], Bookmark: , Void: False↓↓   bei Qlik.Reporting.Reports.Tree.Template.CycleNode`4.ApplyFailure(FailureContentNodeResponse response, TcTransformationContext transformationCtx)↓↓   bei Qlik.Printing.Trees.TcTransformation.ApplyResponse(IContentNodeResponse response)↓↓   bei Qlik.Printing.TreeTransformationService.Process(IReportRequest reportRequest, IContentNodeResponse contentNodeResponse)
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob20170715T060000.000+02:00INFOKSL-VW2K251000b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask20170715T060000.017+02:00INFOKSL-VW2K251008a63d5c8-3933-4699-aead-47c0380fe1e7b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Common.Task.BaseEngineTask`1[[Qlik.NPrinting.Common.Task.GenerateConnectionCacheTaskConfig, Qlik.NPrinting.Common, Version=17.4.0.0, Culture=neutral, PublicKeyToken=null]]20170715T060000.031+02:00WARNKSL-VW2K2510000da228101-5ac8-4e68-9a49-ff938ebc5562000Cannot run Scheduler task da228101-5ac8-4e68-9a49-ff938ebc5562, exception Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Qlik.NPrinting.Repo.Model.DataConnection#8a63d5c8-3933-4699-aead-47c0380fe1e7] occurred
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob20170716T060000.000+02:00INFOKSL-VW2K251000b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask20170716T060000.029+02:00INFOKSL-VW2K251008a63d5c8-3933-4699-aead-47c0380fe1e7b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Common.Task.BaseEngineTask`1[[Qlik.NPrinting.Common.Task.GenerateConnectionCacheTaskConfig, Qlik.NPrinting.Common, Version=17.4.0.0, Culture=neutral, PublicKeyToken=null]]20170716T060000.041+02:00WARNKSL-VW2K25100009134c48f-e20c-4c65-84e9-7210623df5f0000Cannot run Scheduler task 9134c48f-e20c-4c65-84e9-7210623df5f0, exception Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Qlik.NPrinting.Repo.Model.DataConnection#8a63d5c8-3933-4699-aead-47c0380fe1e7] occurred
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob20170717T060000.000+02:00INFOKSL-VW2K251000b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask20170717T060000.022+02:00INFOKSL-VW2K251008a63d5c8-3933-4699-aead-47c0380fe1e7b12e9db3-ebd9-4bb2-a331-40f58dac1e210000Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Common.Task.BaseEngineTask`1[[Qlik.NPrinting.Common.Task.GenerateConnectionCacheTaskConfig, Qlik.NPrinting.Common, Version=17.4.0.0, Culture=neutral, PublicKeyToken=null]]20170717T060000.037+02:00WARNKSL-VW2K251000001f4c6b1-46da-4a28-a04a-9ce7dd4c65cb000Cannot run Scheduler task 01f4c6b1-46da-4a28-a04a-9ce7dd4c65cb, exception Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Qlik.NPrinting.Repo.Model.DataConnection#8a63d5c8-3933-4699-aead-47c0380fe1e7] occurred

18.07. wokrs fine, 19.07. fails again and 20.07. it works again:

update.png

Is this a bug? Or am i doing something wrong?

Also, the run verification gives me an error:

rf.png

The Qlik NPrinting Engine and the QlikView Server are both running on the same machine. I can log on to the machine with both users. Do I need to change any settings?

Thank's for any help & best Regards!

19 Replies
kirkjoserey
New Contributor II

Re: NPrinting 17 - Cache rebuild not stable

Hi,  Stefan

Consider this.  The User Account  used to Run Qlik NPrinting Services needs to be in Administrators Group of the server thats runs QlikView Server. 

I thinks thats why you got the Error : "The account used to  run ......"

regards,  @kirkjoserey

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting 17 - Cache rebuild not stable

Hi,

on top of that  - it not only needs to be a local Administrator on QlikView server, but also needs to belong to QlikView Administrators group.

all is very well described in help document:

https://help.qlik.com/en-US/nprinting/June2017/Content/GettingStarted/HowCreateConnections/Create-Co...

also consider whether your tasks/triggers are not overlapping with other publish task?

cheers

Lech

cheers Lech
When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution.
Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
habermst
New Contributor II

Re: NPrinting 17 - Cache rebuild not stable

Hi Lech & Rey

Thanks a lot for your inputs!

The qlik NPrinting user is part of the local administratior Group but not a member of the QlikView Administrators group. I will change that and see how the connenction rebuild works over the weekend and give another feedback.


Have a nice weekend!


best regards

Stefan

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting 17 - Cache rebuild not stable

Hi - to get it all working properly you have to make sure you have ALL requirements met, else it will once work another time may not work etc...

cheers

Have a nice weekend

Lech

cheers Lech
When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution.
Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting 17 - Cache rebuild not stable

btw.. Is this local connection or qvp:?

If it is local maybe your NPrinting engine server does not have enough capacity to open document locally as it needs to have anough memory and CPU to do it then on NPrinting Engine box.

That is why i strongly suggest to use qvp connection as it is using power of QV box.

regards

Lech

cheers Lech
When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution.
Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
habermst
New Contributor II

Re: NPrinting 17 - Cache rebuild not stable

Hi Lech,

It is a qvp Server Connection. But nPrinting and QlikView are running on the same machine:connection.png

Best Regrads

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting 17 - Cache rebuild not stable

This is another not recommended configuration as NPrinting will suck up all possible resources and qlik will do the same which may have some impact on cache build process

Also - i believe NPrinting has dedicated account user (different than qv server service account user)! Right?

cheers

Lech

cheers Lech
When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution.
Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
habermst
New Contributor II

Re: NPrinting 17 - Cache rebuild not stable

Hi Lech

Yes, I've read that before. But at the moment we only get one server, so it has to work (if I'm not mistaking it also says in the documentation that it's supposed to work with both installation on one machine). And we use different users for the QlikView and NPrinting services.

Another question: The above error is gone now that I've added the user to the group. But now I'm getting another one (The document exists):

21-07-_2017_10-13-10.png

Btw. if I rebuild the cache manually, everything just works fine.

Thanks for your help & best regards

Stefan

EDIT:

This Verify connection errors when setting up a connection to QlikView in Qlik NPrinting ‒ Qlik NPrinting says:

The document exists.

The document specified does not exist.

Verify the document and path are entered correctly.

But this seems to be wrong. Since i can rebuild the connection and document exists?

Lech_Miszkiewicz
Honored Contributor III

Re: NPrinting 17 - Cache rebuild not stable

i am not sure.. that means are you sure you point to right location?

cheers Lech
When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution.
Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.
Community Browser