Skip to Content
avatar image
Former Member

How do I call a .net web service from SAP?

Hello,

I have a web service developed in ASP.net 2.0 C# and published on a PC.

I can get its WSDL from the below address.

http://(IP)/wsYBMB_SCADA_SIP/Service1.asmx?WSDL

What I want to do is call this web service from SAP (version SAP ECC 6.0).

There are 2 SAP systems. One of them is for development and the other one is for production (the real system).

In development system, I created a client proxy called YBMBCO_SCADA_WS.

After that, I created a logical port, in Web Service Administration section of SAP SOA Management (web based), called YBMBCO_SCADA_WS_LP.

When I test to call this web service, it works fine.

Then, I created the same client proxy by moving my request to the production system.

After that, I created a logical port called YBMBCO_SCADA_WS_LP as I did for the development system.

However, when I test it, I got the below error from SAP. How can I solve this problem?

"SoapFaultCode:1 Server did not recognize the value of HTTP Header SOAPAction: http://www.(company).com//YBMB_SCADA_SIP.").

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jan 29, 2009 at 10:56 PM

    Hi,

    Are you sure that you had maintained the Logical port properly, please ensure that you have maintined the SOAP Action while creating the Logical Port. You can find that int he Operations tab.

    Thanks,

    Pakash

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 02, 2009 at 08:59 AM

    hi,

    google the error message you supplied, maybe add IIS because that's with high probability your webserver. You'll find numerous sites where similar problems are discussed and most often it is some IIS and .NET problems with caching or missing dlls or something.

    so, with a good chance your problem is one specific to your webservice environment and not one of your consuming SAP system. therefore it's probably solved faster in some MSDN forums.

    my 2 cents,

    anton

    Add comment
    10|10000 characters needed characters exceeded