Inbound proxy WAS 6.20 - INTERFACE REGISTRATION ERROR -

[Former Member]

Hi guys;

i face annoying problem.

Scenario:

synchronous SOAP => XI => Proxy (CRM WebAS 6.20 with XI Plugin)

I generated the proxy in sproxy and added the code to the generated class method EXECUTE_SYNCHRONOUS.

all objects are saved and activated.

when I send a message via SOAP I get 2 synchron errors in sxmb_moni back from the CRM system.

first error

No implementing class registered for the interface (ABAP interface, request message RepShop_Request_in, request message, namespace urn:endress:com:idm:user)

second error

Message ID FDC223201D0A11DDB63902000000002D for pipeline CENTRAL, version already exists in system

whats the problem?

I already checked sproxy and all objects are activated

I made a simple test with a dummy test message to check if the proxy works in async mode and get more detail information

test scenario asynchronous SOAP => XI => Proxy (CRM).

the test file is processed successfully in XI and sended to CRM.

unfortunately I can´t see any message in CRM neither in sxmb_moni nor in smq2

any ideas, how to get this fixed?

maybe the crm system is not properly configured?!

what to check?

Hope anybody could give me an advice

Kind regards

Jochen

[prateek · Accepted solution]

First error clearly states that the Proxy is not properly generated for the sync interface at CRM side. Recheck the config and if reqd, regenerate the proxy.

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek;

thanks for your reply.

I already made "check proxy" in sproxy.

I seems everything is fine, now errors are displayed.

what should I further check?

Thanks

Regards

Jochen

[sumesh_k2]

Hi,

Goto Sproxy -> Proxy ->Activate All. This should solve your first error.

For second problem, check whether connection details for CRM receiver proxy are maintained properly in the channel.

[Former Member]

Hi guys;

I got ahead a litte bit with my scenario.

The first error changed.

The error "No implementing class found" was caused by the corrupt RFC Destination.

The target of the destination was wrong, because it was copied from a existing connection.

By the way it was not my fault g

But there is still a problem with the RFC connection.

A connection test causes a "HTTP 400 Error" instead of a "HTTP 500 Error" as expected and known by the other system connected via ABAP Proxy.

In the Response-Tab there is no SOAP Response shown.

Looking at the sxmb_moni a reponse error "Error Parsing Response. No XI Response Received." occured

any ideas what´s wrong with the rfc destination?

Could there be other sources of error.

any help appreciated.

Kind regards

Jochen

