The Messaging Engine failed to register an adapter: SOAP, WCF-BasicHttp, HTTP, …

Problem

The following error may occur when BizTalk Server attempts to register the SOAP, HTTP, or WCF adapter.

“The Messaging Engine failed to register an adapter “SOAP”. Details:
“Registering multiple adapter types within the same process is not a supported scenario. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process”.

“The Messaging Engine failed to register an adapter “HTTP”. Details:
“Registering multiple adapter types within the same process is not a supported scenario. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process”.

“The Messaging Engine failed to register an adapter “WCF-BasicHttp”. Details:
“Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process”.

Potential Causes

Already have a different adapter type loaded into IIS, Adapter binding types do not match Receive location for address“/MyService.WCF/MyService.svc” not found. (The BizTalk receive location may be disabled.)
Receive location disabled, Typo in Receive Location name

When running BizTalk Server on Windows Server 2003 / IIS 6.x, the SOAP and HTTP adapters cannot execute in the same process space or application pool.

Solution

If an installation requires using the SOAP, HTTP or WCF adapters on the same Web server then separate application pools must be created for each adapter. Once created, the virtual directories for each adapter are each assigned to a different application pool.

We have to separate the receive locations from different adapters in different IIS application pools.

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community. View all posts by Sandro Pereira

7 thoughts on “The Messaging Engine failed to register an adapter: SOAP, WCF-BasicHttp, HTTP, …”

Hi Sandro, I got a very detailed post on this topic here
http://blogs.digitaldeposit.net/saravana/post/2008/08/26/Multiple-Isolated-Host-(Host-Instances)-Multiple-Virtual-directories-different-adapters-what-are-the-rules.aspx

Sandro Pereira says:

December 12, 2011 at 9:14 am

Great post, thanks for sharing Saravana.

Reply
1. Wael Mohamed says:
  
  November 20, 2016 at 11:47 am
  
  i changed to true in order to consume the service without configure the receive location , but still it is not working , i need to call it without configure the receive port for testing
  
  Reply

Just to be clear, this can also occur if the service description in IIS does not match the receive location in BizTalk. For example, if IIS thinks it is WCF-WSHttp and the BizTalk receive location is set to WCF-BasicHttp. (I think that’s what the 1st potential cause bullet point is saying, but I keep running into this and overlooking it).

Thank you Sandro Pereira. You saved us for a lot of work.

thanks a lot Sandro! very useful post!
Your blog has helped me in multiple occasions.
regards

Thanks Sandro for pointing in the right direction. Error also appears to happens with different WCF adapters on the same app pool eg, WCF-WSHttp and WCF-BasicHttp.