views:

108

answers:

0

I have a problem that is pretty much desctibed on this blog:

http://www.keithelder.net/blog/archive/2008/11/24/workaround-for-wcf-netmsmqbinding-bug-the-service-queue-does-not.aspx

the very problem is described on the blog as:

The wcf claims that service ‘~unittestqueue` does not exist? Well that queue DOES exist on the server but there isn’t a service mapped to that queue.

The kicker to this is that I’m not even using the unittestqueue at all within my code. This begs the question, why is a queue that I’m not even using showing up in my error list? The netMsmqBinding I had configured used another queue called logEntries. Here is the WCF configuration so you can see how this is configured.

The blog provides 2 fixes: 1) delete the que 2) put the app in a virtual folder but neither is acceptable in my scenario as aI have another 3rd party app that keeps creating queues on the server.

Supposedly there was a fix to be delivered by Microsoft to fix that not despite the server being fully patched now the error persists. Has anyone ran into that problem and solved it perhaps?