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: 2075 Source: MSExchangeDSAccess

Process <process name> (PID=<pid number>). DsBind failed. , hr=<error code> delta T=0." The operation will be retried.
I was getting this error on startup, not shutdown, and the Exchange services would not start. I fixed it by running netdiag on the Domain Controller. Netdiag can be installed from the tools directory on the Win2K server CD. When I ran netdiag, it told me I had errors in my DNS settings. I ran “netdiag /fix”, and then the Exchange server was able to startup.
- Error code: 0x8007054b - See ME322856 and ME895858.
- Error code: 0x800706ba - See ME842471.
Several posts suggest adding the same DNS server for both primary and secondary DNS entries on the Exchange server. However, this does not solve all of the 2075 errors. Another post states that this errors start occuring after the installation of Windows 2000 SP2 and that as per Microsoft will be fixed with Exchange 2000 SP2. The error are generated when the computer is shutdown. As a workaround until E2K SP2 make sure that E2K and IIS services are stopped before the computer is shutdown (i.e. shutdown scripts in AD group policies).

Variations of the error:

Error codes:
- 0x800706bb - no info
- 0x80070862 - no info
- 0x8007054b - See ME312425.
See the link to ME306195.

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.