Soap version mis match:

Question

4.00/5 (1 vote)

See more:

Hello,

I have added a web service as my service reference in .Net project. I am able to access the class and I am getting the function exposed in Web service.

The issue is when I try to call the function it says there is a version miss match. Please get a solution to fix the issue

C#

{"Possible SOAP version mismatch: Envelope namespace http://schemas.xmlsoap.org/wsdl/ was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/."}

Posted 2-Nov-13 2:12am

Ameen Sherif

Updated 2-Nov-13 2:32am

Sampath Lokuge

v3

Add a Solution

Comments

Sampath Lokuge 2-Nov-13 8:25am

Can we have whole error message ?

Ameen Sherif 2-Nov-13 8:29am

The Error Message

{"Possible SOAP version mismatch: Envelope namespace http://schemas.xmlsoap.org/wsdl/ was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/."}

Sampath Lokuge 2-Nov-13 8:31am

Plz check my answer.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sampath Lokuge · Answer 1 · 2013-11-02T02:28:00

The problem is that you are setting the URL property of the webservice to the WSDL url. You need to set the URL of the webservice instance to the location of the webservice itself, which is something that is contained within the WSDL. To find this URL, open the WSDL document in a text editor and look for the "location" attribute of the <soap:address xmlns:soap="#unknown"> element. You can and should still use the WSDL url for graphical tools within visual studio, but it's important to make the distinction at run-time.

For more info : Possible SOAP version mismatch

Another useful link : Possible SOAP version mismatch

I hope this will help to you.