Highlighted
Absent Member.. Absent Member..
Absent Member..
1588 views

A signal 11 was raised in native code. Client terminated. Error: Win32 Exception:

Hello,

Whenever a ticket is been created from HPOO and pushed into HPSM via SOAP, I am getting this error. A signal 11 was raised in native code. Client terminated. Error: Win32 Exception: 0xC0000005 

<?xml version="1.0" encoding="UTF-8"?><Envelope><Body><Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>A signal 11 was raised in native code. Client terminated. Error: Win32 Exception: 0xC0000005 (instruction 0x1016B4E4 while reading address 0x00000000)</faultstring><faultactor>Server</faultactor></Fault></Body></Envelope>

I am unable to find anything in the log file related to the above error information. Can anyone help me resolve this. It is quiet urgent.

0 Likes
3 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: A signal 11 was raised in native code. Client terminated. Error: Win32 Exception:

I have this information from the log file

 8700(  8820) 02/21/2017 14:37:10  RTE D Login succeeded
  8700(  8820) 02/21/2017 14:37:10  RTE D Setting uname to HPOO.INTEGRATION, login name is HPOO.INTEGRATION
  8700(  8820) 02/21/2017 14:37:10  RTE I [Address ] Symbol(Parm1,Parm2,Parm3,Parm4) +Offset                                          Source module
  8700(  8820) 02/21/2017 14:37:10  RTE I  1: [1016B4E4] CSimpleXmlDom::getAttributeAsBool(0x0,0x1026E36C,0xBF6350C,0xC77A400) +0x24      D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-xmlpars.cpp-1173
  8700(  8820) 02/21/2017 14:37:10  RTE I  2: [1013BC97] CTopaz::doCardinalOperation(0xC775258,0x1026D974,0x101435FD,0xBF634E0) +0x157    D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-tpzmethods.cpp-3646
  8700(  8820) 02/21/2017 14:37:10  RTE I  3: [1013C9BC] CTopaz::Create(0xBF634E0,0xC9C6180,0xBE2B170,0xFFFFFFFE) +0xC                    D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-tpzmethods.cpp-4028
  8700(  8820) 02/21/2017 14:37:10  RTE I  4: [101435FD] CTopaz::process(0xAA00690,0xC9C6180,0xBF6350C,0x995F888) +0x4BD                  D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-tpzmethods.cpp-16707566
  8700(  8820) 02/21/2017 14:37:10  RTE I  5: [1012DC3F] TopazThread::handleRequest(0x995F888,0xAA00700,0xBF6350C,0x995F8A8) +0x26F       D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-topazthread.cpp-326
  8700(  8820) 02/21/2017 14:37:10  RTE I  6: [100E98ED] SCXMLInterface::SM_ThreadHandleRequest(0x71E4540,0x995F934,0x0,0x995F920) +0x44D D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-scxmlinterface.cpp-308
  8700(  8820) 02/21/2017 14:37:10  RTE I  7: [1012D795] Java_com_hp_ov_sm_server_utility_TopazThread_handleRequest(0x71E4540,0x995F934,0x995F930,0x33FC0C3) +0x25 D:\Program Files\HP\Service Manager 9.30\Server\RUN\SM.dll-topazthread.cpp-106
  8700(  8820) 02/21/2017 14:37:10  RTE I  8: [033FC0C3] <not found>(0x0,0x71E4400,0x0,0x1F80)
  8700(  8820) 02/21/2017 14:37:10  RTE I  9: [63AF8672] JVM_GetThreadStateNames(0x995FA30,0x995FBFC,0xA,0xA4055E8) +0x4C652              D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 10: [63AF8BA5] JVM_GetThreadStateNames(0x995FBF4,0x995FAF8,0x995FB6C,0x1E4400) +0x4CB85         D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 11: [63BBE12E] JVM_FindSignal(0x63AF89D0,0x995FBF4,0x995FAF8,0x995FB6C) +0x6355E                D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 12: [63AF8C3E] JVM_GetThreadStateNames(0x995FBF4,0xA4055E8,0x71E4400,0x995FB6C) +0x4CC1E        D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 13: [63AF8DC6] JVM_GetThreadStateNames(0x995FBF4,0x54A29C0,0x328EE68,0x32904D0) +0x4CDA6        D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 14: [63AF8E37] JVM_GetThreadStateNames(0x995FBF4,0x7397838,0x54A29C0,0x328EE68) +0x4CE17        D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 15: [63A9D84F] jio_printf(0x7397838,0x71E4400,0x71E4400,0x0) +0x9F                              D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 16: [63B1C07C] JVM_GetThreadStateNames(0x71E4400,0x0,0x0,0x1) +0x7005C                          D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 17: [63B1C16A] JVM_GetThreadStateNames(0xBC26BF0,0xFFFDE000,0x777B0214,0x995FC2C) +0x7014A      D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 18: [63B606F6] JVM_FindSignal(0x71E4400,0xF2515314,0x0,0x0) +0x5B26                             D:\Program Files\HP\Service Manager 9.30\Server\RUN\jre\bin\client\jvm.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 19: [6393C6DE] endthreadex(0x0,0x995FF94,0x7511336A,0xAA1A190) +0x3A                            D:\Program Files\HP\Service Manager 9.30\Server\RUN\MSVCR100.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 20: [6393C788] endthreadex(0xAA1A190,0x995FFD4,0x776E9902,0xAA1A190) +0xE4                      D:\Program Files\HP\Service Manager 9.30\Server\RUN\MSVCR100.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 21: [7511336A] BaseThreadInitThunk(0xAA1A190,0x7CCFFD4F,0x0,0x0) +0x12                          C:\Windows\syswow64\kernel32.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 22: [776E9902] RtlInitializeExceptionChain(0x6393C724,0xAA1A190,0xFFFFFFFF,0x777775CC) +0x63    C:\Windows\SysWOW64\ntdll.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I 23: [776E98D5] RtlInitializeExceptionChain(0x6393C724,0xAA1A190,0x0,0x2000) +0x36               C:\Windows\SysWOW64\ntdll.dll-
  8700(  8820) 02/21/2017 14:37:10  RTE I !!! Core Generation is disabled.  Ignoring Generate Core Dump Request.
  8700(  8820) 02/21/2017 14:37:10  RTE W Exception occurred for method Create and XML request <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:com="http://servicecenter.peregrine.com/PWS/Common" xmlns:pws="http://servicecenter.peregrine.com/PWS" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body/>
