Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
I am facing a weird issues with Qlikview Server 11.20 64x
The application was running successfully on all previous attempts, but has started failing abruptly without any code change.
Currently the application loads around 129 Million records and fails while saving the app.
In the Logs all i can see is
08/05/2018 20:31:16: General Script Error
08/05/2018 20:31:17: Execution Failed
08/05/2018 20:31:17: Execution finished.
Current Settings:
Application has Initial Data Reduction Based on Section Access.
Things that I have tried:
Removed Initial Data Reduction Based on Section Access. -- No Luck
Removed Final Store QVD Command -- No Luck
Checked if the QVW itself has some checks on windows attribute (ie Read Only) -- No Luck -- No Attributes were applied
Checked if the Disk has enough Space -- Its ample space to save the QVD
Checked the CPU and Memory Usage -- No issues with that as well -- One thing that i noticed -- Before failing it spikes to 100% CPU and abruptly fails.
Currently I am trying to reduce the data, Lets see how it goes.
Update : Reduced 9mil records and the extract has ran successfully
Want to understand what is the issue about? Is it the Load capacity between the Qlikview version and Windows Server?
Meanwhile any help would be much appreciated
Have you made yourself and all of the qlik services into Admins in your Section Access script?
Did you search for the word 'error' in the log file? Any changes done to the script to cause this issue
?
HI,
There no error apart from General Script Error.
Anyway the thing that I was trying to reduce the data a load, It has worked.
To my surprise why would the reload would fail? May be load capacity between the Server and Qlikview vr ?
Yes, Joe, I am the admin
Hi,
Have you checked that no other documents are referencing the file you are trying to save.
Kind Regards
Kamiel
Are you storing QVDs in sequence? Or to put it differently, is there a STORE statement immediately before or after the one that fails? Then you may want to try by putting delays inbetween those successive STOREs (SLEEP statements)