SharePoint Server 2019 - Search service application issue

%3CLINGO-SUB%20id%3D%22lingo-sub-833110%22%20slang%3D%22en-US%22%3ESharePoint%20Server%202019%20-%20Search%20service%20application%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833110%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Everyone%20!%3C%2FP%3E%3CP%3EI%20have%20been%20deployed%20SharePoint%20Farm%3C%2FP%3E%3CP%3Ecreated%20Web%20Applications%20and%20Host-based%20Site%20Collections%3C%2FP%3E%3CP%3EEveything%20was%20fine%20until%20the%20Search%20Service%20Application%20stop%20working.%3C%2FP%3E%3CP%3EI%20tried%20to%20analize%20the%20issue%2C%20track%20after%20ULS%20logs%20and%20research%20the%20internet%2C%20and%20this%20is%20what%20I%20found%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3E%22Unable%20to%20retrieve%20topology%20component%20health%20states.%20this%20may%20be%20because%20the%20admin%20component%20is%20not%20up%20and%20running%22.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EI%20tried%20to%20reset%20the%20search%20index%20and%20I%20prompt%20to%20this%20error%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3E%22No%20system%20manager%20location%20set%2C%20Search%20application%20might%20not%20be%20ready%20yet%22%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E(by%20w3wp.exe%20process)%3C%2FP%3E%3CP%3E------------%3C%2FP%3E%3CP%3E%3CU%3ETopology%20description%3A%3C%2FU%3E%3C%2FP%3E%3CP%3EFront-End%20Server%20(Front-End%20%26amp%3B%20Distributed%20Cache)%26nbsp%3BWindows%20Server%202016%3C%2FP%3E%3CP%3EBack-End%20Server%20(Application%20%26amp%3B%20Search)%20Windows%20Server%202016%3C%2FP%3E%3CP%3ESQL%20Server%202016%3C%2FP%3E%3CP%3E------%3C%2FP%3E%3CP%3EI%20don't%20know%20what%20else%20to%20do%2C%20please%20help%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-833110%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833132%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Server%202019%20-%20Search%20service%20application%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833132%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F401980%22%20target%3D%22_blank%22%3E%40tashtiot%3C%2FA%3E%26nbsp%3BIt's%20a%20very%20common%20error%20and%20you%20need%20to%20try%20a%20lot%20of%20things.%20Please%20follow%20these%20links%20-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F383ad2cd-d9bc-4701-a6e0-c018c66b3ce4%2Funable-to-retrieve-topology-component-health-states-this-may-be-because-the-admin-component-is-not%3Fforum%3Dsharepointsearch%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F383ad2cd-d9bc-4701-a6e0-c018c66b3ce4%2Funable-to-retrieve-topology-component-health-states-this-may-be-because-the-admin-component-is-not%3Fforum%3Dsharepointsearch%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsharepoint.stackexchange.com%2Fquestions%2F178446%2Ferror-unable-to-retrieve-topology-component-health-states-this-may-be-because-t%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsharepoint.stackexchange.com%2Fquestions%2F178446%2Ferror-unable-to-retrieve-topology-component-health-states-this-may-be-because-t%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.sharepointfire.com%2F2015%2F03%2Fsharepoint-unable-to-retrieve-topology-component-health-states%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.sharepointfire.com%2F2015%2F03%2Fsharepoint-unable-to-retrieve-topology-component-health-states%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmanojmittalblogs.blogspot.com%2F2016%2F01%2Funable-to-retrieve-topology-component.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmanojmittalblogs.blogspot.com%2F2016%2F01%2Funable-to-retrieve-topology-component.html%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hey Everyone !

I have been deployed SharePoint Farm

created Web Applications and Host-based Site Collections

Eveything was fine until the Search Service Application stop working.

I tried to analize the issue, track after ULS logs and research the internet, and this is what I found:

"Unable to retrieve topology component health states. this may be because the admin component is not up and running".

I tried to reset the search index and I prompt to this error:

"No system manager location set, Search application might not be ready yet"

(by w3wp.exe process)

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

Topology description:

Front-End Server (Front-End & Distributed Cache) Windows Server 2016

Back-End Server (Application & Search) Windows Server 2016

SQL Server 2016

------

I don't know what else to do, please help :(

1 Reply