I had the same error message and the solution was simple. There were a lot of messages sitting on various queues, and the storage limits had been reached. I went to: Server Manager -> Features Right clicked on Message Queuing Selected properties In the General tab un-ticked the storage limits I was informed that services … Read more
If you are using Visual Studio – Open Server Explorer under Servers/[Server Name] there is Message Queues folder that gives you view as well.
I ran into the same issue trying to write to the MSMQ through ASP.NET (Windows 7). I added “Receive Message” “Peek Message” and “Send Message” permissions and it works correctly now. If you’re running this through ASP.NET, then you’re probably under the IIS_IUSRS account.
With all due respect to @Juan’s answer, both are ways of exchanging data between two disconnected processes, i.e. interprocess communication channels (IPC). Message queues are asynchronous, while webservices are synchronous. They use different protocols and back-end services to do this so they are completely different in implementation, but similar in purpose. You would want to … Read more
I’d recommend staying away from hand-rolled solutions as there is a bunch of somewhat difficult stuff that needs to be gotten just right – like how transactions are handled, how exceptions cause rollbacks, how to stop rolling back endlessly (poison messages), how to integrate with long-running workflows so that the state management boundaries line up, … Read more