MSMQ Installation in Windows 2003 Cluster
John
We have MSDTC, MSMQ installed as Cluster Resource in Windows 2003 Server.
MSMQ is installed on each nodes. When ever we move group to another node,
MSMQ is failing in the cluster administrator (windows event log is showing as
"MSMQ Cluster Resource DLL" is not getting authorized from AD. Event ID: 2011
After comparing with other server, we are seeing MSMQ [Message] Service is
available on active node, not in the secondary node. in this scenario the
failover testing is working fine.
please advice for how to trouble shoot this issue. Thanks in advance.
John Breakwell (MSFT)
There are 3 MSMQ services running on the cluster:
1 Node A local service - usually switched off.
2 Node B local service - usually switched off.
3 Clustered resource group service - the one you actually use.
The clustered MSMQ service only exists on one node at a time.
Whenever you fail it over, it destroys the old service and creates the new
service from scratch.
So if you look in the Services snap-in you should see only one service on
the passive node and two on the active node.
Event ID 2011 is usually resolved by enabling Kerberos on MSMQ's Network
Name resource.
302389 Description of the properties of the cluster Network Name resource in
Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;302389
The "Enable Kerberos Authentication" option is in the user interface for the
Network Name resource and should be enabled.
This will create the computer object in AD for the computer object if you
are getting the error "Unable to create Message Queuing objects in Active
Directory:
0xc00e050f".
Cheers
John Breakwell
"John" <Jo...@discussions.microsoft.com> wrote in message
news:3D376540-25AE-497B...@microsoft.com...