sd_jexec.exe crash in StopOrderAbort

book

Article ID: 223185

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Software Delivery

Issue/Introduction

Every time SD Agent is started, sd_jexec.exe is crashing.

A file crash_sd_jexec_*.txt could be generated under DSM\logs containing :

 

sd_jexec.exe caused an EXCEPTION_ACCESS_VIOLATION in module sd_jexec.exe at 0023:00890AED, StopOrderAbort::StopOrderAbort()+216221 byte(s)

Call Stack:
0023:00890AED (0x00830000 0x00000000 0x006E38BA 0x0000000A) sd_jexec.exe, StopOrderAbort::StopOrderAbort()+216221 byte(s)
0023:0089A044 (0x0026D000 0x74AB62A0 0xA5730E34 0x0053F944) sd_jexec.exe, InPossession::operator=()+22164 byte(s)
0023:74AB62C4 (0x0026D000 0xBA2C2B8A 0x00000000 0x00000000) KERNEL32.DLL, BaseThreadInitThunk()+0036 byte(s)
0023:779C1B69 (0xFFFFFFFF 0x779E33D8 0x00000000 0x00000000) ntdll.dll, RtlSubscribeWnfStateChangeNotification()+1081 byte(s)
0023:779C1B34 (0x0089A1CE 0x0026D000 0x00000000 0x00000000) ntdll.dll, RtlSubscribeWnfStateChangeNotification()+1028 byte(s)


Last lines in TRC_USD_SDAGENT*.log are :

 

170821-00:24:01.0739746L|004732|000015c4|SDAgent |  |sdnlsif |000053|ERROR  | Error init NLS
170821-00:24:01.0756212L|004732|000015c4|SDAgent |  |        |000000|ERROR  | #################### HW Exception occurred [PID:4732] ####################

 

 

In Event Viewer Application, Following Application Error appear :

Faulting application name: sd_jexec.exe, version: 14.0.2000.255, time stamp: 0x59b27342
Faulting module name: sd_jexec.exe, version: 14.0.2000.255, time stamp: 0x59b27342
Exception code: 0xc0000005
Fault offset: 0x00060aed
Faulting process id: 0x121c
Faulting application start time: 0x01d78ffeabfaf7a7
Faulting application path: c:\Program Files (x86)\CA\DSM\Bin\sd_jexec.exe
Faulting module path: c:\Program Files (x86)\CA\DSM\Bin\sd_jexec.exe
Report Id: b8268dab-9b1c-4cfe-b20b-599a34a8efe4
Faulting package full name: 
Faulting package-relative application ID: 

Cause

This problem could be cause by an invalid localename value in registry key :
HKEY_USERS\.DEFAULT\Control Panel\International\localename
 
Example :
HKEY_USERS\.DEFAULT\Control Panel\International\localename = hu
could cause the crash

Environment

CA Client Automation - Any version on Windows

Resolution

If
HKEY_USERS\.DEFAULT\Control Panel\International\localename = hu
 
then execute this :
reg ADD "HKU\.DEFAULT\Control Panel\International" /v localename /d "hu-HU" /f
 
 
If it is other value, then execute this :
reg ADD "HKU\.DEFAULT\Control Panel\International" /v localename /d "en-US" /f
reg ADD "HKU\.DEFAULT\Control Panel\International" /v locale /d "00000409" /f