ESBT 2.1 Bad Receive Port

I had an ESBT 2.1 solution which publishes a mesasge to the ESBT itinerary response on ramp.  The first problem I encountered was the receive port that comes pre-canned with ESBT wasn’t creating the instance subscription so the two way receive port was immediately shutting down after the request was published to the message box, when the itinerary reached the point where it would return a result to the receive port I got a routing error because the message had no receive port service instance to correlate to.  I tried creating a new receive location with no success and then created a new receive port and receive location which immediately saw my instance subscriptions being created and everything working correctly.  It appears that somehow the port created by the Microsoft.Practices.ESB.CORE64.msi file was somehow corrupt even though to all outward appearances it looked to be perfect.  Something to watch out for.

Advertisements
This entry was posted in BizTalk Server. Bookmark the permalink.

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