EXCEPTION_BREAKPOINT in module axc2p.exe at 0023.0x0048B301

Products

• Automation Point

Issue/Introduction

Since we have upgraded to  version 11.7.1 , each time we do an IPL on one of the mainframe partitions defined in Automation Point, the Autostart service aborts with the following error :  

14:21:22.016 T6184 C=NA Sev=5 UtilEventWait: 'Local\ASOSEM5019', rc = 4157, global handle = 5019, private handle = 1076.
14:21:22.016 T5820 C=NA Sev=F Task=17  SESSION MCSCOQU IO: (0,0,777,E)   axc2p.exe caused an EXCEPTION_BREAKPOINT in module axc2p.exe at 0023.0x0048B301,  failwithmessage()+599 bytes
14:21:22.016 T5820 C=NA Sev=F Task=17  SESSION MCSCOQU IO: (0,0,777,E)     cmd:axc2p   /hide
14:21:22.016 T5820 C=NA Sev=F Task=17  SESSION MCSCOQU IO: (0,0,777,E)     ver:CA Automation Point 11.7.1.0 Rev=33561  Sep 22 2022
14:21:22.016 T5820 C=NA Sev=F Task=17  SESSION MCSCOQU IO: (0,0,777,E)    

 

Environment

Release : 11.7

Cause

Tracing enabled during startup may cause this issue.

Resolution

Trace messages enabled during startup can produce an extreme amount of logging/tracing data and may lead to an AP crash. Turning off tracing if enabled may resolve this issue.

1) Open AP Configuration Manager for the server in question.

2) Go to "Expert Interface" -> "Infrastructure" -> "Debugging".

3) If the "Trace Messages" checkbox is ticked as in the screenshot below, untick it.

4) Click "OK".

5) Restart AP.