search cancel

JSCH activities throw U00011088 after upgrade to AE 21.0.x with old Agents and WP processes crash with Access violation

book

Article ID: 252829

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After a migration of AE 12.2.x to AE 21.0.x, keeping the Agents on the same old version (most Agents on versions 11.2.x or 12.x), some WP generate Force Traces continously and some JSCH objects do not execute the activities anymore at the Scheduled time with the error U00011088 :

U00011088 Task 'BI.VENTES.JOBP.VENTES' does not start because the scheduled start time lies before the start time of 'BI.VENTES.JSCH.VENTES'.

In the generated UC4Dump_*.txt, we can find the root cause of the WP crashes:

20221018/155053.265 -  U00011043 Activating event  'COM.UB_GM.EVFS.UB_AFFECTATION_FINE_ARTICLE' (RunID:  '0215224899' ).
20221018/155053.671 - U00009909 TRACE: (Message-Key: MQQWP_PK        00007FFC88EEA164 00004
                                00000000  4E000000                             >N...<
20221018/155053.671 -                                         >78<
20221018/155053.702 -  Access violation at 00007FFC96EC146C on read 0000000000000000
20221018/155053.702 -  U00009907 Memory dump 'Parameter List ' (Address='00000012A9FED620', Length='1296')
20221018/155053.702 -            00000000  25255352 30310400 00000000 20202020  >%%SR01......    <
20221018/155053.702 -            00000010= 20202020 20202020 20202020 20202020  >                <
20221018/155053.702 -            00000400  20202020 20202020 20202020 00000100  >            ....<
20221018/155053.702 -            00000410  20000000 D8730200 D88E6200 48081F00  > ...Øs..ØŽb.H...<
20221018/155053.702 -            00000420  2A534552 56455220 20202020 20202020  >*SERVER         <
20221018/155053.702 -            00000430  20202020 20202020 20202020 20202020  >                <
20221018/155053.702 -            00000440  4A504558 45435F52 00000000 20202020  >JPEXEC_R....    <
20221018/155053.702 -            00000450= 20202020 20202020 20202020 20202020  >                <
20221018/155053.702 -            00000470  20202020 00000000 47494649 5F414552  >    ....GIFI_AER<
20221018/155053.702 -            00000480  23575030 33312020 20202020 20202020  >#WP031          <
20221018/155053.702 -            00000490  20202020 20202020 4D515750 20202020  >        MQWP    <
20221018/155053.702 -            000004A0  9D4D2501 00000000 20202020 20202020  >M%.....        <
20221018/155053.702 -            000004B0= 20202020 20202020 20202020 20202020  >                <
20221018/155053.702 -            00000500  20202020 20202020 01000000 00000000  >        ........<
20221018/155053.702 -  U00009907 Memory dump 'Input Memory' (Address='00000145C389AE80', Length='32')
20221018/155053.702 -            00000000  54494D45 525F444F 30310000 00000000  >TIMER_DO01......<
20221018/155053.702 -            00000010  4556454E 54202020 4312D40C 2A000000  >EVENT   C.Ô.*...<

 

Every time the Above File Event COM.UB_GM.EVFS.UB_AFFECTATION_FINE_ARTICLE runs, the issue occurs.

On a similar scenario, it was also found that one Agent in 11.2.6 configured for 2 File Events in one of the clients, it was causing a lot of System Forced dump messages in the DWP logs and eventually they went all down one by one with the following kind of traces in the trc files:

05 - 20221126/215542.366 -  UCMAIN_R              RCV  CHGRED   frm UC4D#WP001                                INTERNAL MsgID: 0004210338 c-acv: 00000000
...
01 - 20221126/215542.381 - U00015006 System forced memory trace dump.

Environment

Automation Engine Release : 21.0.x

Context: Agent Windows 11.2.1 Running a File Event every minute (1440 times per day).

Cause

Defect on the Windows Agent 11.2.1.

The issue (WP force traces and eventually crashes) was caused by a Windows Agent 11.2.1 while launching some Event File jobs.

Resolution

Workaround:

Move the Jobs to be executed on another server with a more recent Windows Agent (on this case 12.2.2) and use network path to access the desired folder.

Solution:

Upgrade impacted Agent to a recent supported version, ie. Agent Windows 12.3.9 HF1 and restart the associated Events.