topic Re: Reloading MetaData Of Connection Running EndlessTime in Qlik NPrinting

Reloading MetaData Of Connection Running EndlessTime

elmelavi — Wed, 15 Mar 2023 08:57:41 GMT

Hi,

I Have a Model That when i add an Object and start to reloading the MetaData but it shows up as running and even after 14 hours it's not completed and is still in the same state.

Add The Cache rebuild task for connection

On Status Running

I tried to dig into logs but i couldnt deduce the proper log to look into or even enable debug mode to.

we have upgraded the NPRINTING and QVIEW to the latest versions and tried again but in vain.

one thing i have noticed is that if in the first 2 hours i was unable to run any models in qview (stated it timed out after 45 minutes while waiting for node), i can run other models though the ram is still used 99% (256gb) with the caching process and cpu is at around 30% usage (12 cores, 24 threads).

The Version Of The NP And Qlik View Are Updated To The Letest Version:

Qlik NPrinting May 2022 SR4

Version: 22.15.14.0

any insights would be appreciated.

Best Regards

Lavi

Re: Reloading MetaData Of Connection Running EndlessTime

Ruggero_Piccoli — Wed, 15 Mar 2023 09:33:29 GMT

Hi,

Do a Run Verification in the connection and be sure all lines are green.

Be sure you are running a supported configuration https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/System-requirements_engine.htm

Be sure the connected document has only supported objects https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/ReportsDevelopment/Qlik-objects-supported-NP.htm

Check the workload of the Qlik NPrinting server and of the QlikView server during the cache generation. It could be that the .qvw is huge and it requires time.

Is the cache generated correctly at the end?

Best Regards,

Ruggero

Re: Reloading MetaData Of Connection Running EndlessTime

Lech_Miszkiewicz — Wed, 15 Mar 2023 09:36:01 GMT

Hi,

This looks like resource problem and has nothing to do with NPrinting so lets get facts straight:

how big is your qvw file on HD
how big is your qvw file when loaded to memory
are all sheets (also hidden) in this qvw possible to browse with all selections cleared
is this qvw supported? list of unsupported items is documented and MUST be 100% checked: https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/GettingStarted/HowCreateConnections/Connect-to-QlikView-docs.htm#anchor-1
what is your NPrinting connection (Local or QVP) - obviously there is huge difference in which resources are used in each of those connections (whether we are using NPrinitng server resources or QlikView server resources)
Provide info about QlikView server hardware
Provide info about NPrinting server hardware

If this model is causing such resource consumption then it needs to be worked on and optimized. I have seen so many times sloppy Qlik apps built which performed terribly and which require review by person who knows how to build data model and all required expressions to make such model work again.

Bottom line is that your model needs to be working without any issues on QlikVIew server and all other things need to be checked and verified.

cheers

Re: Reloading MetaData Of Connection Running EndlessTime

elmelavi — Wed, 15 Mar 2023 10:00:45 GMT

Hi Ruggero,

thanks for the prompt reply!

one of the first things we did was to run the connection verification and it was and is always green.

the model is nothing new and was not changed either and was running fine until recently.

it never finishes running as i stated even after 14 hours when it usually would finish after up to 2.5 hours max on the same machine.

we have larger and more complex models that finish running after 3.5 hours.

went over the supported objects and connected documents and they seem to be inline with the guidelines.

this model's size is 1.34gb and larger models twice its size and more run regularly fine.

Re: Reloading MetaData Of Connection Running EndlessTime

Ruggero_Piccoli — Wed, 15 Mar 2023 11:12:48 GMT

Hi,

Does this happen one time or multiple times? If it happened one it could be caused by something temporary.

Check if there are QlikView processes frozen.

Check the Qlik NPrinting log files to see if there are errors. You could stop the Windows services, move the old log files to a different folder, restart the services and run a metadata reload manually. In this way you will have shorted logs and you could isolate metadata reload errors easier.

Best Regards,

Ruggero

Re: Reloading MetaData Of Connection Running EndlessTime

Lech_Miszkiewicz — Wed, 15 Mar 2023 11:47:25 GMT

@elmelavi

Have you checked for hidden sheets in this app? If you have some unhide them, clear all selections and see how QlikView performs by going to each of them. We often forget about hidden sheets and they may carry a lot of problems.

Re: Reloading MetaData Of Connection Running EndlessTime

elmelavi — Wed, 15 Mar 2023 17:09:21 GMT

Hy Ruggeero

Regard To You Checklist

I Checked The Connection type and changed from server to local

and it fixed it out now it finished after half hour

Best Regards

Lavi

Re: Reloading MetaData Of Connection Running EndlessTime

Frank_S — Wed, 15 Mar 2023 18:48:15 GMT

@elmelavi

Keep in mind that switching to local connections means you will need to reload your NPrinting Connection regularly to ensure it doesn't encounter stale data.

Basically, reload your NP local connections if the QVW in the QMC is reloaded.

Kind regards...

Re: Reloading MetaData Of Connection Running EndlessTime

Lech_Miszkiewicz — Wed, 15 Mar 2023 20:13:09 GMT

Hi @elmelavi

this fix can indicate that QVP connection didnt work because maybe QlikView desktop version installed on Nprinting Machine was different then version of your Qlikview server?

Also it would be worth checking this: https://community.qlik.com/t5/Official-Support-Articles/NPrinting-diminished-execution-time-with-QVP-connection-versus/ta-p/1713126

Re: Reloading MetaData Of Connection Running EndlessTime

Lech_Miszkiewicz — Wed, 15 Mar 2023 22:09:09 GMT

That will also mean heav use of NPrinting server resources as local QlikView desktop is used to open qvw locally which will not have benefits of running app on server - that may potentially kill your NPrinting server (given that you may have multiple instances open of the same app locally)!!!