cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Client Proxy error. SOAP:1.010 SRT: ASSERT failed: object reference not bound CX_AI_SYSTEM_FAULT

matias_z
Participant
0 Likes
1,374

Hi All,

I've a custom client proxy (consumer proxy) which SAP send information to CPI.

It's working fine in Dev system, but when I transported it to Quality system I'm getting the following error when testing it directly in the SE80:

SOAP:1.010 SRT: ASSERT failed: object reference not bound

Exception of class CX_AI_SYSTEM_FAULT

I created the Logical Port locally in Quality system as it's not transportable. I compares both SOAMANAGER from Dev a Q and they are exactly the same.

Do you know what could be the solution to this error?

I didn't find much information in previous posts, just a couple mentioning something about roles, but also I did not find anything on SU53 after running it in Se80.

Thanks in advane!

Accepted Solutions (0)

Answers (3)

Answers (3)

matias_z
Participant
0 Likes

So, after debugging and comparing Dev (working fine) and QA (system with the issue) systems.

I found the following difference, but I cannot identify from where that difference is coming from as Se80 and SOAMANAGER configuration are exactly the same. Any hints?

In program CL_SOAP_RUNTIME_CLIENT========CM001 line 80 when it checks if hibernation is enabled, in GBQ is not (value is '-') and in GBQ is enabled (value is 'X'). We don't know where that value is coming from. That's the first difference we found. Again, in both systems, the condifurarion of the consumer proxy is the same.
The second one, and if we change via debug the value on GBQ of the hibernation from 'X' to '-', we see in method PRE_PROCESS_PROTOCOLS from class CL_SOAP_RUNTIME_ROOT, the Reliable Messaging protocol (WSRM), in GBD is not enabled (again a '-'), but in GBQ is enabled ('X').

matias_z
Participant
0 Likes

Any other tip where to look?

harald_lesche-holzbecher
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Matias, well I'd then start debugging (e.g. set breakpoint in constructor of CX_AI_SYSTEM_FAULT) and check from where the exception is raised ...
Having a call stack might be helpfull then as well.

harald_lesche-holzbecher
Product and Topic Expert
Product and Topic Expert
0 Likes

There is a note which gives some hints what to check:

1951997 - XI runtime: Error handling for outbound proxy

matias_z
Participant
0 Likes

Thanks Harald, but I just want to understand why that error is happening. I know how to catch it via ABAP.

I checked the last section of the note with the typical problems but didn't help 😞