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: 33333 Source: DataAccessLayer

Data Access Layer rejected retry on SqlError: Request: p_RelationshipDiscovered -- (RelationshipId=392fbb59-7d69-a37a-e629-1f824dbacb6e) (SourceEntityId=cc7b3f66-b6b4-3199-399f-b395dfa8a920) (TargetEntityId=5e9c4cfd-00be-774b-b749-67f01b5217f1) (RelationshipTypeId=0c18d101-8d27-4333-6d54-682fe19a5896) (DiscoverySourceId=f15f0030-c44f-3250-52e4-7e40f07bea45) (HealthServiceEntityId=c83cdf96-ccea-ad8f-a893-1a3822e9b182) PerformHealthServiceCheck=True) (TimeGenerated=9/6/2008 4:55:36 PM) (RETURN_VALUE=1)
Class: 16
Number: 777980002
Message: The specified relationship doesn't have a valid source.
From a Microsoft blog: "Sometimes after installing an agent or importing a management pack you may see event number 33333 logged by the Data Access layer. In many situations this error is caused by the fact that proxying is not enabled for a particular agent. You can figure out using powershell the name of the agent that requires proxying to be enabled using the following command:

Get-MonitoringObject -id:'2090A6E7-27D2-425F-5617-6EE7B2291970' | ft DisplayName

This will provide the name of the agent that needs to have proxying enabled.

Note: You will need to replace the GUID that you use as the parameter to the cmdlet with the first GUID that you see in the alert."

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.