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

Posted: February 24, 2010 in BizTalk
Tags: , , , , ,

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”.

or

“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.

Tags: BizTalk | IIS | SOAP | HTTP | WCF | Adapter

Comments
  1. 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).

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s