the problem was that the queue was created by a service that i wrote.  since that service was not running under my account, i was not the creator of the queue.  even as administrator, i didn't have authority to read or delete the queue.  so to solve the problem, i made the service delete the queue and then recreated it by using the computer management console.  now it's all working fine.

Hi,

I've noticed the same problem when creating a queue programatically in
both XP and 2k, but only on some machines. I'm not sure... I think it
has something to do with security policy or something.

Anyway, I sort of solved the problem by setting the security
permissions on the queue manually while creating the queue. Not a very
elegant solution, but it served my purpose at the time:

using System.Messaging;

AccessControlList acl = new AccessControlList();

Trustee trustee = new Trustee("SYSTEM", Environment.MachineName,
System.Messaging.TrusteeType.Group);

Trustee owner = new Trustee(System.Security.Principal.WindowsIdentity.GetCurrent().Name,
Environment.MachineName, System.Messaging.TrusteeType.User);

MessageQueueAccessControlEntry aceSystem = new
System.Messaging.MessageQueueAccessControlEntry(trustee,
System.Messaging.MessageQueueAccessRights.FullControl);

MessageQueueAccessControlEntry aceOwner = new
System.Messaging.MessageQueueAccessControlEntry(owner,
System.Messaging.MessageQueueAccessRights.FullControl);

acl.Add(aceSystem);
acl.Add(aceOwner);

myQueue.Permissions = acl;