locked
Possible SOAP version mismatch? RRS feed

  • Question

  •  

    I'm trying to upgrade MS CRM code from .NET 1.1 to 2.0. Getting there slowly, thanks to the folks here.

     

    Now, I am trying to execute my first webservice call however I get this error and no idea where to go:

     

    "System.Web.Services.Protocols.SoapException: Possible SOAP version mismatch: Envelope namespace http://schemas.xmlsoap.org/wsdl/ was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/.\r\n   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)\r\n   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)\r\n   at BusinessLogicManager.CrmSdk.CrmService.Execute(Request Request)\r\n   at BusinessLogicManager.FetchData.GetCurrentUserID()"

     

     

    My development box is WS2003 R2 SP2 + all updates and has .NET Framework 2.0 as well as 1.1

    My testing box where I MS CRM is installed (4.0) is WS2003 SBS Premium R2 + all updates and .NET 2.0 and 3.0 (MS CRM 4.0 installs this)

     

    any ideas whats going on here and how to fix it?

     

    I'm guessing has to do with the .NET Framework however.... does MS CRM 4.0 not use .NET 2.0? or do we have to develop a solution in .NET 3.0, which means I would have to get VS 2008 since VS2005 doesnt support .NET 3.0 out of the box....

     

    I am running the application in VS.NET 2005 from my dev box and hooking it up to/directing it to the testing box that has MS CRM 4.0 installed.

     

    Thanks

    Tuesday, February 12, 2008 12:14 AM

Answers

  •  

    Nevermind, it was because I was actually putting in the new URL for the webservice as opposed to just changing the year of the webservice directory to 2007 from 2006....

     

    just ignored the warning in VS.NET when entering the URL location as there is a message returned back from the service that the URL has been moved - just ignore it....it will auto redirect I guess

    Tuesday, February 12, 2008 1:36 AM

All replies

  •  

    Nevermind, it was because I was actually putting in the new URL for the webservice as opposed to just changing the year of the webservice directory to 2007 from 2006....

     

    just ignored the warning in VS.NET when entering the URL location as there is a message returned back from the service that the URL has been moved - just ignore it....it will auto redirect I guess

    Tuesday, February 12, 2008 1:36 AM
  • Another reason when this happens is when you're pointing at the CrmService.aspx instead of the CrmService.asmx

    Ronald


    Ronald Lemmen
    Microsoft Dynamics CRM MVP
    http://www.ronaldlemmen.com
    Friday, September 24, 2010 6:13 AM
    Moderator