none
Unable to retrieve topology component health states

    Question

  • I've been fighting with this error for almost a day now. Very frustrating

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

    I've tried most of the MSDN Searches Fixes but still no luck....

    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/newthread?category=sharepoint&forum=

    http://pointsforsharing.com/Lists/Posts/Post.aspx?ID=5#searchapp

    and even this

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/50acc2b8-dd56-4d5a-a660-dffa325ef807/sharepoint-2013-search-not-provisioning-correctly

    Tried all of those and no luck, in addition I even try adding the search service app via the config wizard.

    No luck at all.

    Kindly please advice on any other methods ? Thanks in advance.


    AJ MCTS: SP 2010 Configuration MCSA: Windows 7 If you find this post useful kindly please mark it as an answer :) TY

    Thursday, August 22, 2013 7:32 PM

Answers

  • Wow, so after almost trying all the google and MSDN searches I made non of them work...

    How I fixed it ? Repair SharePoint under Control Panel... I can't believe why I didn't do this first


    AJ MCTS: SP 2010 Configuration MCSA: Windows 7 If you find this post useful kindly please mark it as an answer :) TY

    • Marked as answer by itsAboutSp Friday, August 23, 2013 1:24 PM
    Friday, August 23, 2013 1:23 PM

All replies

  • Did you tweak anything in memory for node runner process? I did same thing and battled it for 3 days. 

    sachin

    Thursday, August 22, 2013 7:43 PM
  • I did put it to 50 and then put it back to the default "0" and still no luck, any suggestions ?

    AJ MCTS: SP 2010 Configuration MCSA: Windows 7 If you find this post useful kindly please mark it as an answer :) TY

    Thursday, August 22, 2013 7:56 PM
  • Wow, so after almost trying all the google and MSDN searches I made non of them work...

    How I fixed it ? Repair SharePoint under Control Panel... I can't believe why I didn't do this first


    AJ MCTS: SP 2010 Configuration MCSA: Windows 7 If you find this post useful kindly please mark it as an answer :) TY

    • Marked as answer by itsAboutSp Friday, August 23, 2013 1:24 PM
    Friday, August 23, 2013 1:23 PM
  • Running repair is a new one for me. I have always avoiding this error by doing the following.

    1. Start with a fresh Windows install
    2. Run windows update until there are no more updates - this should only be after 3 or 4 reboots and update downloads
    3. Install the 4 infamous missing prerequisites http://www.dontpapanic.com/blog/?p=256
    4. Install SharePoint

    *** Also note that I didn't have a lot of luck having the host controller windows service and the search windows service running as different accounts - Make them the same ***


    Please mark my response as an answer if appropriate.
    Learn.SharePoint.com


    Friday, August 23, 2013 1:36 PM
  • I got the same error :

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

    restarting search servers solved my problem.


    Ayman Saleh

    • Proposed as answer by EricHerlitz Saturday, December 21, 2013 3:33 PM
    Sunday, December 15, 2013 10:11 AM
  • here is one more scenario that I faced for the same error message...thought might be useful to someone
    http://aseempandit.wordpress.com/2013/12/24/unable-to-retrieve-the-search-application-topology/

    Aseem Pandit ========== http://www.agreeya.com http://aseempandit.wordpress.com/

    Tuesday, December 24, 2013 3:20 AM
  • I just rebooted the server, removed the Search Service Application and installed it again, and now it works - without errors!

    I have used (twice) the following script to provision the Search Service:

    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=378

    Best regards,


    Tarcísio Gambin | MCP, MCT, MCTS, MCITP, ITILv3
    Você já viu seus logs hoje? | www.tarcisiogambin.net

    Wednesday, January 08, 2014 4:39 PM
  • Guys - I ran into this issue and it took almost a weeks time to fix without reinstalling of SP 2013, but i had to recreate search application multiple times though the problem didn't fixed.  Finally using ULS log viewer i noticed that my SharePoint Search Host Controller service / application was running with a different service account, after changing the service account to the same account used for search service account fixed the problem and all issues fixed within minutes.
    • Proposed as answer by NabeelSalie Monday, June 30, 2014 11:04 AM
    Tuesday, March 18, 2014 10:38 AM
  • When I tried running the repair, I got the following error:  "Microsoft SharePoint 2013 configuration did not complete successfuly."  Error 1731. *in some other language besides english* Microsoft Server Proof (Russian) 2013...."

    Any suggestions?

    Thanks

    Kim


    Kim.Williams

    Wednesday, March 19, 2014 1:49 PM
  • Ensuring that the Search Host Controller Service is running was the key to resolving this issue for me.

    The Search Host Controller Service requires that the Net.TCP Port Sharing Service, Net.TCP Listener Adapter service, and AppFabric Caching Service be running to start up successfully, as well.


    Friday, August 05, 2016 9:30 AM