failed task status

[#1]

Hi All,

I have a reload task say task1 which gets executed successfully everyday but on the QMC/QEMC status it shows failed.

So the task followed by task1 is not triggered,

Here is some portion of publisher task log.

The Source Document reload complete. DocumentPath=F:\qvsdocs\binary\publish\invoice.qvw
8/16/2010 07:46:32.9354084 Information Memory Allocation Delta for this file=1000.76 Mb. Available Physical Memory Before Reload=4848.20 Mb. Available Physical Memory After Reload=5562.30 Mb. Total Physical Memory=5562.30 Mb.
8/16/2010 07:46:36.1072225 Information The Source Document was reloaded successfully.
8/16/2010 07:46:39.1071649 Warning Read Document Log was aborted
8/16/2010 07:46:39.1227896 Information Initializing Reload (0), Finished (2525015)
8/16/2010 07:46:39.1384143 Information Reload finished successfully.
8/16/2010 07:46:39.1384143 Information Saving document
8/16/2010 07:48:46.9953344 Information Initializing save (0), Copying permissions to new file (0), Saving F:\qvsdocs\binary\publish\200630f9-a17e-458d-8950-3c05c9ddb19a_invoice.qvw.tmp (0), Moving temp file to new file (127734), Deleting old file (127750)
8/16/2010 07:48:47.0578332 Information Closing the document.
8/16/2010 07:49:02.9950272 Warning The QlikView Engine isn't responding to close command, it will be killed (Please ignore logged errors about the kill).
8/16/2010 07:49:02.9950272 Information Killing the QlikView Engine. ProcessID=5632
8/16/2010 07:49:03.0262766 Error Could not close the SourceDocument. Exception=System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
at QlikView.Doc.CloseDoc()
at QVBWrapper.Document.NiceCloseThread(ILogBucket i_LogBucket)
8/16/2010 07:49:03.0419013 Error Could not request the QlikView Engine process to quit.. Exception=System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at QlikView.ApplicationClass.Quit(Int32 _ExitCode)
at QVBWrapper.Document.NiceCloseThread(ILogBucket i_LogBucket)
8/16/2010 07:49:03.1044001 Information Closed the QlikView Engine successfully. ProcessID=5632
8/16/2010 07:49:03.1044001 Information Initializing (0), Finished (16110)
8/16/2010 07:49:03.1044001 Error Reload failed. Distribution skipped.
8/16/2010 07:49:03.1044001 Error The task "Reload_Publish_Invoice" failed. ErrorCount=3
8/16/2010 07:49:03.1200248 Information Sending Alert Mail to 1 recipients.

Any help will be appreciated.

thank you

[#2]

I have posted this issue 2nd time but not heard any response.

Can anybody will help me to come out from this issue.

[#3]

Can anybody will help me out.

[sathishkumar_go]

Hi Santhosh,

U r reloading the application by batch file or QlikView Scheduler(In qlikview Server)?

-Regards

Sathish

[#5]

Dear Satish,

The log i have shown is itself stating it is publsher log.

It means i am scheduling from publisher.

[#6]

Have you tried deleting the task and recreating it?

Are you calling any custom functions in the load script? I recall another forum poster having a problem similar to yours and they found that custom functions weren't working.

[sathishkumar_go]

Dear Santhosh,

I think everday its reloading but it shows failed. just check in QMC, SELECT THAT APPLICATION AND GOTO--> Reload

Deselect the Enable button and apply

Regards

Sathish

[brindlogcool]

Hi I am also getting the same warning "Warning Read Document Log was aborted" in the task during EDX. Any suggestions

[korsikov]

This can happen if you have very large documents handled by the QlikView Engine.

However there is a possibility to modify the time the Distribution Service will wait for the document to close.

Open the config file for the Distribution Service ([Install path]\QlikView\Distribution Service\QVDistributionService.exe.config) and modify/add the setting "SECONDSTOWAITBEFOREQVBKILL".

Default value should be 16.

Example where it has been changed to one minute:

<add key="SECONDSTOWAITBEFOREQVBKILL" value="60" />

[jeremy_kofoot]

So one thing I would look at is the document log for the file being reloaded.  I have found that the task log doesn't do a good job of saying why a task failed, but if you look at the document log it gives the exact point in the file where the task failed on.  So first I would make sure that document log is turned on in the file.  If it is already turned on then look at the document log, if not please turn document logging on and reload the app.  This should be able to give you more information on why the task is failing.