none
"KHI: Too many failed message tracking requests via task" in Exchange 2010 SP1 management pack?

    Question

  • I asked this over in the SCOM Management Packs forum, and no one has any information for me other than "Don't do so many message tracking requests" and file a bug on connect for the lack of Company Knowledge, so I thought I would see if anyone here has any idea what is causing these alerts to be raised?

    http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/089b0c7c-77c5-47ef-9e48-7e44a8f1d2a1

    I am seeing the above alert now that I am running Exchange Server 2010 SP1 management pack version 14.2.71.0.

    Bing shows nothing on the error, and clicking on the useless "External Knowledge Sources" link in Product "Knowledge" brings you to a 404 "Page Not Found" page.

    I have noticed that in almost all the alerts I get now, whicch at least seems more homest than thee ones I have been getting for the last two years that say "Thank you for clicking the link that brought you to this page. We do not currently have an article to resolve this specific issue. Your attempt to get to content for this alert helps us prioritize the Exchange Server 2010 Management Pack alerts for which we will be providing detailed explanations and user actions."

    Anyway, back to this alert - what is it, and how do I resolve the issue that causes it?

    Karl


    http://unlockpowershell.wordpress.com
    Co-Author, Windows PowerShell 2.0 Bible
    -join("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})
    Thursday, June 30, 2011 8:40 PM

Answers

  • Just got confirmation from Microsoft that this is due to a bug.

    As you can see from the description, this alert refers to MessageTracking on a CAS server. This happens when users use the ECP to track messages. If their query returns no results, Exchange considers this an error (bug)!

    So, when the number of “failed” queries exceeds 3 or 5%, you get this warning in SCOM.

    Until this bug gets fixed, this can be ignored as long as you don’t see loads and loads of this for the same server, for example, which could indicate a problem with the MessageTrackingLogs, with the ECP, etc...

     

    Hope this helps!


    http://LetsExchange.blogspot.com
    Tuesday, December 13, 2011 4:41 PM

All replies