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: 17113 Source: MSSQL$SQLDB01

Error 32(The process cannot access the file because it is being used by another process.) occurred while opening file '<file>' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options and correct or remove them if necessary.
Error 3 (The system cannot find the path specified.) - We received this message when we tried to start the SQL server in in Single-User Mode by specifying the "-m" startup parameter. The problem was that we did not add semi-colon (;) between -m and the other startup parameters. Once we added ;, the server started fine, in single-user mode (for a master database restore).
I have set up a local user to start all SQL 2005 services, added that user to all the MSSQL local groups and this error started to appear. Adding the user to the Local Administrator group fixed the error.

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.