topic Re: NPrinting 17 - Cache rebuild not stable in Qlik NPrinting

NPrinting 17 - Cache rebuild not stable

Anonymous — Thu, 20 Jul 2017 14:20:58 GMT

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:

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.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob	20170714T060000.000+02:00	INFO	KSL-VW2K251	0	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask	20170714T060000.022+02:00	INFO	KSL-VW2K251	8a63d5c8-3933-4699-aead-47c0380fe1e7	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.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:00	WARN	KSL-VW2K251	0	0	7d6099a7-4fab-4161-8260-784a05b64e41	0	Cannot 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.Repo	17.4.0.0	Qlik.NPrinting.Repo.Plan.ReportFailurePlanNodeExecutor	20170714T162823.181+02:00	ERROR	KSL-VW2K251	0	00000000-0000-0000-0000-000000000000	0	865dc91e-0b80-4be1-ab16-9418f0db147b	Failed 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.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob	20170715T060000.000+02:00	INFO	KSL-VW2K251	0	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask	20170715T060000.017+02:00	INFO	KSL-VW2K251	8a63d5c8-3933-4699-aead-47c0380fe1e7	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.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:00	WARN	KSL-VW2K251	0	0	da228101-5ac8-4e68-9a49-ff938ebc5562	0	Cannot 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.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob	20170716T060000.000+02:00	INFO	KSL-VW2K251	0	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask	20170716T060000.029+02:00	INFO	KSL-VW2K251	8a63d5c8-3933-4699-aead-47c0380fe1e7	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.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:00	WARN	KSL-VW2K251	0	0	9134c48f-e20c-4c65-84e9-7210623df5f0	0	Cannot 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.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob	20170717T060000.000+02:00	INFO	KSL-VW2K251	0	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask	20170717T060000.022+02:00	INFO	KSL-VW2K251	8a63d5c8-3933-4699-aead-47c0380fe1e7	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	0	Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.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:00	WARN	KSL-VW2K251	0	0	01f4c6b1-46da-4a28-a04a-9ce7dd4c65cb	0	Cannot 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:

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

Also, the run verification gives me an error:

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!

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Thu, 20 Jul 2017 19:19:02 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Thu, 20 Jul 2017 21:48:36 GMT

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-Connections.htm

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

cheers

Lech

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Fri, 21 Jul 2017 07:18:52 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Fri, 21 Jul 2017 07:21:08 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Fri, 21 Jul 2017 07:24:56 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Fri, 21 Jul 2017 07:39:04 GMT

Hi Lech,

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

Best Regrads

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Fri, 21 Jul 2017 07:42:40 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Fri, 21 Jul 2017 08:19:43 GMT

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):

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?

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Fri, 21 Jul 2017 08:28:21 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Fri, 21 Jul 2017 08:41:00 GMT

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

This is in the paht in the mgmt console:

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

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Sat, 22 Jul 2017 03:44:13 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

czm — Tue, 25 Jul 2017 11:09:31 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Wed, 02 Aug 2017 09:26:50 GMT

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:

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.Engine

17.4.0.0

Qlik.NPrinting.Engine.Consumer.EngineConsumer

20170802T105414.867+02:00

ERROR

KSL-VW2K251

Error 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:

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

Best Regards

Stefan

Re: NPrinting 17 - Cache rebuild not stable

czm — Wed, 02 Aug 2017 10:02:46 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Wed, 02 Aug 2017 12:27:38 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Thu, 03 Aug 2017 08:16:33 GMT

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.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.EnqueueTaskQuartzJob	20170803T060000.000+02:00	INFO	KSL-VW2K251	0	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	Triggering task b12e9db3-ebd9-4bb2-a331-40f58dac1e21 by trigger 7b9885df-099b-4cac-91c5-87802151772f
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.NPrinting.Scheduler.Task.GenerateConnectionCacheEngineTask	20170803T060000.017+02:00	INFO	KSL-VW2K251	8a63d5c8-3933-4699-aead-47c0380fe1e7	b12e9db3-ebd9-4bb2-a331-40f58dac1e21	0	Generating cache for connection 8a63d5c8-3933-4699-aead-47c0380fe1e7
Qlik.NPrinting.Scheduler	17.4.0.0	Qlik.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:00	WARN	KSL-VW2K251	0	0	c27bab5c-753c-4ecc-beae-254e43666815	Cannot 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

Re: NPrinting 17 - Cache rebuild not stable

czm — Thu, 03 Aug 2017 08:25:44 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Anonymous — Thu, 03 Aug 2017 08:47:59 GMT

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

Re: NPrinting 17 - Cache rebuild not stable

Lech_Miszkiewicz — Thu, 03 Aug 2017 21:50:50 GMT

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...