Discussion:
MSMQ stalls when DC's are taken offline
(too old to reply)
Andrew Maloney
2008-09-11 03:09:01 UTC
Permalink
We have two 2000 DC's in the same AD site running MSMQ 2.0. When we re-boot
one of them MSMQ will stall on one of the client servers (running 2003 MSMQ
3.0). It seems to recover itself in about 10 mins.

Is there any way of determining which DC is responding to MSMQ requests from
the client servers? Also, is there any way to force these connections to one
of the servers (so the other one can be rebooted)?

thanks,

Andrew
John Breakwell (MSFT)
2008-09-11 11:35:07 UTC
Permalink
Hi Andrew,

I was going to ask why you had 2000 DCs in the same site but I expect that
wouldn't be helpful :-)

Try looking at:
CurrentMQISServer
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/58732.mspx?mfr=true
"Stores the computer name of the MQIS server currently selected by Message
Queuing on this computer. The MQIS client uses the server specified for MQIS
queries."

You can override this with:
StaticMQISServer
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/58773.mspx?mfr=true
"The value of this entry replaces the values of the MQISServer and
CurrentMQISServer entries, so that this server is the only one known to the
client."

Note that you would need to restart the MSMQ service to pick up the change.

Have you investigated why the client has a problem?
What sort of activity is your application performing at the time?

Cheers
John Breakwell (MSFT)
Post by Andrew Maloney
We have two 2000 DC's in the same AD site running MSMQ 2.0. When we re-boot
one of them MSMQ will stall on one of the client servers (running 2003 MSMQ
3.0). It seems to recover itself in about 10 mins.
Is there any way of determining which DC is responding to MSMQ requests from
the client servers? Also, is there any way to force these connections to one
of the servers (so the other one can be rebooted)?
thanks,
Andrew
Frank Boyne
2008-09-11 22:55:36 UTC
Permalink
Post by Andrew Maloney
We have two 2000 DC's in the same AD site running MSMQ 2.0. When we re-boot
one of them MSMQ will stall on one of the client servers (running 2003 MSMQ
3.0). It seems to recover itself in about 10 mins.
Could you offer a bit more detail about "MSMQ will stall on one of the
client servers"? I would expect a Domain Controller restart to affect
things that depend on the MQ information service - things like
translating Path Names into Format Names or searching for public queues.
I wouldn't expect message transfer or access to the queues themselves to
be affected by a domain controller restart.

Loading...