Message Queuing failed to bind to port 1801 in Cluster resource

[Aaron]

I am attempting to create a MSMQ cluster resource. When I try to bring it on
line, I get the following error:

Event Type: Error
Event Source: MSMQ$MSMQ
Event Category: None
Event ID: 2170
Date: 9/22/2008
Time: 9:48:15 PM
User: N/A
Computer: TSS4W475V3
Description:
Message Queuing failed to bind to port 1801. The port may already be bound
to another process. Make sure that the port is free and try to start Message
Queuing again. If this problem arises during setup, you must free the port
and run setup again.

MSMQ is functing fine on each node. This is the 3rd 2 node cluster I am
trying to set up. All built exactly the same. I did not have any problems
on the other 2 clusters?

Any Ideas?

THanks
Aaron

[Frank Boyne]

"Aaron" <Aa...@discussions.microsoft.com> wrote in message
news:93BC4118-74CC-4A09...@microsoft.com...

> MSMQ is functing fine on each node. This is the 3rd 2 node cluster I
> am
> trying to set up. All built exactly the same. I did not have any
> problems
> on the other 2 clusters?
>
> Any Ideas?

It is possible that port 1801 is being used by something else. One way
to check would be to run the command

netstat -a -n -b

If port 1801 is in use the output should include a line that looks
something like this...

Proto Local Address Foreign Address State
PID
TCP 0.0.0.0:1801 0.0.0.0:0 LISTENING
2744
[mqsvc.exe]

Mind you, I have no idea how to run a netstat command in the context of
a clustered resource.

I have to say though that it seems quite unlikely for some other piece
of software to be using port 1801. Is it possible that your clustered
MSMQ resource is colliding with another copy of MSMQ running on the same
node?