AnsweredAssumed Answered

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

Question asked by DanielDarling607133 on Oct 1, 2015
Latest reply on Oct 1, 2015 by DanielDarling607133
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.

Outcomes