Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1013 Source: MSExchangeCluster

MSExchangeCluster - (<server>) Failed to get protocol IP address and put bindings from the metabase.
When we installed the certificate and left the SSL port number empty, we received these error messages. To resolve the problem we added the port number of SSL 443, and restarted IIS.
This problem can also be caused by misconfiguring IIS on the passive node of a cluster. Make sure the settings are the same for both nodes, especially SSL port and certificate settings.
By far, the most common cause of Event ID 1013 is metabase corruption. Metabase corruption itself can occur for a variety of reasons, including the following: antivirus software scanning the %systemroot%\system32\inetsrv\metabase.bin file, Iisadmin.exe process stopped or killed unexpectedly, unsupported editing of the metabase, and disk corruption or other hardware failures. See MSEX2K3DB for additional information about this event.

Windows Event Log Analysis Splunk App

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



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.