Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

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
Anonymous
Not applicable
Author

Hmmm, yeah, pretty sure This is the folder on the server:

folder.png

This is in the paht in the mgmt console:

path.png

I also can open reports, edit them, preview, send etc. using that connection.

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi,

I usually open in server a document from a desktop qlikview and look at the path which is shown on top window bar - like in here:

Re: Nprinting 17 server connection to a qvw

i would also try to use server name instead of localhost

regards

Lech

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
czm
Employee
Employee

Hi Stephan,

the verification fails because of a known issue (the fix will be released with next upcoming version) with string case. The folder is Accesspoint while you connection says "AccessPoint". Moreover I'm quite sure that also localhost could create issue: the fact that reload metadata works is just because the QlikView server and the NP Engine are installed in the same machine. If you would add another NP Engine to the cluster in the future that connection won't work for the second NP Engine, the one in which QlikView is not running on.

Try change connection in qvp://ksl-vw2k251/Accesspoint/InformatikManagement_GUI.qvw (if I got it right and if I understood correctly that the QlikView server runs on ksl-vw2k251 as NP Server and NP Engine) and please tell me if that works. Thanks.

Best regards,
Carlo

Anonymous
Not applicable
Author

Hello Carlo

Thanks for your answer. Sorry for the late replay, I was not in the office the past week.

I've chnaged the path as follows:

path.png

As You can see, the error persists. Furthermore, I can no longer reload the metadata. The error-line from the log file says:

Qlik.NPrinting.Engine17.4.0.0Qlik.NPrinting.Engine.Consumer.EngineConsumer20170802T105414.867+02:00ERRORKSL-VW2K25100000000Error while trying to add a resolver for connection navigator=qlikview;documentpath=qvp://ksl-vw2k251/ksl-qlikview$/Accesspoint/InformatikManagement_GUI.qvw. ERROR: An exception was thrown while invoking the constructor 'Void .ctor(Engine.Navigator.QlikView.QlikViewConnectionString, Engine.Navigator.QlikView.IQlikViewPool)' on type 'QlikViewContentNavigator'. ---> QlikView is not able to open the document qvp://ksl-vw2k251/ksl-qlikview$/Accesspoint/InformatikManagement_GUI.qvw (See inner exception for details.) Inner exception: System.InvalidOperationException: QlikView is not able to open the document qvp://ksl-vw2k251/ksl-qlikview$/Accesspoint/InformatikManagement_GUI.qvw↵↓   bei Engine.Navigator.QlikView.QV11.QlikViewDocument..ctor(String qlikViewApplicationPath, QlikViewConnectionString connectionString, Func`1 getLocalAndServerBuilder, IQlikViewArtifactsCachePool artifactsCachePool, IQlikViewWindowMonitor windowMonitor) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewDocument.cs:Zeile 456.↵↓   bei Engine.Navigator.QlikView.QV11.QlikViewNavigatorFactory.GetQlikView(QlikViewConnectionString connectionString) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewNavigatorFactory.cs:Zeile 79.↵↓   bei Engine.Navigator.QlikView.Module.QlikViewPool.Engine.Navigator.QlikView.IQlikViewPool.GetQlikView(QlikViewConnectionString connectionString) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QlikViewPool.cs:Zeile 79.↵↓   bei Engine.Navigator.QlikView.QlikViewContentNavigator..ctor(QlikViewConnectionString connectionString, IQlikViewPool pool) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QlikViewContentNavigator.cs:Zeile 23.↵↓   bei lambda_method(Closure , Object[] )↵↓   bei Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate() Inner stack trace:    bei Engine.Navigator.QlikView.QV11.QlikViewDocument..ctor(String qlikViewApplicationPath, QlikViewConnectionString connectionString, Func`1 getLocalAndServerBuilder, IQlikViewArtifactsCachePool artifactsCachePool, IQlikViewWindowMonitor windowMonitor) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewDocument.cs:Zeile 456.↵↓   bei Engine.Navigator.QlikView.QV11.QlikViewNavigatorFactory.GetQlikView(QlikViewConnectionString connectionString) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QVx\QlikViewNavigatorFactory.cs:Zeile 79.↵↓   bei Engine.Navigator.QlikView.Module.QlikViewPool.Engine.Navigator.QlikView.IQlikViewPool.GetQlikView(QlikViewConnectionString connectionString) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QlikViewPool.cs:Zeile 79.↵↓   bei Engine.Navigator.QlikView.QlikViewContentNavigator..ctor(QlikViewConnectionString connectionString, IQlikViewPool pool) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine.Navigator.QlikView\QlikViewContentNavigator.cs:Zeile 23.↵↓   bei lambda_method(Closure , Object[] )↵↓   bei Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate() Stack trace:    bei Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓   bei Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓   bei Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓   bei Autofac.Core.Resolving.InstanceLookup.Execute()↵↓   bei Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓   bei Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)↵↓   bei Autofac.ResolutionExtensions.ResolveNamed[TService](IComponentContext context, String serviceName, IEnumerable`1 parameters)↵↓   bei Autofac.Builder.RegistrationBuilder.<>c__DisplayClass1`1.<ForDelegate>b__0(IComponentContext c, IEnumerable`1 p)↵↓   bei Autofac.Core.Activators.Delegate.DelegateActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓   bei Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓   bei Autofac.Core.Resolving.InstanceLookup.Execute()↵↓   bei Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓   bei Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable`1 parameters)↵↓   bei lambda_method(Closure , String )↵↓   bei Qlik.Printing.QlikPrintingModule.GenericContentNavigatorFactory.Get(String connectionString)↵↓   bei Qlik.NPrinting.Engine.Consumer.BlockingContentResolverFactory.Get(Guid connectionId, String connectionString, IRequestBuffer buffer, Int32 initialMaxBatchSize, Int32& startupTime) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine\Consumer\BlockingContentResolverFactory.cs:Zeile 30.↵↓   bei Qlik.NPrinting.Engine.Consumer.EngineConsumer.AddResolverToConnection(Guid connectionId, String connectionString, Int32 bufferMaxSize, Int32 batchMaxSize, DateTime requestTimestamp) in c:\Jws\workspace\NP-REL-17.4.0.0-BR-01-build\server\NPrinting\src\Engine\Consumer\EngineConsumer.cs:Zeile 488.

