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.
The list of MQIS servers in registry is empty.
|English: Request a translation of the event description in plain English.|
See ME839929 for information on fixing this event.
This event may be recorded on a stand-alone server that has Message Queuing Services installed that it is not part of any domain.
From a newsgroups posting: "The combination of NT4 supporting server and W2K dependent client is not supported. You can install a W2K Independent Client in an NT4 environment, though. When you install Independent Client, you'll be asked for the name of your site controller. Give the name of one of your NT4 PSCs (or the PEC). The Independent Client will join your NT4.0 MSMQ Enterprise just like an NT 4.0 IC or any other MSMQ 1.0 system. At that point, a program running on your Windows 2000 system can open a queue anywhere in your MSMQ Enterprise just like any of the NT 4.0 systems do. You can use pathname to open public or private queues, you can use MQLocate to search for a public queue, etc."
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated