Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Message Queuing was unable to create the msmq (MSMQ Configuration) object in Active Directory (Error: <error code>).
|English: Request a translation of the event description in plain English.|
To see the MSMQ objects in Active Directory Users and Computers, click View on the menu and ensure that the Users, Groups, and Computers as containers and Advanced Features options are ticked.
For a correctly installed MSMQ object, MQPing should get a response. To see this in Windows 2003, alternate-click the MSMQ object and click Send MQPing message. A good response is the message "The computer responded. MQPing was successful". A bad response is a long wait followed by the message "The computer did not respond. MQPing failed”.
See MSMQ Frequently Asked Questions for more details.
The following procedure assumes that Windows 2003 is installed. The procedure for Windows 2000/XP is similar. If this EventID appears on the log of a computer (and was not later followed by EventID 2060 from source MSMQ) then proceed as follows:
Go to Start -> Settings -> Control Panel -> Add or Remove Programs. Click Add/Remove Windows Components. Select Application Server and click Details. Select Message Queuing and click Details. Make a note of the names of all currently installed components. Click OK. Untick Message Queuing. Click Yes. Click OK. Click Next. Click Finish. Now reinstall the components that were removed. Examine the event log. This Event ID should not appear. Look for EventID 2060 from source MSMQ.
From a newsgroup post: "If you have problems reinstalling MSMQ please go to Active Directory Users and Computers Snap-in on your DC with the domain admin account to check if there are any MSMQ objects already existing under this application server. If there are, delete them and then try to install again.
Another thought is if the server is a Win2k server without SP4, you can first install SP4 on it and then reinstall MSMQ again. It contains some updated components of MSMQ". See the link to "Google thread - Problems re-installing MSMQ on A/P cluster" for the original thread.
|Private comment: Subscribers only. See example of private comment|
|Links: Google thread - Problems re-installing MSMQ on A/P cluster, Microsoft Message Queuing (MSMQ) Center, MSMQ Frequently Asked Questions, EventID 2060 from source MSMQ|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated