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 topology doesn’t contain a route to Exchange 2000 Server or Exchange Server 2003 server <server> in Routing Group <group> in routing tables with the timestamp <timestamp>.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This Warning event indicates that the specified routing table does not have route information to the routing group where the specified server resides. Therefore, routing is unable to route messages to any servers in this routing group. This error can occur in the following situations:
- Microsoft Exchange 2000 Server or Exchange Server 2003 routing groups are removed and routing group connectors are removed, leaving an Exchange 2000 or Exchange 2003 routing group disconnected from the rest of the organization.
- A routing group connector was not created between the Exchange Server 2007 routing group and an Exchange 2000 or Exchange 2003 routing group during setup of the first Hub Transport server.
- A routing group connector is misconfigured.
- Because of Active Directory replication latency, the route information is not yet available to the server that registered this event". See MSEX2K3DB for more details.
|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