cannot create proxy in sproxy

[Former Member]

Dear Forum!

We have a PI 7.0 installed and cofigured (actally a conultant did)

Now we have a problen with the buisiness system (basis 620 with SAP Exchange Infrastructure Add on).

I am supposed to create a proxy in TA SPROXY. The 4 connection tests are all fine, but when I click on "create proxy" the following message appears:

Message Interface MI_Dummy_Out | http://www.baw.de /tms/_Dummy references External Message ED_Dummy | http://www.baw.de/tms/_Dummy | SCWB_RFC_PINGOutpu t | urn:sap-com:document:sap:rfc:functions and the

Message no. SPRX000

I have no idea what kind of problem is arround, and if the problem is in the buisiness system or the PI system.

Does somebody have an idea?

Greetings

Andreas

[Former Member]

It looks like your message interface definition is not valid.

Are you using any external definition as the message. If so, reimport the ED and activate it. Check if the ED xsd is a valid one using some XMl editors.

Regards

Jaishankar

[Former Member]

thank for the answer. I have to ask "my" consultant.....

You here from me later

[Former Member]

Hello, in the meanwhile i had to open a sap call. The final answer is that i cannot crearte the proxy with the constallation PI7.0 - WAS 620

Thanks for your good tips

Andreas

[Former Member]

Hi Andreas,

I had the same issue.

It seems that WAS 6.20 has problems with external definitions.

Try to create data type, message type and message interface in our XI and generate the proxy specifing this interface.

The error will not occur anymore

Kind regards

Jochen

[Former Member]

Hi Andreas

Go to sm59 and check the RFC connections between the R/3 and XI systems.

useful link

Thanks

Gaurav Bhargava

Edited by: Gaurav Bhargava on Oct 6, 2008 2:18 PM

[Former Member]

Hello,

i checked all, they are fine aside from the "H" connection:

HEADER NAME HEADER VALUE

~response_line HTTP/1.0 500 Empty HTTP request received

~server_protocol HTTP/1.0

~status_code 500

~status_reason Empty HTTP request received

content-type text/xml

content-length 825

content-id </SOAP:Faul