Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5563
  • Last Modified:

Exchange 2013 DBs have Content Index State Unknown

I have 2 exchange 2013 servers with 4 DBs each, exch one has 2 active mounted and 2 passive healthy.

This morning I found that all 4 DBs are mounted on ExServer2, the 4 DBs on ExServer1 are healthy but their Content index state is unknown.

1. I could active the 2 DBs back to ExServer1, I get an error about the content index state that is unknown
2. Suspend/Resume did do anything
3. Suspend/Update stated movind file and I the end I get an error:

warning
Seeding of content index catalog for database 'DB4' failed. Please verify that the Microsoft Search (Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: Could not connect to net.tcp://localhost:3863/Management/SeedingAgent-6BCDDF4B-88E9-47CE-8EB6-836714D1AE9912/Single. The connection attempt lasted for a time span of 00:00:02.0313113. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:3863. .

 

Checked: all services are running.
1
nourben
Asked:
nourben
  • 11
  • 6
  • 4
1 Solution
 
Adam FarageEnterprise ArchCommented:
1) Try restarting the FAST Search Service (MS Exchange Search service)
2) If this does not work, recreate the catalog file (e.g: content index)

- Stop the MSExchange Search service
- In the location of the database find the content index files (it should be a separate folder with the words like CatalogData-blahblahblah)
- Remove that folder (recommend moving it somewhere else
- Start the search service, and wait for the folder to get recreated (takes about 10 -15 minutes)
0
 
nourbenAuthor Commented:
Is it the folder with numbers? see attachment
DB.JPG
0
 
Adam FarageEnterprise ArchCommented:
Yes.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
nourbenAuthor Commented:
Nothing worked, I even removed the DB copy, deleted the folders, added the copy and the same thing.

Got this error
error
DB4
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: The specified database isn't configured for replication and therefore cannot be used to perform seed operations
0
 
Adam FarageEnterprise ArchCommented:
Do me a favor, run Get-MailboxDatabase "DB Name" | Get-MailboxDatabaseCopyStatus please and post it here. Also run the following command, as I think this could be replication network related:

Get-DatabaseAvailabilityGroupNetwork | FL
0
 
nourbenAuthor Commented:
I cannot post the second one because it has server's name and IP addresses
0
 
nourbenAuthor Commented:
First one
0
 
nourbenAuthor Commented:
First one
Issue.JPG
0
 
Adam FarageEnterprise ArchCommented:
Restart fast search on the passive copy and see what happens.
0
 
nourbenAuthor Commented:
I have restarted the server a couple of time already and there are no Fast Search, I see:
Microsoft Exchange Search
Microsoft Exchange Search Host controller
0
 
Adam FarageEnterprise ArchCommented:
Restart both Search Service, but on the passive node. I thought you were doing it on the active node.
0
 
nourbenAuthor Commented:
Just did again, nothing changed

Server1:
DB Active Mounted
Content Index state: Healthy

Server2:
DB Passive Healthy
Content Index state: Unknown

BTW: this is test environment
0
 
Adam FarageEnterprise ArchCommented:
What does your DAG network look like?
0
 
nourbenAuthor Commented:
Changed servernames and IPs
DAG.JPG
0
 
nourbenAuthor Commented:
Problem was the OS hardening, Local Policy FIPS needs to be disabled.
1
 
nourbenAuthor Commented:
In our environment FIPS needed to disabled.
0
 
Arun RajaExchange administratorCommented:
I have two exchange Server .
ONe server content index state was healthy but another server having all the database content index state unknow status.

. i try follow all setting still same Issue
0
 
Arun RajaExchange administratorCommented:
I have two exchange Server .
ONe server content index state was healthy but another server having all the database content index state unknow status.

. i try follow all setting still same Issue

how to check  the OS hardening, Local Policy FIPS needs to be disabled.
0
 
Arun RajaExchange administratorCommented:
No One Answer Question?
0
 
Arun RajaExchange administratorCommented:
No One answer this Question
0
 
nourbenAuthor Commented:
Go to control panel
Click on Adminstration tools
Click on Local Security Policy
Under Security Settings/Local Policies/Security Options
Make sure that "System cryptography: Use FIPS compliant algorithms for encryption..." is disabled

This is what fixed my issue, hope you have the same problem
EE.jpg
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 11
  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now