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: 115 Source: IMAP4SVC

Source
Level
Description
The service could not bind instance <instance number>. The data is the error code.
Comments
 
As per Microsoft: "This issue can occur because TCP/IP, which includes the SMTP, POP3, and IMAP4 protocols, requires a unique socket for each instance. A TCP/IP socket is composed of an Internet Protocol (IP) address and Transmission Control Protocol (TCP) port pair. To generate a unique socket, either the TCP port or the IP address of each instance must be unique to the given virtual server". See MSEX2K3DB for additional information about this event.
See the link to "EventID 115 from source W3SVC" for details on this event.
Make sure you have a unique IP address for each virtual server. See ME256132.

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 www.eventid.net.

Read more...

 

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.

Read more...