Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

External Task - starting a batch file

Hi,

I want to execute an a batch file via external task in QlikView Management Console.
My Command line statement is the following: "C:\Excel Export\QV_Excel_Export.exe" ID01

When executing this via CMD Command Line, it works fine - no problems.
When starting this task via QlikView Management Console nothing happens and the task shows a "Warning".

Heres the log:

(2010-07-30 07:33:54) Information: Executing ClusterID=1, QDSID=11b39504-12b5-8aaf-3b89-ca25b856e474QDSMain.ExternalProgramTask

(2010-07-30 07:33:54) Information: Starting task "Excel Test Task" (Attempt 1 of 1)

(2010-07-30 07:33:54) Information: Max run time: 1.00:00:00

(2010-07-30 07:33:54) Information: Executing "C:\Excel Export\QV_Excel_Export.exe" ID01

(2010-07-30
07:33:54) Information: Executing commandline: "C:\Excel
Export\QV_Excel_Export.exe ID01" in folder "C:\Excel Export".

(2010-07-30 07:34:01) Warning: Process exited with non zero exit code: -532459699 at 7/30/2010 7:34:01 AM

(2010-07-30 07:34:01) Information: Process exited with exit code: -532459699 at 7/30/2010 7:34:01 AM

(2010-07-30 07:34:01) Warning: The task "Excel Test Task" finished with warnings. WarningCount=1

Really need help. It's sort of strange because when entering my command line in via "CMD" it works fine.

Thanks!

1 Solution

Accepted Solutions
vgutkovsky
Master II
Master II

Try saving the commands as a .bat file and referencing the .bat file in the External Task (instead of putting the commands directly in the task).

Regards,

View solution in original post

3 Replies
vgutkovsky
Master II
Master II

Try saving the commands as a .bat file and referencing the .bat file in the External Task (instead of putting the commands directly in the task).

Regards,

StefanBackstrand
Partner - Specialist
Partner - Specialist

If you are on a Service Release before SR5, I would say that you need to upgrade if you see this kind of errors in when running external tasks.

Not applicable
Author

We are switching to SR5 soon.
Now we are using SR3. We already have a test server with SR5 now.
I tryed it also with the test server and sometimes it gives me the error again.

But it seems to work better with SR5 now.

Thanks for your help guys!