Error Message :
U0000001 NO DATA (end of file, invalid key, no message...)
If *API (CallAPI) tasks are used, it's possible that the following forced trace files are generated after doing a COLD start of the Automation Engine (AE):
Root Cause: During a COLD start the *API (CallAPI) tasks are not set to inconsistent and within a COLD start the MQ* tables are truncated.
OS Version: N/A
Upgrade to Automation Engine version 11.1 or newer as the behavior has been improved.
Fix Status: Released
Automation Engine 11.1 - Available
Set the status of the API (CallAPI) objects in the Activity Window to inconsistent and then just cancel them manually with 'Status Ready' for start.