Server did not recognize the value of HTTP Header SOAPAction: .

[Former Member]

When I try to call a WS, the system gives me the following error:

"Server did not recognize the value of HTTP Header SOAPAction: ."

If I go to WSDL definition, I find:

<soap:operation soapAction=""/>

so... I've not soapAction defined in the WS.

The fact is that the same scenario works right before some upgrades we made last weekend. We are looking in the lpconfig, sm59, ... transactions, but we don't find anything!

Could anyone help us??

Thanks!

Miguel Angel.

[prateek]

In the receiver CC, have u filled any value for SoapAction?

Regards,

Prateek

[Former Member]

Sorry, How could I see that? Any transaction? I'm not an expert in WS configuration... sorry!

What I do to call the WS is the following:

- create a new proxy class from wsdl file

- create a new logical port (lpconfig)

- and write the following code:

data: uluproxy type ref to zhr_co_unlock_user_web_servic1.

try.

create object uluproxy.

catch cx_ai_system_fault.

clear uluproxy.

endtry.

try.

data: ex3 type ref to cx_ai_system_fault,

ex4 type ref to cx_ai_application_fault.

data: input_unlock type zhr_unlock_user_in_doc1,

output_unlock type zhr_unlock_user_out_doc1.

input_unlock-logon_id = 'mjulianc'.

call method uluproxy->unlock_user

exporting

input = input_unlock

importing

output = output_unlock.

catch cx_ai_system_fault into ex3. >>> Here is where the error is showed!

catch cx_ai_application_fault into ex4.

endtry.

[prateek]

I was talking about the Communication Channel in Integration Directory of XI.

Regards,

Prateek

[inigo_sacramento]

Wow.

I solved my problem with this thread.

I searched string 'soap action' in the WSDL and fill the field SOAP ACTION in SOAP receiver communication channel.

Regards,

[Former Member]

cool..

this solved my similar problem too..