General Script Error

[wonkymeister]

Hi,

My QMC/Server has started to fail to load documents. This started happening about a week ago and so far its happened to 3 QVD loaders (scripts that do the main load from our data warehouse and store to QVD to be read by other apps).

These are established Apps, where nothing has changed. The error from the Log File is a "General Script Error", just before it writes to the QVD.

9/11/2014 11:10:09: 0351  STORE MyData INTO .\QVDs\MyData.qvd

19/11/2014 11:10:09:       General Script Error

19/11/2014 11:10:09:       Execution Failed

19/11/2014 11:10:09:      Execution finished.

any ideas? As you can imagine this is a big issue as i have various applications updating daily.

cheers.

[alexandros17]

try:

1) STORE MyData INTO MyData.qvd that is without defining path

2) verify that you have write permission in that directory

let me know

[michael_anthony]

It could be a locking issue.  If this qvw is writing the .qvd and a consumer of the .qqvd is trying to read at same time it may stop the write.

We had this problem as have a complicated batch window.  Our solution was to create the qvd and then immediately copy it with an execute statement to MyData_4_Read.qvd.  the consumer qvw's only read from the copy.  This prevented the locks.

[wonkymeister]

its odd

these loaders have ran fine for 12 months or so. its not the path as its never been an issue and other loaders use the same path

its not a write permission on the server

and it cant be a locking issue as we use layers i.e. first we load from SQL to QVDs, then we use another layer to load from QVD

[simondachstr]

Not enough space on the disc maybe?

[wonkymeister]

should be stacks of drive space but i'll check.

[ashfaq_haseeb · Accepted solution]

Hi,

Check below for error codes.

http://community.qlik.com/docs/DOC-5342

May be you try below

STORE MyData INTO 😧\QVDs\MyData.qvd(qvd);

D was example, check your.

Open your Qlik document in Desktop --> Go to document properties --> General -->select Generate Logfile.

Now you will find detailed log file in the same path pinpointing to exact issue.

Hope it helps.

Regards

ASHFAQ

[wonkymeister]

(qvd) before the semicolon has solved the problem - or appears to anyway.

odd

we have lots of apps running and some have (qvd) in the code and some don't (earlier versions don't, its something that we've started to add to the code recently through best practice etc)

so

INTO $(vQVDsPath)MyData.qvd; has been failing all morning

and

INTO $(vQVDsPath)MyData.qvd(qvd); has successfully ran.

cheers for all the help/advice/comments people.