SearchCatalogAvailabilityMonitor showing unhealthy for all database on DAG member mailbox server

Hi All

Help me to resolve server (all database) search catalogue availability monitor.

I am facing a search catalogue "Unknown" issue for newly created copy database and also on same mailbox server "SearchCatalogAvailabilityMonitor" showing unhealthy for all database.

For the newly created copy database I tried to reseed / update search index catalogue by using below PowerShell command but it stopped with below mentioned error.

[PS] C:\Windows\system32>Update-MailboxDatabaseCopy -Identity DBTest\MBX1 -CatalogOnly

 Confirm

Are you sure you want to perform this action?

Seeding database copy "DBTest\MBX1".

[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y

 

Confirm

The mailbox database copy 'DBTest\MBX1' has failed to update from server . Do you want to clean up that update

request now? Seeding cannot be requested for the same database copy until the failed request has been cleaned up by the

server, which should automatically happen within 15 minutes.

[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y

WARNING: Seeding of content index catalog for database 'DBTest' failed. Please verify that the Microsoft Search

(Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There

was no endpoint listening at

net.tcp://localhost:3863/Management/SeedingAgent-64310690-DEA4-47E1-9860-E8B2AC4E292A12/Single that could accept the

message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details..

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Identity DBTest

 

Name                                          Status          CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex

                                                              Length    Length                             State

----                                          ------          --------- ----------- --------------------   ------------

DBTest\MBX2                              Mounted         0         0                                  Healthy

DBTest\MBX1                              Healthy         0         0           2/8/2015 3:09:49 PM    Unknown

DBTest\DRMBX1                            Healthy         0         0           2/8/2015 3:09:49 PM    Healthy

Same time Result of get-serverhealth -server MBX1, also please note all database (Copy) search is in unhealthy condition and newly created copydatabase have no entry for "SearchCatalogAvailabilityMonitor".

Name

TargetResource

HealthSetName

AlertValue

SearchCatalogAvailabilityMonitor

DB01

Search

Unhealthy

SearchCatalogAvailabilityMonitor

DB06

Search

Unhealthy

Reg

Aditya

February 17th, 2015 12:37am

Hi,

Please restart the replication service and then reseed database copy to check result.

If the issue persists, please rebuild the content index manaully to check result.

Besides, here is a related thread that may help you for your reference.

https://social.technet.microsoft.com/forums/exchange/en-US/bc5f9666-6b33-47af-bf88-98917b3fe894/exchange-2013-content-index-state-failed

Best regards,

Free Windows Admin Tool Kit Click here and download it now
February 17th, 2015 9:23pm

Hi

My issue seems different. Its problem with a single server out of 3 Dag Member server.

Looking for solution yet.

Output for MailboxDatabaseCopyStatus DBTest | fl *index*

ContentIndexState            : Healthy
ContentIndexErrorMessage     :
ContentIndexBacklog          : 0
ContentIndexRetryQueueSize   : 0
ContentIndexMailboxesToCrawl :
ContentIndexSeedingPercent   :
ContentIndexSeedingSource    :

ContentIndexState            : Unknown
ContentIndexErrorMessage     : Could not find registry value of Index Status for database {64310690-dea4-47e1-9860-e8b2ac4e292a}.
ContentIndexBacklog          :
ContentIndexRetryQueueSize   :
ContentIndexMailboxesToCrawl :
ContentIndexSeedingPercent   :
ContentIndexSeedingSource    :

ContentIndexState            : Healthy
ContentIndexErrorMessage     :
ContentIndexBacklog          : 0
ContentIndexRetryQueueSize   : 0
ContentIndexMailboxesToCrawl :
ContentIndexSeedingPercent   :
ContentIndexSeedingSource    :

Reg

Aditya

February 23rd, 2015 12:17am

HI

some, please help to repair "SearchCatalogAvailabilityMonitor" for a mailbox exchange server 2013 with SP1.

Reg

Aditya

Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 3:05am

You might need to rebuild your index on the source DB first and then update the copy of the catalog on other server.
February 23rd, 2015 7:33am

Hi Deepak

Already tried to rebuild search index on primary server, its successfully done.

As I have another DR based mailbox too, and it is rebuild there successfully too.

But by same method its not happening on the problematic server.

Reg

Aditya


Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 8:07am

Hi Deepak

Already tried to rebuild search index on primary server, its successfully done.

As I have another DR based mailbox too, and it is rebuild there successfully too.

But by same method its not happening on the problematic server.

Reg

Aditya


February 23rd, 2015 1:04pm

Do you seen any resource crunch on the problematic box, if possible i would suggest to move all the mounted DB on other box and try to reboot the box and give it a try.
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2015 11:57pm

Hi Deepak

My both exchange servers on hyper V and there should not be resource problems.

However I have already rebooted server. but it wont help.

Mean while I get success to make search component healthy on my problematic server by below command but still content index folder is not coming automatically.

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer>.\installconfig.ps1 -action I dataFolder  "C:\program files\Microsoft\Exchange Server\V15\bin\search\ceres\hostcontroller\data"

Configuring Search Foundation for Exchange....

Successfully configured Search Foundation for Exchange

By running this command these are in health state now.

Name

TargetResource

HealthSetName

AlertValue

SearchCatalogAvailabilityMonitor

DB01

Search

healthy

SearchCatalogAvailabilityMonitor

DB06

Search

healthy

Reg

Aditya

February 26th, 2015 12:56pm

Please try this step on your problematic server.

Give full access permission for the below accounts on MachineKeys folder
C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys 
-Administrator
-Exchange Servers
-Exchange Trusted Subsystems
-The account which you have logged into the server.
- Restart the Microsoft Exchange Search Host Controller and Microsoft Exchange Search. 
- Run command for one DB to update CI.
Update-MailboxDatabaseCopy -Identity server\dbname -catlogonly

Free Windows Admin Tool Kit Click here and download it now
February 27th, 2015 6:08am

Hi Deepak

I tried it but its was no result. Assuming that there were problem with exchange program files too, hence I prepared a new server in place of exiting one.

Now issue resolve. Thanks for your support. :-)

Reg

Aditya

March 18th, 2015 6:56am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics