sd_jexec.exe exception 0xC0000008

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

- In TRC_USD_SDAGENT*.log last lines before excpetion are :

160523-23:16:58.3637353L|009224|00001784|SDAgent | |sdjecachedcnfif.cpp |000166|INFO | Renaming C:\Program Files (x86)\CA\DSM\Agent\units\00000001\usd\sdjexec\3C2AB734-9EC6-4A85-A65A-94E7518A4E03.cwf to C:\Program Files (x86)\CA\DSM\Agent\units\00000001\usd\sdjexec\3C2AB734-9EC6-4A85-A65A-94E7518A4E03_4.crf
160523-23:16:58.3638308L|009224|00001784|SDAgent | |sdjecontainerif.cpp |003954|DETAIL | SDJEContainerIf::UnReportedResults() - Opened lockjobcheck registry key
160523-23:16:58.3638695L|009224|00001784|SDAgent | |sdjecontainerif.cpp |003961|DETAIL | SDJEContainerIf::UnReportedResults() - ContainerID in registry that locked job check is 3C2AB734-9EC6-4A85-A65A-94E7518A4E03 and current container ID is 3C2AB734-9EC6-4A85-A65A-94E7518A4E03
160523-23:16:58.3641495L|009224|00001784|SDAgent | |sdjecontainerif.cpp |003967|DETAIL | SDJEContainerIf::UnReportedResults() - Deleted lockjobcheck registry key

 

Example of exeption :

Tue May 16 23:16:58.000

ExceptionAddress: 530d0fca
   ExceptionCode: c0000008 (Invalid handle)
  ExceptionFlags: 00000000
NumberParameters: 0
Thread tried to close a handle that was invalid or illegal to close

PROCESS_NAME:  sd_jexec.exe

ERROR_CODE: (NTSTATUS) 0xc0000008 - An invalid HANDLE was specified.

EXCEPTION_CODE_STR:  c0000008

FAULTING_THREAD:  ffffffff

STACK_TEXT:  
003fea64 77de2bcc ntdll!NtClose+0xc
003fea68 769e97cb KERNELBASE!RegCloseKey+0x11b
003feaac 0016cb68 sd_jexec!Directory::operator=+0xd928
003fec34 0015df4b sd_jexec!FileSysIterator::operator=+0xa93b
003ff360 001a1dbe sd_jexec!StopOrderAbort::StopOrderAbort+0x25e9e
003ffad4 001ba224 sd_jexec!InPossession::operator=+0x5684
003ffb68 775400f9 kernel32!BaseThreadInitThunk+0x19
003ffb78 77dd7bbe ntdll!__RtlUserThreadStart+0x2f
003ffbd4 77dd7b8e ntdll!_RtlUserThreadStart+0x1b

Environment

Client Automation 14.5

Resolution

Open a case at CA Broadcom Technical Support and ask the fix T533369