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: 107 Source: ScheduleandDeliveryProcessor

Schedule and Delivery Processor cannot connect to the report server database.
The event can take place after a member server is promoted to Domain Controller, and reporting services were installed on it before promotion and were configured to use the NETWORK SERVICE (or another built-in one) account to connect to the SQL server on the same host.
Use rsconfig util (i.e. rsconfig -c -a windows) to recreate valid encrypted connection information.
From a newsgroup post: "Check the ReportServer service. See what dependencies it has. Perhaps it should be configured to start only after the SQL Server services have started, so that the ReportServer service finds the SQL Server to attach to. However, this is not desirable if the SQL server is not on the same box. If the service cannot talk to the SQL catalog, it will continue to try until it is successful. Therefore, even if the ReportServer service starts first, once SQL server starts, everything should start to work".

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.