detailed error messages from sxmb_moni ...

 
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Call Adapter 
  --> 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category> 
  <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code> 
  <SAP:P1>200</SAP:P1> 
  <SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2> 
  <SAP:P3></SAP:P3> 
  <SAP:P4></SAP:P4> 
  <SAP:AdditionalText>--SAP_4829E6A58E6B5B57E10000000A35E046_END content-type:text/xml content-length:4264 content-id:<soap-4829E6A48E6B5B57E10000000A35E046sap.com> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>91C99510-20F0-11DD-CF78-02000000002D</SAP:MessageId><SAP:TimeSent>2008-05-13T13:29:10Z</SAP:TimeSent><SAP:Sender><SAP:Service>IDM_BS</SAP:Service></SAP:Sender><SAP:Receiver><SAP:Party agency="" scheme=""></SAP:Party><SAP:Service>SAP_DCM_MDT110_BS</SAP:Service></SAP:Receiver><SAP:Interface namespace="urn:endress:com:idm:user">RepShop_Request_in</SAP:Interface></SAP:Main> <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging> <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-13T13:29:10Z" wasRead="false"><SAP:Engine type="AE">af.dxi.osdxi0</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>91C99510-20F0-11DD-CF78-02000000002D</SAP:MessageId><SAP:Info></SAP:Info></SAP:Hop><SAP:Hop timeStamp="2008-05-13T13:29:11Z" wasRead="false"><SAP:Engine type="IS">is.70.linvm90</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>91C99510-20F0-11DD-CF78-02000000002D</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList> <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic> <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1"><SAP:From><SAP:Name></SAP:Name><SAP:Interface namespace=""></SAP:Interface></SAP:From><SAP:MessageId>00000000-0000-0000-0000-000000000000</SAP:MessageId><SAP:QualityOfService></SAP:QualityOfService><SAP:TimeSent></SAP:TimeSent><SAP:Direction>Request</SAP:Direction><SAP:Document></SAP:Document></SAP:MessageHeader> <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:Context></SAP:Context><SAP:Code p1="" p2="" p3="" p4="">CALLER.MSG_GUID_NOT_QUALIFIED</SAP:Code><SAP:Text language="EN">Attribute message GUID not specified</SAP:Text></SAP:ErrorHeader> <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0"><SAP:Hop SystemName="SAP_DCM_MDT110_BS" Type="RECEIVER" TimeStamp="2008-05-13T13:29:15Z" WasRead="0"><SAP:MessageInbound><SAP:Type>AENGINE</SAP:Type></SAP:MessageInbound><SAP:MessageOutbound><SAP:Type></SAP:Type></SAP:MessageOutbound></SAP:Hop></SAP:HopList> <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound></SAP:InternalAttributesHeader> </SOAP:Header> <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-91caa68020f011dd855d02000000002dsap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest> <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0"> <SAP:Payload xlink:href="cid:payload-4829E6A38E6B5B57E10000000A35E046sap.com"> <SAP:Document>TraceDocument</SAP:Document> </SAP:Payload> </SAP:Manifest> </SOAP:Body> </SOAP:Envelope> --SAP_4829E6A58E6B5B57E10000000A35E046_END content-type:text/xml;charset=utf-8 content-length:185 content-id:payload-91caa68020f011dd855d02000000002dsap.com <?xml version="1.0" encoding="UTF-8"?> <ns1:RepShopUser_request_MT xmlns:ns1="urn:endress:com:idm:user"><I_PARTN>0000118075</I_PARTN><I_WAM>E0754328</I_WAM></ns1:RepShopUser_request_MT> --SAP_4829E6A58E6B5B57E10000000A35E046_END content-type:text/plain content-length:1720 content-id:payload-4829E6A38E6B5B57E10000000A35E046sap.com <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat"><Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">XMB entry processing </Trace> <Trace level="1" type="T">system-ID = DCM</Trace> <Trace level="1" type="T">client = 110</Trace> <Trace level="1" type="T">language = E</Trace> <Trace level="1" type="T">user = DXIREMOTE</Trace> <Trace level="1" type="Timestamp">2008-05-13T13:29:15Z </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">* * </Trace> <Trace level="1" type="T">**************************************************** </Trace> <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="T">Message-GUID = 00000000000000000000000000000000</Trace> <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace> <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace> <Trace level="1" type="System_Error">System-Error: CALLER.MSG_GUID_NOT_QUALIFIED</Trace> <Trace level="1" type="System_Error">Attribute message GUID not specified </Trace> <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace> <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace> </SAP:TraceHeader> --SAP_4829E6A58E6B5B57E10000000A35E046_END--</SAP:AdditionalText> 
  <SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage> 
  <SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack> 
  <SAP:Retry>N</SAP:Retry> 
  </SAP:Error> 

[Former Member]

Hi guys;

HTTP status 400 is known as "Bad request".

so probably the configurations of the CRM System (WebAs 6.20) is corrupted.

what´s about the path prefix for the Integration engine?

Is that different from Systems >= WebAS 6.40

=> /sap/xi/engine?type=receiver

structure in SICF looks the same in both systems

what else could be the reason for this error?

Hopefully somebody could help me..

Kind regards

Jochen

[Former Member]

Hello ,

first ,Regenerate the proxy and check the ABAP code in it...

then for second

search this blog,to solve your problem

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

Is it first time .. , i mean have ever before seen any messages in SXMB_MONI, if yes , no need to change any parameters unless if you are dealing with sync communicaiton.

if you have successfullmessages in moni previously , what date it was ..chak and give that date..

after that ,

try to check the cache.. if cache is showing green ok other wise you can refresh the cache. by sxi_cache.. and refresh and see..

also if sender side message is processed by CC or not in RWB check ..( here also check for previos successful messages date if available give that date onwards)

One more is have u change any date recently.. if system is not running ??

**************reward points,if found useful

Edited by: BVS on May 13, 2008 10:14 AM

[Former Member]

hi,

Server proxy

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

Regards