All of my Ex2k7 servers report the following alert: Alert: Test-SystemHealth did not run successfully Monitor: Exchange 2007 Test-SystemHealth Monitor Description: Unable to execute Test-SystemHealth cmdlet. Error HRESULT E_FAIL has been returned from a call to a COM component. All this monitor does is verify that the cmdlet has executed. Searching forums and the web shows little to no results on how to resolve this error. I checked the sync time and interval and they are correct. What can be done here?

Looks like pretty unique to your situation based on the lack of others reporting the same issue. Have you tried to run the cmdlet manually on the Exchange server as a user with appropriate permissions? Do you have any Run As Accounts set up called for in the MP Guide?Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com

I'm seeing the same thing after moving to SCOM R2: State: New Alert: Test-SystemHealth did not run successfully Source: ExBpa (servername.domain.name) Path: servername.domain.name Last modified by: System Last modified time: 8/2/2010 7:02:25 PM Alert description: Unable to execute Test-SystemHealth cmdlet. Error HRESULT E_FAIL has been returned from a call to a COM component. Seeing this from only a few of the twelve mail clusters in our environment, but with some regularity (one every other day or two).

Do you see anything relevant in the event log on the exchange server producing the error in either the application log or the scom agent log?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. If the post wasn't the exact answer or was helpful in leading you to the answer, please vote it as helpful. This can be beneficial to other community members reading the thread.

I have the same situation, Exchange 2007 standalone with SP2 (no rollup updates). when i execute the cmdlet manually it seems to work fine. this is the first time i'm bumped to a problem like this after several different diployments. any idea ?

You could try enter this Powershell command: Set-ExecutionPolicy Unrestricted And then try to run the cmdlet. And have you created a test-mailbox using the script: New-TestCasConnectivityUser.ps1. To create the test mailbox, on each Exchange 2007 Mailbox server, open the Exchange Management Shell , locate the Scripts directory under the installation path for Exchange Server 2007 (usually \Program Files\Microsoft\Exchange Server\Scripts). Certifications: MCSA 2003|MCSE 2003|MCTS| MCTIP:SA

Hey Pete! Same probleme here at a customer... PoSh is unrestricted, HealthService runs with Local System, so no RunAs should be necessary. When I run the script manually (and excluded the check for Local System) it runs as expected. Will try it now with LS. The interesting thing is, that I get the BPA event (0% and 100%) two times running within the workflow. Any idea I appreciate! Cheers, Patrick0101001101111001011100110111010001100101011011010100001101100101011011100111010001100101011100100101001001101111011000110110101101110011 http://www.systemcenterrocks.com All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

Hey Pete! Same probleme here at a customer... PoSh is unrestricted, HealthService runs with Local System, so no RunAs should be necessary. When I run the script manually (and excluded the check for Local System) it runs as expected. Will try it now with LS. The interesting thing is, that I get the BPA event (0% and 100%) two times running within the workflow. Any idea I appreciate! Cheers, Patrick UPDATE: it seems that this is solved with Exchange SP3 RU2. Customer has SP1 installed... 0101001101111001011100110111010001100101011011010100001101100101011011100111010001100101011100100101001001101111011000110110101101110011 http://www.systemcenterrocks.com All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.