Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a client that has a server (server A) that has a .net app that is trying to write to a MSMQ on another server (server B). They are getting the error "MSMQ independent clients cannot serve MSMQ dependent clients".

What is the difference between the two, and is there an easy way to make server A independent?


share|improve this question
up vote 3 down vote accepted

Dependent clients are (were) clients that didn't have a local MSMQ queue manager but instead used RPC to access a queue manager on another machine. Bit like a terminal services client where you see what's going on but the work is done elsewhere.

If you go to the MSMQ properties in Computer Management on the server, there is a "Server Security" tab; make sure the "Disable Dependent Clients ....." option is unchecked.

What exact line of code generates the error message?


share|improve this answer
Using .Net, it was either the constructor of the MessageQueue class or the the send method. We ended up discovering that when the client recently installed MSMQ on the machine, they did not have a particular checkbox (Local Storage) checked. Reinstalling MSMQ with that set fixed it right up. – Dan Appleyard Jun 15 '11 at 17:26
Yes, Local Storage checkbox controls dependent client creation. I think it was part of the product group's effort to remove awarenmess of dependent client from the product. – John Breakwell Jun 15 '11 at 18:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.