Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Running into random General Script Errors when storing QVDs on a script that loops through each day in a date range, loads data from QVD, adds new data, and stores QVD. There are no other apps/processes interacting with the QVDs and we've tried the reload on multiple machines. We've also tried inserting SLEEP statements immediately following the STORE...results are no different. The General Script Error does not occur on the same record or at the same time but it does occur on just about every reload of this data. I've inserted TRACE statements to identify where it's failing and I'll then narrow my data load to the range of the failed record and the reloads finishes successfully. Any thoughts?
My guess is that you're both reading and loading from these QVDs and the store function seems to always lose. If it's happening at different parts of the script I would say it's all about timing. Have you looked at the logs?
Hi,
Make sure that the user who is trying to update the QVD has the full right on the QVD file. (Windows Security of the file)
Regards,
Kaushik Solanki
I would check if your anti virus program are scanning the catalogs.
If you have any.
Hello, Kevin!
Today I have experimented the same problem and it disappeared after renaming the QVD archive and restarting QlikView. It seems to me that the problem is related to the fact that the store operation cannot proceed because the operating system, QlikView or both are blocking the file for write.
In your case, I believe the solution would be to perform a file deletion or rename before storing the QVD.
I hope this helps.
Hi,
I've had a similar problem. My problem was that "Copy" a syncing program was uploading the QVDs that I just stored. If I reloaded a second time, when the QVDs where uploading. I received the general script error in the log.
When I pause the syncing application. The reload works perfectly.
,KR Koen
See Avoid General Script Error in STORE command
I am using Sysinternals handle.exe to avoid the error.
Marcel
In case this helps anyone running into this problem - I have just encountered it with a qvd builder that has been working fine for months. Changing the name of the output qvd allowed the qvw script to complete without error. It turns out the system was locking the file (still thought it was in use") so was not allowing deletion or any other action.
Oli
I realize this is an old thread, but the only way that I have been able to correct this is to restart the QDS. It works every time.
mike