Qlik Community

New to QlikView

Discussion board where members can get started with QlikView.

Announcements
Modernize Your QlikView Deployment webinar, Nov. 3rd. REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

Why won't my script reload on the server?

Good morning,

I use a set of scripts to run multiple store commands to extract data from a database using an ODBC connection.

2 of my scripts fail when scheduled to reload on the server, but I am able to reload these scripts via my local machine.  All of the other scripts, with all of the store commands saving the same folder, work without issue.

Below are two scripts that are currently scheduled on the server, the first of which runs without issue and the second fails every time.

tblJournalPart1:

LOAD CallType, ContactType, ContactUnique, CreatingUser, CreationDate, DiaryDate;

SQL SELECT CallType, ContactType, ContactUnique, CreatingUser, CreationDate, DiaryDate

WHERE CreationDate + 90 >= CURDATE();

STORE tblJournalPart1 INTO '\\HCR-WX01\AnalyticalData\Scripts\tblJournalPart1Export.csv' (txt);

tblENIK:

First 200000 LOAD AccountCode, CreatingUser, AmendmentDate, CreationDate, BillingStatus;

SQL SELECT AccountCode, CreatingUser, AmendmentDate, CreationDate, BillingStatus

WHERE CreationDate + 250 >= CURDATE();

STORE tblENIK INTO '\\HCR-WX01\AnalyticalData\Scripts\tblENIKExport.csv' (txt);

1 Solution

Accepted Solutions
Highlighted
Not applicable

Thanks again for all of your help.

The issue is now fixed, and hopefully won't happen again, but this is what I believe was happening.

One of the scripts had so much data that it was overloading the server and failing, this script ran at the same time as another script, which failed also ( I assume because the server was overloaded with the other script?).

We reduced the amount of data going in to the first script and this resolved the issue for both of them

View solution in original post

6 Replies
Highlighted

Scripts usually fail for a reason. The actual cause of failure can be found in the DocumentLog.txt on your server (see the Distribution Service log folders). Open a DocumentLog.txt file of a failed reload and navigate to the end. If no DocumentLog can be found, the failure may occur even before your document is loaded. In that case, check the TaskLog.txt file.

Most probable causes of failure:

  • To reload a document, the server uses a different Windows account than you do on your machine. With an account come file/folder permissions, database access permissions, network access and such.
  • On a server, multiple simultaneous tasks may try to access the same files for reading, writing or both. On your personal machine, you usually reload only one document at a time. The server may experience file access conflicts.
  • Section Access (you probably don't use that in your QVD generator but I'm listing this item anyway) is a tricky thing and is also tied to a particular account. If the service account of your QlikView server isn't present in your SA table but your personal account is, then the outcome is very predictable.
  • ...

If you need further assistance, please post both log files of a single failed reload attempt.

Best,

Peter

Highlighted
Not applicable

Thanks for the reply.  I will look at the log files to see if there is any more information in there.  I'll also look into the most probable cause of failure you posted.

Highlighted

Hi Phil,

The reload fails means there are N no of reasons will be there but,what Error message you are getting as a pop up ?

1) May be the path you mentioned is not correct some times

2) For cross verification purpose just comment first table code and reload only 2nd table then we can observer correct failure with Doc.log

so that we can help you.

if possible post your code and mention error message you got then easily our folks will help to you.

Highlighted
Specialist
Specialist

Make sure that the qlikview services are running with accounts that have read and write access to the folders you use in your STORE commands.


Robert


Svebeck Consulting AB
Highlighted
Not applicable

Thanks again for all of your help.

The issue is now fixed, and hopefully won't happen again, but this is what I believe was happening.

One of the scripts had so much data that it was overloading the server and failing, this script ran at the same time as another script, which failed also ( I assume because the server was overloaded with the other script?).

We reduced the amount of data going in to the first script and this resolved the issue for both of them

View solution in original post

Highlighted
Specialist
Specialist

Ok Great you found the solution! 


Mark your own answer as the "correct answer" so other members can learn from it!


Regards 

Robert

Svebeck Consulting AB