Hi,
when running Test-ExchangeSearch on my Mailbox exchange 2010 servers, i get the result as "Time out for test thread" (when i specify the identify of a mailbox on the either MBX server, i get the same error as when it uses the systemmailbox)
I have two CAS+HUB servers setup in a casarray, and two MBX servers in a DAG. the Exchange version is:Microsoft Exchange Server 2010 Service Pack 3 (SP3) (14.3 build 123.4)
i tried adding the perfmon counter "MSExchange Search Indexer" but I was getting "Can't load counters" and was unable to add counters to monitor.
i've also rebooted both MBX servers.
the only error in eventvwr after this is run is:
Log Name: ApplicationSource: MSExchangeIS Mailbox Store
Date: 1/07/2013 4:12:53 PM
Event ID: 9877
Task Category: Content Indexing
Level: Error
Keywords: Classic
User: N/A
Computer: COLOMBX01.xxxxxx.local
Description:
Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: Mailbox Database Melbourne
Error Code: 0x8007007e
here is the verbose output:
[PS] C:\Windows\system32>Test-ExchangeSearch -verboseVERBOSE: [06:41:28.217 GMT] Test-ExchangeSearch : Active Directory session settings for 'Test-ExchangeSearch' are: View
Entire Forest: 'False', Default Scope: 'xxxxxx.local', Configuration Domain Controller: 'melmail01.xxxxxx.local',
Preferred Global Catalog: 'melmail01.xxxxxx.local', Preferred Domain Controllers: '{ melmail01.xxxxxx.local }'
VERBOSE: [06:41:28.217 GMT] Test-ExchangeSearch : Runspace context: Executing user:
austock.local/Organisation/ITSupport/User/System Accounts/Backup User, Executing user organization: , Current
organization: , RBAC-enabled: Enabled.
VERBOSE: [06:41:28.217 GMT] Test-ExchangeSearch : Beginning processing &
VERBOSE: [06:41:28.217 GMT] Test-ExchangeSearch : Instantiating handler with index 0 for cmdlet extension agent "Admin
Audit Log Agent".
VERBOSE: [06:41:28.264 GMT] Test-ExchangeSearch : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
{}, Exclusive Configuration Scope(s): {} }
VERBOSE: [06:41:28.405 GMT] Test-ExchangeSearch : Searching objects
"SystemMailbox{f9ef9ee6-12ba-4d3c-a8fd-76b6107fde26}" of type "ADSystemMailbox" under the root "$null".
VERBOSE: [06:41:28.467 GMT] Test-ExchangeSearch : Previous operation run on global catalog server
'melmail01.austock.local'.
VERBOSE: [06:41:28.514 GMT] Test-ExchangeSearch : Searching objects
"SystemMailbox{43f20a02-c340-4ff5-b75f-ec623eef652d}" of type "ADSystemMailbox" under the root "$null".
VERBOSE: [06:41:28.530 GMT] Test-ExchangeSearch : Previous operation run on global catalog server
'melmail01.austock.local'.
VERBOSE: [06:41:28.545 GMT] Test-ExchangeSearch : Admin Audit Log: Entered Handler:Validate.
VERBOSE: [06:41:28.545 GMT] Test-ExchangeSearch : Admin Audit Log: Entered ClassFactory:InitializeConfig.
VERBOSE: [06:41:28.577 GMT] Test-ExchangeSearch : Admin Audit Log: Exited ClassFactory:InitializeConfig.
VERBOSE: Testing Exchange Search.
VERBOSE: [06:41:28.702 GMT] Test-ExchangeSearch : Resolved current organization: .
VERBOSE: [06:43:29.307 GMT] Test-ExchangeSearch : Getting catalog state for Mailbox Database "Mailbox Database
Interstates"...
VERBOSE: [06:43:29.307 GMT] Test-ExchangeSearch : Catalog state: Notifications.
VERBOSE: [06:43:29.307 GMT] Test-ExchangeSearch : Getting the indexing state for mailbox
"SystemMailbox{f9ef9ee6-12ba-4d3c-a8fd-76b6107fde26}" ...
VERBOSE: [06:43:29.307 GMT] Test-ExchangeSearch : Mailbox state: Done, Crawl start time: 2013-06-13T23:31:17.
VERBOSE: [06:43:29.323 GMT] Test-ExchangeSearch : Getting the message indexing state...
VERBOSE: [06:43:29.338 GMT] Test-ExchangeSearch : Document state: InRetry, state = 101.
VERBOSE: [06:43:29.338 GMT] Test-ExchangeSearch : TimeSinceLastNotificationWasIndexed for MDB Mailbox Database
Interstates is 0 seconds.
Database Server Mailbox ResultFound SearchTime Error
InSeconds
-------- ------ ------- ----------- ---------- -----
Mailbox D... COLOMBX02 SystemMai... False -1 Time out for test thread.
VERBOSE: [06:43:29.417 GMT] Test-ExchangeSearch : Getting catalog state for Mailbox Database "Mailbox Database
Melbourne"...
VERBOSE: [06:43:29.417 GMT] Test-ExchangeSearch : Catalog state: Notifications.
VERBOSE: [06:43:29.432 GMT] Test-ExchangeSearch : Getting the indexing state for mailbox
"SystemMailbox{43f20a02-c340-4ff5-b75f-ec623eef652d}" ...
VERBOSE: [06:43:29.432 GMT] Test-ExchangeSearch : Mailbox state: Done, Crawl start time: 2013-06-13T23:31:19.
VERBOSE: [06:43:29.448 GMT] Test-ExchangeSearch : Getting the message indexing state...
VERBOSE: [06:43:29.463 GMT] Test-ExchangeSearch : Document state: Unknown, state = 0.
VERBOSE: [06:43:29.463 GMT] Test-ExchangeSearch : TimeSinceLastNotificationWasIndexed for MDB Mailbox Database
Melbourne is 0 seconds.
Mailbox D... COLOMBX01 SystemMai... False -1 Time out for test thread.
VERBOSE: [06:43:29.479 GMT] Test-ExchangeSearch : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [06:43:29.510 GMT] Test-ExchangeSearch : Ending processing &
the reason i was even looking at this test was that whilst monitoring the Microsoft.Exchange.Search.ExSearch.exe performance in taskmgr on both my CAS+HUB servers, both servers show that process constantly using average 10-15% CPU. I read in an MS article (for 2007) that this process shouldnt be more than 1% continuously. Given my setup is a vm environment, I'm just trying to ascertain whether the servers will have enough resources to cope when i migrate all mailboxes from my current live 2003 exchange environment to this new 2010 environment. I only have 150 mailboxes and probably 2/3 of those users will also have mobile devices connecting to Mail. it doesnt seem like a lot but this constant CPU use is a tad worrying.
so i guess it's two issues: CPU usage and the Test-ExchangeSearch results
any suggestions