Posted by: Charles Maitland | Wednesday 18 November, 2009

Backwards compatibility in the MSCRM web services

Had an interesting issue today trying to hook up a content management system to MSCRM using the CMS provided connector.

The connector was configured to call

http://<Server Name> mscrmservices/2007/crmservice.asmx?WSDL&uniquename=<client name>

but it was throwing the following error:

Possible SOAP version mismatch: Envelope namespace was unexpected. Expecting

When I tried the URL in a browser to check we spotted that this was being re-directed to

http://<Server Name> mscrmservices/2007/crmserviceWSDL.asmx?uniquename=<client name>

and the WSDL I got back did indeed reference

It was only after a bit of digging that I spotted that there was a mscrmservices/2006 directory and when we pointed the integration at http://<Server Name> mscrmservices/2006/crmservice.asmx?WSDL&uniquename=<client name>


all was fine.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: