fortch

Sorry, I should have stated that the referenced KB above, although a perfect fit, does not apply to 2008 R2. We have monthly patching, so the round that applied this month is: KB2522422, 2570791, 2515325, 2505438, 2563227, 2511250, 931906, 2463332, 2488113, 2545698, 982018, 2541014, 2506928, 2484033, 2492386, 2529073,…

Thanks -- a round of patching (2 .NET updates) and R2 SP1 addressed the problem.

I have this exact issue, but only concerning monitored machines in another forest (no trusts). Was the fix actually the KB? My DLLs are dated earlier (6/2009 rather than 9/2009) but have a higher version number (2.0.50727.4927 as opposed to 2.0.50727.4400 in the KB).