Exchange 2016 Indexing

Question

Exchange 2016 Indexing

Marco Camparsi 21

I seem to be having a fun time with a Database and search not working.

I followed the standard go to:

Get-Service -Name "HostControllerService","MSExchangeFastSearch" | Stop-Service

went to DB folder and deleted the GUID.single file

Get-Service -Name "HostControllerService","MSExchangeFastSearch" | Start-Service

and then

Get-MailboxDatabaseCopyStatus * | Sort Name | Select Name, Status, ContentIndexState

normally it would show the database as crawling and start rebuilding the GUID dir

however it shows as healthy, no sign of a GUID and search is def not working on Outlook or OWA

Get-MailboxDatabase | Select-Object Name, IndexEnabled | Format-Table -AutoSize

DB shows as True so indexing seems to be enabled. I'm stumped, any help would be appreciated tyia

Accepted answer

0 additional answers

Your answer

Answer 1

Yuki Sun-MSFT 41,376 Moderator

Hi @Marco Camparsi ,

What is the specific build or CU of your Exchange 2016?

Please have a look at the Event Viewer to see if there's any clues out there. If you see the instance of Event 1012, it's suggested to follow the instructions in the blog below and check the result:
Exchange 2013: FAST Search Technology Failed
(The blog talks about Exchange 2013, but it can be applied to Exchange 2016 as well.)

In case the issue persists, you can also try creating a new mailbox database, moving one of the user mailboxes there and see if search can work properly.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Yuki Sun-MSFT 41,376 Reputation points Moderator

2023-01-05T07:53:18.967+00:00

Hi @Marco Camparsi ,

I am writing to see if there is any progress on the issue. Any update would be appreciated.
Marco Camparsi 21 Reputation points

2023-01-07T19:43:37.837+00:00

Hi YukiSun,
Thank you soo much for your response, I believe the root cause was in the service itself, this server was running CU22 and there were plans to update to CU23 over the holiday break. my hope was to either run a repair using CU22 or to run the CU23 update with the hope it would fix problems.

in addition to this, over the break (as this was a single server STDR 2016 running AD and Exchange) we had intended to add an additional server to compliment this one, however after we added the second server, added AD, the exchange server took a turn for the worst, and completely crumbled, now I can't even connect using Exchange Management shell or Admin center at all. after attempts on repairing the decision has been made extract the EDB file and to migrate to 365. I whish I had a working exchange environment to do this but that's life I guess.

Thank you so much for your attempt at help. I very much appreciate it.
Marco Camparsi 21 Reputation points

2023-01-07T19:46:00.47+00:00

even though a fix couldn't be applied, this was the closest response to an answer and I will mark it as that.

Thank you for your help
Yuki Sun-MSFT 41,376 Reputation points Moderator

2023-01-09T06:37:03.42+00:00

Thanks @Marco Camparsi for getting back to us with the current status of this thread. Hopefully everything can get back to work soon.

Share via

Exchange 2016 Indexing

0 additional answers

Your answer