Anatoliy, I am not sure but I think this will be related to the wsdl file, WCF don't publish all of the metadata in a single wsdl file. This link could provide you with more info http://stackoverflow.com/questions/10370710/complex-type-is-not-available-in-wcf-wsdl.

Another solution would be to upgrade to NET 4.5 http://blogs.microsoft.co.il/blogs/idof/archive/2011/09/17/what-s-new-in-wcf-4-5-a-single-wsdl-file.aspx

I am sorting out something similar with a WCF Web Service that cannot be consumed by a mainframe but it can be easily consumed by everyone else.

Cheers,

Luis

>Hi All,
>
>I'm working on task of creating WCF service to be called from Peoplesoft Integration Broker. The WCF service has single method that takes XML string and returns also a string. I have developed the service, installed it on IIS and tested it from .NET and VFP clients with no trouble at all. Worked like a clock.
>
>Peoplesoft calls to this WCF service fail with error message "Expected to find node type 'Element' with name [method name] and namespace 'http://tempuri.org/'...
>
>Soap envelopes created by Peoplesoft are different from ones created by NET client.
>
>Peoplesoft envelope is shorter: /Envelope/Body/ input parameter -- XML string, not escaped
>
>.NET envelope has additional wrapping: /Envelope/Body / [method name] / [parameter name] / input parameter -- XML string, properly escaped
>
>Peoplesoft developer on the other side claims that there is no way of passing parameters to 3rd party web services, which is something hard to believe.
>
>Has anybody run into this issue before? Strangely enough there is not much information around (or at least I cannot google it up) about integrating Peoplesoft and WCF.
>
>Thanks a lot! I'm flogging this horse 3rd day already.