hi all, after importing the Exchange 2007 management pack for SCOM2007 r2 I've been seeing this error: Alert Monitor: Exchange 2007 Test Exchange Search Monitor Alert Description: The search performed by this test failed. - The search performed by this test failed. In the exchange powershell console: [PS] C:\>test-exchangesearch -server exchange1 -IndexingTimeout 1200 ResultFound SearchTime ----------- ---------- False -1 After some snooping around on the net looking for a way to resolve this error i found that the SCOM monitor runs a script that tests the search on the 'SystemAttendant' mailbox. First i thought it was a issue with the user executing the script, but i logged on to the exchange server as exchange-admin and ran the script manually, but i still got a timeout. All mailbox databases are Search enabled: [PS] C:\>get-mailboxdatabase | format-table Name,Indexenabled Name IndexEnabled ---- ------------ Mailbox Database 1 True Mailbox Database 3 True Mailbox Database 4 True Mailbox Database 5 True The funny part is when i test the search for a mailbox of a user, the test result comes back as a succes: [PS] C:\>test-exchangesearch -Identity userid -IndexingTimeout 1200 ResultFound SearchTime ----------- ---------- True 6 Does anybody knows what the problem could be?

Yes, Its very common issue. Do you have CCR installed. If yes then try to move cluster betwen node when you can in non business time and test it. If you have one BOX then try to reboot server and it will fix. As you see your test got succes you can also ignore this alerts. For more detail i would advise you to post one thread in SCOM forum. http://social.technet.microsoft.com/Forums/en-US/category/systemcenteroperationsmanager Anil

Anil, We have an Exchange cluster with 2 nodes with CCR (log shipping). I'll try to change the active node this evening and let you know what happens. I've already posted the same question on that forum, but did not receive an answer yet. :) thanks for the info.

Anil, I changed the active node overnight and the search works now! Thanks!

I'm getting this issue on ~15 servers in my environment now. However none use CCR and a reboot, service restart, and even Exchange repair don't help. If I specify an identity the cmd works, otherwise it fails. I've let it run as long as 10min on a server with only 2 mailboxes...still failed. Has anyone seen this before? Has anyone solved this issue?