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 service could not bind instance <instance number>. The data is the error code.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is IMAP?
What is the role of a POP3/IMAP virtual server?
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.
|Private comment: Subscribers only. See example of private comment|
|Links: ME256132, EventID 115 from source W3SVC, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated