Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Reload Issue

Hello All,

I have few qvd generators and a final application which i have been scheduled for reload and the reload was happening succesfully.bt 1 qvd generator has not reloaded from yestrday morning.rest all reload is done.

when i try to open the application(failed app) it is showing Failed to load.

what can be the issue ??

please suggest..!!

Thanks in advance..

7 Replies
qlikmsg4u
Specialist
Specialist

Hi Reena,

Please post the failed application log file to understand

Kushal_Chawda

Please check the logs generated

avinashelite

I think the app i not fully written or not saved by the server after the reload or still the task is running .....

try to copy the app to your local and try to open with out data mode this should work

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Maybe one reload engine got stuck or managed to destroy the original generator QVW...

If you have a copy somewhere in you development environment, replace the broken one with the copy and launch the reload task in QMC.

How did the last reload of this generator end in QMC? As "Failed" or is it still marked as "Running"?

Peter

Not applicable
Author

hello..

since the reload has not happened there is no log files and the schedule is through Batch file for that application.

when i tried copying the application it is not getting copied even.,.

Peter_Cammaert
Partner - Champion III
Partner - Champion III

You are not using a QlikView Server to perform these sequenced reloads? The QlikView Server has builtin technology that makes sure no partial or broken QVWs are created when reloads fail midway. In a Task Scheduler setup there is no such guarantee.

Better delete the broken QVW and replace it iwth a fresh copy. You do have backup copies, don't you?

Not applicable
Author

Yea..i do have  a back up application. But the reason for the file corruption is unknown !!!