Hello
Thank you for your question and reaching out. I can understand you are having query\issues related to Indexing in Windows server 2019.
1. Execute below command from Command Prompt.
msdt.exe -ep WindowsHelp id SearchDiagnostic
2. Disable any Antivirus program or Windows firewall you may have for temporary purpose.
3. Cleanup below Temp folders location -> Open Start -> Run -> Type below location one-by-one and press enter
-> C:\Windows\Temp
-> %USERPROFILE%\AppData\Local\Temp
4. Run Disk Cleanup from Select C:\ Drive from Properties- > General -> Disk Cleanup - >Cleanup system files
5. Run sfc /scannow from elevated prompt.
6. Run below DISM commands from elevated prompt.
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
References:
https://answers.microsoft.com/en-us/windows/forum/all/windows-search-indexcatalog-gets-corrupted-daily/330eaa46-164f-49c6-bae1-048d108a1704
--If the reply is helpful, please Upvote and Accept as answer--
Windows Server 2019 Indexing status stuck on 'Loading...'
Hello,
Running W2019 (latest updates) with FSLogix 2210 HF1 and Office 365 (latest semi-annual) with per user search database. When I open Outlook and click on search tools > Indexing status, it's just forever stuck on 'Loading.....'
When I open Indexing options it just says 'Waiting to receive indexing status....'. When I do this as admin on the server it says indexing complete, but nothing is indexed (0 items). When I try to add locations to the index there are no locations available. When I click Modify locations everything is blank, i.e.: I can't add any locations to index.
I tried to move the server to an OU with no GPOs applied, no difference. Tried to rebuilt the index, no difference. When I check the user index in Appdata as well as the system index in Programdata, the file stays 8 MB in size, so it never grows.
When i check the eventlog it's giving me the errors below. Any idea how to fix this? Even with a new image built from scratch (it's non-persistent PVS) it's still not working.
Any idea?
The index cannot be initialized.
Details:
The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)
The application cannot be initialized.
Context: Windows Application
Details:
The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)
The gatherer object cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)
The plug-in in <Search.TripoliIndexer> cannot be initialized.
Context: Windows Application, SystemIndex Catalog
Details:
The specified object cannot be found. Specify the name of an existing object. (HRESULT : 0x80040d06) (0x80040d06)
The plug-in manager <Search.TripoliIndexer> cannot be initialized.
Context: Windows Application
Details:
(HRESULT : 0x8e5e0713) (0x8e5e0713)
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.
Details:
The content index catalog is corrupt. 0xc0041801 (0xc0041801)
The search service has detected corrupted data files in the index {id=4810 - onecoreuap\base\appmodel\search\search\ytrip\common\util\jetutil.cpp (310)}. The service will attempt to automatically correct this problem by rebuilding the index.
Details:
0x8e5e0713 (0x8e5e0713)
Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Server | User experience | Other
Windows for business | Windows Client for IT Pros | User experience | FSLogix
1 answer
Sort by: Most helpful
-
Limitless Technology 44,766 Reputation points
2023-03-14T08:38:38.9933333+00:00