ComputerBob post a question under Operations Manager.
Error 4506 "Data was dropped..." with text-based log file rule
Using SCOM 2007 R2 (CU5) I created a log file watcher rule that looks for specific text in entries in a Sharepoint log file (the text indicates when users are added to the Farm Admins group).  It worked fine for a few years until not too long ago when the SP team migrated the farm to a new set of servers. The rule runs fine on some of the servers, but on some of them I'm getting the repeating Event ID 4506 "Data was dropped due to too much outstanding data in the rule" error.  This has been going on since I enabled the rule on these servers, so my first thought was that since there were 39gb of logs in the folder, SCOM simply couldn't do all that at one time and failed. My attempt at solving it was to stop the healthservice, remove those files from the directory (had to leave 1 there since SharePoint was currently writing to it), and restart the SCOM service.  I still got the 4506's.  I then took it a step further and repeated teh process,

ComputerBob RE: Re: DPM 2007 on 2008 server not alerting
Yes.  When we started looking at the issue when I originally posted, she noticed that in our two environments that we manage, the two DPM 2007 versions weren't the same.  In the one that had SP1 everything was working fine, but the RTM version was the one having the trouble with logging and thus no SCOM monitoring. Tonight she updated the problem environment to DPM 2007 SP1 and the logging issue went away.  

ComputerBob RE: Re: Monitoring and reporting on a CSV log file
I did something similar a while back with regular event data that someone wanted to manipulate into an existing SSRS report rather than receive a separate report from SCOM on.  So I developed an rdl to pull the event data in, then used all sorts of left() and mid() and instr() operators to whittle down each parameter into a separate field in the SSRS report.  I bet you could do the same. The SQL query is pretty simple.  You set up your database connection and then create a query that looks like this: SELECT        TimeGenerated, LoggingComputer, EventData FROM            dbo.EventAllView WHERE        (RuleId = '1024a3e9-46db-eac7-0d41-c187354f4ef2') AND (TimeGenerated >= DATEADD(Day, - 1, GETDATE())) That one actually only pulls the last 24 hours, but you can obviously change that.  Also, you'll have to use Powershell

ComputerBob accepted an answer Re: DPM 2007 on 2008 server not alerting

ComputerBob accepted an answer Re: DPM 2007 on 2008 server not alerting