This article was previously published under Q244700
When you create a new MSMQ resource in Cluster Administrator with the Configure Application Wizard or the New Resource Wizard, you may receive the following error messages:
NOTE: This may occur after setting the required dependencies and clicking Next on the Application Resource Name and Description page of the Configure Application Wizard or on the first page of the New Resource Wizard.
Title: Cluster Application Wizard Description: An error occurred attempting to set common properties on the 'msmq' resource: The device is not ready. Error ID: 21 (00000015)
Title: Cluster Administrator Description: An error occurred attempting to read properties for the 'msmq' resource: The device is not ready. Error ID: 21 (00000015)
NOTE: The name "msmq" in the preceding sample error messages may be different depending on what name was given to the resource in the wizard.
Also, the Application Event Viewer may contain the following error entry:
Source: MSMQ Cluster Resource Event ID: 2000 Description: Message Queuing Cluster Resources are not supported on this node since Message Queuing Server is not installed. You may install Message Queuing by running Add/Remove Programs from Control Panel, click Windows Components, and click Message Queuing.
This problem can occur if the MSMQ service has not been installed on the node that is the owner of the group to which MSMQ is being added. Note that this is not necessarily the node that is running Cluster Administrator Wizards to add the resource. Also, the service must be installed with the same settings on all nodes that will be possible owners of this MSMQ cluster resource.
To work around this problem:
Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Windows Components. If there are no outstanding configurations, the Windows Component Wizard starts automatically. If it does not, click Windows Components.
Click to select Message Queuing Services check box, and then click Next. Now configure MSMQ as needed for your environment. For more information about these options, view Windows 2000 Help for this topic.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.