SOAP Runtime: Exception message: Unallowed RFC-XML Tag (SOAP_EINVALDOC)

[Former Member]

Hi,

Curretly I am trying to test a Webservice on ECC 5.0, Oracle, Windows.

Below is the error that I am facing.

SOAP Runtime: SOAP Runtime exception: 111 occurred in method XP_READ_TAG of class CL_SOAP_XP at position 1

SOAP Runtime: Exception message: Unallowed RFC-XML Tag (SOAP_EINVALDOC)

In dev_rfc0:

ERROR 03:20:57: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE

STATUSCODE() Received return code 404 ( Not found )

ERROR 03:20:57: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE

PART~INITFOR_DESERIALIZE() A SOAP Runtime Core Exception

occurred in method XP_READ_TAG of class CL_SOAP_XP at position id

1 with internal error id 111 and error text Unallowed RFC-XML Tag

(SOAP_EINVALDOC) (fault location is 1 ).

I have looked up on sdn, and also looked at note 919886.

I have read several posts regarding creation of RFC Destination in sm59 of Type G, to get over this issue.

But RFC Destination of type G is not available in ECC 5.0

Is the error because of incorrect URL mentioned in logical port,

I am unable to ping the host name mentioned in URL, looks like that machine is not in the network.

does it mean the wsdl is not located at that particular host.

Any suggestions would be greatly appreciated.

Regards,

Vishnu.

[Former Member]

*... Received return code 404 ... * means that you called a server (which exists) and try to fetch a service on that server that does not exist (404 - file not found).

the einvaldoc-thing stems from the fact that the server (which you hit) returned you the 404 message in HTML format, which in turn the parser tried to parse like a soap message which of course doesn't work.

hope all is clear. it's basic HTTP knowhow.

regards, anton

[Former Member]

Hi Anton,

Thank you very much for your reply.

My scenario is, by using a client proxy in ECC 5.0 we are trying to consume a webservice which is

located on another server(non-sap). We are using URL in LPCONFIG.

The problem is the client proxy is not able to make the call to the other server.

This Client proxy was created some 4 years ago.

Looking at all your previous posts and the error, I was thinking that the call went through to the other

server and as you said that particular service was not available there.

(Am I correct in assuming this?)

However we tested the webservice using other means succesfully.

From what I understand, the Client Proxy is not invoking the Webservice.

I have looked up all the settings in SAP, everything looks fine.

I am unable to figure out what I am missing.

ICM is running and so are its services. I have the http port set as 8000.

Hope, I putting across my problem clearly.

Thanks,

Vishnu

[Former Member]

Hi Anton,

The complete error message in dev_rfc0:

INFO 02:15:12: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT

->IF_SOAP_TRANSPORT_BINDING~SEND() Try to send message ( DEST =

,PATH = ,URL = http://hostname:portno/ ,SOAP Action =

"ROI_R3_DF.roiSAPCreateOrder" )

INFO 02:15:12: SOAP Transport Binding CL_SOAP_HTTP_TPBND_ROOT

->IF_SOAP_TRANSPORT_BINDING~SEND() Message sent

INFO 02:15:12: SOAP Transport binding CL_SOAP_HTTP_TPBND_ROOT

->IF_SOAP_TRANSPORT_BINDING~RECEIVE() Try to receive message

ERROR 02:15:12: SOAP HTTP Binding CL_SOAP_HTTP_TPBND_ROOT->HANDLE

STATUSCODE() Received return code 404 ( Not found )

ERROR 02:15:12: SOAP Message CL_SOAP_MESSAGE->IF_SOAP_MESSAGE

PART~INITFOR_DESERIALIZE() A SOAP Runtime Core Exception

occurred in method XP_READ_TAG of class CL_SOAP_XP at position id

1 with internal error id 111 and error text Unallowed RFC-XML Tag

(SOAP_EINVALDOC) (fault location is 1 ).

After reading your post about the return code 404, I am in a dilemma whether, services in icman are unavailable or

the services at the location of the wsdl in the other server.

If you could clarify, it would be great.

Thanks a lot.

Vishnu.

[Former Member]

Hi,

per HTTP definitions 404 errors can only be thrown by the target server. usually you can rely on that. only some microsoft proxies seem to allow their admins to throw any HTTP errors they stumble upon. some do.

but usually you should assume that you received the error from your target server. you should even see the request in your target servers dev.rfc logs. if you really tested the same service sucessfully from elesewhere you should look for typos in your customizings.

anton

[Former Member]

Thank you very much for your time.

Regards,

Vishnu

[Former Member]

Hi,

Any Suggestions.

Regards,

Vishnu