Seems like nprinting is not able to open the file. But then I switched back to the localhost-string an changed the AccessPoint to Accesspoint and verification runs withouth an error:

path2.png

That way I'm also able to reload the meta data.

Best Regards

Stefan

czm
Employee
Employee

Hi Stefan,

it seems that it has been changed in qvp://ksl-vw2k251/ksl-qlikview$/Accesspoint/InformatikManagement_GUI.qvw instead of the correct one qvp://ksl-vw2k251/Accesspoint/InformatikManagement_GUI.qvw

There is a "ksl-qlikview$" in it that shouldn't be there, so this is the reason of the last failure.

Thanks

Anonymous
Not applicable
Author

Hi Carlo

Jesus, I didn't see that. Something went wrong during the copy / paste... and the networkfolder-path contains the $ sing, which i also removed. Now the verification is working, thanks for this! No more error there.

I will wait and see how the triggered metadata reload will work this week. I hope this will bring some improvement.

Best regards

Stefan

Anonymous
Not applicable
Author

Hi Carlo

Unfortunately, the reload failed again this morning. In the Web GUI arent any infomartions concerning the error. It only says Elapsed Time and failed. The NPrinting engine log didn't generate any entry this morning, only the scheduler log. These are the  lines:

Qlik.NPrinting.Scheduler17.4.0.0Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob20170803T060000.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.GenerateConnectionCacheEngineTask20170803T060000.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]]20170803T060000.037+02:00WARNKSL-VW2K2510000c27bab5c-753c-4ecc-beae-254e43666815000Cannot run Scheduler task c27bab5c-753c-4ecc-beae-254e43666815, 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

Is this a known error / Bug or what elese could I try to resolve this issue?

Best Regards

Stefan

czm
Employee
Employee

Hi Stefan,

I'm sorry for this issue. This is a totally different error: it is already known, traced in our internal bug tracking system and we are working on it. Unfortunately I don't know any workaround for it at the moment but I will inform you if something new arises.
I'll add a comment and a link to this thread to our internal tracking system, trying to ask for a solution.

Sorry to not being able to do more on it right now.

Best regards,
Carlo

Anonymous
Not applicable
Author

Hi Carlo

I see. Thanks for your efforts anyway. I'll leave this question / thread as unanswerd for now.

Hope to hear soon from you & thanks again.

Best regards,

Stefan

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Carlo, Stefan - let us know, when you find a solution for the other bug. It looked like services were not "talking" to each other. I may had a client who experienced similar behaviour and had to roll back to NPrinting 16...

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.