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.
Process <process name> (PID=<process id>). The site monitor API was unable to verify the site name for this Exchange computer - Call=<function> Error code=<error code>. Make sure that Exchange server is correctly registered on the DNS server.
|English: Request a translation of the event description in plain English.|
According to ME2025528, this may be recorded when network connectivity is affected such as:
- Transient DNS failures
- Transient issues with Domain Controllers
- Transient network connectivity issues
- Network switches that have the PortFast functionality disabled on the ports to which the Exchange servers connect
See the article for workaround.
In my case, I was getting events 2080, 2601, 2604 and 2501 from the same source on a clustered Exchange 2007 server approximately every 15 minutes. It was a permissions error. The names of both the pieces of the cluster were in the Exchange Servers group but the virtual name of the cluster itself was not. Adding it to the group and rebooting both servers corrected the issue.
This event may occur for one or more of the following reasons:
1. The Exchange server is not correctly registered on the DNS server.
2. The Site monitor API cannot find the correct domain name.
See MSEX2K3DB for additional information about this event.
Several newsgroup posts suggest a simple reboot of the server will fix this issue.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (2) - More links...|
Send comments or solutions
- Notify me when updated