Intermittent force trace files with “U0000001 NO DATA” are generated after doing a COLD start

Document ID : KB000087787
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
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):
 
U0000001 NO DATA (end of file, invalid key, no message...)
20170328/092447.202 - U0000001 NO DATA (end of file, invalid key, no message...) 
20170328/092447.203 - U0009909 TRACE: (Eingabespeicher) 110b67990 032768 
20170328/092447.203 - U0009909 TRACE: (Conversationssp.) 110b87a50 012168 
00000EE0 00000000 2A534352 49505420 20202020 >....*SCRIPT < 
00000000 25254442 30360068 00000000 00000000 >%%DB06.h........< 
00000010= 00000000 00000000 00000000 00000000 >................< 
00000410 00000000 00010000 00000001 13E88E10 >.............èŽ.< 
00000420 00000001 13E883A8 4E4E4A4E 494F524F >.....胨NNJNIORO< 
00000430 4D515352 56202020 20200000 2EC74F43 >MQSRV ...ÇOC< 
20170328/092450.836 - 27. 2017
 
According to this particular excerpt, one Agent tries to send the wrong ACV and the work processes tries to read the ACV message (in the table MQMEM), but it can not find it because of the AE COLD start.
 
The reason is that during a COLD start the *API (CallAPI) tasks are not set to inconsistent, and within a COLD start the MQ* tables are truncated.

 
Environment:
OS Version: N/A
Cause:
Cause type:
By design
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.
Resolution:
Upgrade to Automation Engine version 11.1 or newer as the behavior has been improved.

Fix Status: Released

Fix Version(s):
Automation Engine 11.1 - Available
Additional Information:
Workaround :
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.