Unable to restart failed JOBF file transfers
search cancel

Unable to restart failed JOBF file transfers

book

Article ID: 87272

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U00063079 FT '8309281' unable to load the restart info file (StatusStore) 'C:\Program Files\UC4\Agents\Windows\TEMP\\FT0.sts' for FT '0',
reason: '2 - The system cannot find the file specified.'.

A failed JOBF file transfer is unable to restart because it always looks for the same file name, "FT0.sts" resulting in the above errror message.

Status store files generate different names each time so it should be looking for a unique.sts file name not always "FT0.sts."

Investigation
  1. Create a new JOBF job object.
  2. In the FROM section, select a single agent as the Source host and enter a directory path for a text file.
    1. EXAMPLE: C:\Automic\user_tests\hki\transferme.txt
  3. In the TO section, select a host group as the Target host and enter a directory path for the text file.
    1. Please ensure you already have an existing file called 'transferme.txt' in the target directory path so that we can force the JOBF to abort, which will allow the .sts files to stay.
    2. Under the 'File exists' sub-section, please select 'Cancel'.
 
Your test JOBF should look something like this:

 

<Please see attached file for image>

0EM0N000001husl.png
  1. Run the test jobf job and it should fail with an error that file already exists.
  2. Remove that existing file from the target directory path.
  3. Now, restart that same failed jobf job from the 'Last Restart Position'.
 
Results

 
Actual
The JOBF aborted with the error: C:\Program Files\UC4\Agents\Windows\TEMP\FT0.sts|0|2 - The system cannot find the file specified.
 
Expected
It will run the job successfully because the .sts file exists and can finally transfer the file from the source to target because there is no existing file in there yet.
Something to determine if I’m affected, steps to reproduce, etc.
 

Environment

OS Version: N/A

Cause

Cause type:
Defect
Root Cause: File transfer is looking for the same file name, "FT0.sts" when it should be looking for a unique.sts file.

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Automation Engine 12.1.0 - Available
Automation Engine 12.0.2 - Available
Automation Engine 11.2.5 - Available

Additional Information

Workaround :
N/A

Attachments

1558693620520000087272_sktwi1f5rjvs16mab.png get_app