Soap Format Exception

WSE910: An error happened during the processing of a response message, and you can find the error in the inner exception.

You can also find the response message in the Response property.

Hi All

I am getting this exception when calling a api / Webservice even i am sending a soap security header in request also.

Inner Exeption is

Microsoft.Web.Services3.SoapFormatException: WSE005: The input was not a valid SOAP message because

it has either the wrong name or the wrong namespace. The name specified was: definitions.

The namespace it was defined under was: http://schemas.xmlsoap.org/wsdl/..

please provide solution

Thanks In advance

Is the target Namespace correct? It should look like:

xmlns:xsd1="http://example.com/stockquote.xsd" xmlns:soapbind="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"

"The definitions element sets the name of the WSDL document and typically declares the namespaces used in the document. In the above sample, the StockQuote is a name for the WSDL definition as a whole. This name need not correspond to the name of any particular service in the WSDL definition.

Notice that you must specify a target namespace for your WSDL definition which identifies the namespace of elements defined in the WSDL document, just like you would for an XML Schema definition. Anything that you name in the WSDL definition (like a message, portType, binding, etc.) automatically becomes part of the WSDL definition's target namespace defined by the targetNamespace attribute. In the above sample, the targetNamespace attribute states that the elements within the WSDL definitions declare names in the namespace "http://example.com/stockquote.wsdl".

The message, portType, and binding elements must be named (by their name attributes) making it possible to refer to them from elsewhere in the WSDL definition. These "named" labels automatically take on the namespace specified by the targetNamespace attribute. You must use the fully qualify name (QName) to refer to them in you WSDL document.

Here are some of restrictions in WS-I Basic Profile 1.0. "

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Arunava Bhattacharjee12y ago
Is the target Namespace correct? It should look like:

xmlns:xsd1="http://example.com/stockquote.xsd" xmlns:soapbind="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/"

"The definitions element sets the name of the WSDL document and typically declares the namespaces used in the document. In the above sample, the StockQuote is a name for the WSDL definition as a whole. This name need not correspond to the name of any particular service in the WSDL definition.
Notice that you must specify a target namespace for your WSDL definition which identifies the namespace of elements defined in the WSDL document, just like you would for an XML Schema definition. Anything that you name in the WSDL definition (like a message, portType, binding, etc.) automatically becomes part of the WSDL definition's target namespace defined by the targetNamespace attribute. In the above sample, the targetNamespace attribute states that the elements within the WSDL definitions declare names in the namespace "http://example.com/stockquote.wsdl".
The message, portType, and binding elements must be named (by their name attributes) making it possible to refer to them from elsewhere in the WSDL definition. These "named" labels automatically take on the namespace specified by the targetNamespace attribute. You must use the fully qualify name (QName) to refer to them in you WSDL document.
Here are some of restrictions in WS-I Basic Profile 1.0. "