|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
MSMQ PermissionsHello,
I have an application that runs as a Windows Service. When the application runs for the very first time, it creates a new MSMQ Queue. Because the Queue was created under the SYSTEM account, now I cannot modify, delete, or even view the contents of the queue from the MSMQ Admin. What are my options to allow me to gain access to this queue? Thanks Check out the following link, it has basically the same problem as you are
experiencing. The problem bascially is related to which account created the queue in the windows service and the permissions and acess rights you granted to the queue when it was created. http://www.dotnet247.com/247reference/msgs/53/268167.aspx HTH Ollie Riches <yof***@comcast.net> wrote in message Show quote news:1128442305.327471.81670@g14g2000cwa.googlegroups.com... > Hello, > I have an application that runs as a Windows Service. When the > application runs for the very first time, it creates a new MSMQ Queue. > Because the Queue was created under the SYSTEM account, now I cannot > modify, delete, or even view the contents of the queue from the MSMQ > Admin. What are my options to allow me to gain access to this queue? > > Thanks > I understand what the problem is. The link you provided mentions how to
prevent it. My question is now that I am in this situation, how do I correct it? Is my only option to create a new Windows Service to go in an modify the queue's permissions? you should impersonate an admin account or better yet, a speciall account
that has admin priviledges. Don't impersonate at the application level, just impersonate on the calling thread or programatically because it is safer. That should get your queue account created with the correct permissions set. -- Show quoteRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The Microsoft Office Web Components Black Book with .NET Now Available @ www.lulu.com/owc Forth-coming VSTO.NET - Wrox/Wiley 2006 ------------------------------------------------------- <yof***@comcast.net> wrote in message news:1128446414.779136.306330@g44g2000cwa.googlegroups.com... > I understand what the problem is. The link you provided mentions how to > prevent it. My question is now that I am in this situation, how do I > correct it? Is my only option to create a new Windows Service to go in > an modify the queue's permissions? > |
|||||||||||||||||||||||