Home

 

When you get a 'group not found' error

 

This problem can arise because WebSphere MQ loses access to the local mqm group when Windows 2000 or Windows 2003 servers are promoted to, or demoted from, domain controllers. The symptom is an error indicating the lack of a local mqm group, for example:

>crtmqm qm0
AMQ8066:Local mqm group not found.

Altering the state of a machine between server and domain controller can affect the operation of WebSphere MQ, because WebSphere MQ uses a locally-defined mqm group. When a server is promoted to be a domain controller, the scope changes from local to domain local. When the machine is demoted to server, all domain local groups are removed. This means that changing a machine from server to domain controller and back to server loses access to a local mqm group.

To remedy this problem, recreate the local mqm group using the standard Windows 2000 or Windows 2003 management tools. Because all group membership information is lost, reinstate privileged WebSphere MQ users in the newly-created local mqm group. If the machine is a domain member, also add the domain mqm group to the local mqm group to grant privileged domain WebSphere MQ user IDs the required level of authority.

 

Parent topic:

Guidelines for Windows 2000 and Windows 2003

fa13370_

 

Home