</soapenv:Envelope>
  8700(  8820) 02/21/2017 14:37:10  RTE E Caught SCFramework::SCEHException: Win32 Exception: 0xC0000005 (instruction 0x1016B4E4 while reading address 0x00000000)
  8700(  4764) 02/21/2017 14:37:10 JRTE W Send error response: A signal 11 was raised in native code. Client terminated. Error: Win32 Exception: 0xC0000005 (instruction 0x1016B4E4 while reading address 0x00000000)
  8700(  8820) 02/21/2017 14:37:10 JRTE I Termination signal: 11
  8700(  8820) 02/21/2017 14:37:10  RTE I -Memory : S(3368016) O(1162940) MAX(5023020) - MALLOC's Total(559587)
  8700(  8820) 02/21/2017 14:37:10  RTE I ===> Signal 11: User=HPOO.INTEG, Application=Unknown, Panel=Unknown
  8700(  8820) 02/21/2017 14:37:10  RTE I  RAD thread id 0, last option key 0

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: A signal 11 was raised in native code. Client terminated. Error: Win32 Exception: 0xC0000005

Hello Prath

hope you are doing well.

When you have a signal 11 issue, the best suggestion to follow is raised a ticket with CPE team directly because for ure there is a bug on the system that they may fix. Please proceed to open a ticket with them.

Carlos Villalobos R
Customer Support Engineer
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: A signal 11 was raised in native code. Client terminated. Error: Win32 Exception:

Can you run it with an RTM:3 trace enabled on the port? The signal 11 is basically an unhandled error (there might be a pop-up programmed that obviously doesn't work as this is a bg process, etc.)

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.