Automic Workload Automation

Expand all | Collapse all

REPORT could not be started causing job failure, what is root cause?

Jump to Best Answer
  • 1.  REPORT could not be started causing job failure, what is root cause?

    Posted 10-01-2015 03:23 PM
    Okay - so - this was a result of the file existing in two locations and the IF statement failing for some reason. 

    What would cause this error in the system? I've checked permissions and everything seems to be in order. We are running Automation Platform version 9.00A333-782 in a clustered setup between two nodes.

    edit: to add some more information as I am troubleshooting it appears the issue is with the prep_process that is being executed. The prep_process is running a WINCMD "IF EXIST" line. The line executes as expected but the report that is saved within the event is what is causing the failure.

    U0010038 Runtime error: Could not create data sequence 'FILETRANSFER'. Status: '0000001820', return code: '0000000000'.
    U0011000 'JOB.NAME' (RunID: '0006648568') could not be started on '<WIN>'. See next message.
    U0010038 Runtime error: Could not create data sequence 'FILETRANSFER'. Status: '0000001820', return code: '0000000000'.
    U0029003 Cannot open file 'C:\uc4\UC4V9Test\Agents\Windows\TEMP\EAAOOHEE.TXT', error code '2', error description: '2 - The system cannot find the file specified.'.
    U0011000 'REPORT' (RunID: '0006649400') could not be started on 'SERVER'. See next message.


  • 2.  REPORT could not be started causing job failure, what is root cause?

    Posted 10-01-2015 04:25 PM
    One thing that I would look at, is that <WIN> is a default HOST identifier suggesting you need to specify a real host instead of taking this default.


  • 3.  REPORT could not be started causing job failure, what is root cause?
    Best Answer

    Posted 10-01-2015 04:26 PM
    Thanks for the suggestion, but I set the host/user in the pre-process tab.

    I've found out that the issue is with the specific prep_process that I'm trying to execute. It is a WINCMD that runs an IF statement. It works in 1 client but none of the others and I can't locate what setting is different in that client.