Feed Icon  


  • Bryant Likes
  • Send mail to the author(s) E-mail
  • twitter
  • View Bryant Likes's profile on LinkedIn
  • del.icio.us
Get Microsoft Silverlight
by clicking "Install Microsoft Silverlight" you accept the
Silverlight license agreement

Hosting By

Hot Topics


Open Source Projects



WCF: Unable to open IChannelListener

Posted in BizTalk | WCF at Wednesday, August 2, 2006 9:51 AM Pacific Daylight Time

On one of my current projects we are trying to use WCF with BizTalk 2006. In order to do this I was trying to implement the WCF adapter for BizTalk Server 2006 community project. The project comes with a nice sample application that demonstrates how everything works. However, when I tried to start the receive port I would get an error message saying:

The Messaging Engine failed to add a receive location "News Receiver" with URL "wcf://http://localhost:13000/eventsource" to the adapter "WCF". Reason: "The ChannelDispatcher at 'http://localhost:13000/eventsource' with contract(s) '"IndigoOneWayReceiver"' is unable to open its IChannelListener."

I tried to get this working a few different ways but nothing seemed to matter. The weird thing was that I could write a simple WCF console app that would listen on http://localhost:13000/eventsource and it would work. But whenever I would start the receive location I would get that error. I posted my question in the WCF Forums and also on the codeplex project but was unable to resolve it.

Then I ran into this same issue again with another sample app that I downloaded, but this time it was because IIS was running on the same port (and I was using Windows XP). However, in the process of figuring that out I came across this post by Martin Parry. While the post didn't resolve my issue (it is for Vista only), it did point me in the right direction. After some more googling I came across this post by dominick baier which explains the issue in Windows Server 2003 terms (and he even provides a tool to help you with the HttpCfg syntax).

So if you're working with WCF and you want to listen on a port and you're not running as an administrator, then you will need to configure the server with the HttpCfg tool. The error message about the IChannelListener isn't very helpful, but maybe that will change before we get to RTM. In the meantime, HttpCfg is your friend.

Thursday, November 2, 2006 12:54:52 AM (Pacific Standard Time, UTC-08:00)
Your blog entry was the only useful thing I could find for this error.

I am trying to open a servicehost on an XPSP2 machine but get the same error. Since I'm logged in as an user who is part of the Adminstrators group, I really shouldn't have to use httpcfg. Any ideas?

Tuesday, November 7, 2006 11:31:41 PM (Pacific Standard Time, UTC-08:00)
I had the same problem when opening a ServiceHost. I just figured out that I should shut down IIS, in order to release port 80 for my app to listen on :-)
Wednesday, May 16, 2007 7:55:23 AM (Pacific Daylight Time, UTC-07:00)
Newbie here. I am having the same error, but the service is running as an admin, and on a different port. If it matters, I'm trying to run multiple instances of the same service name on different schemes/ports, so that remote users can use HTTP/SOAP, LAN users can use TCP, and localhost users can use named pipes. Apparently, this isn't doable. I suspect a service name conflict? Since the service name is the fully qualified classname w/ namespace, do I create a whole new service class for each scheme?
Comments are closed.