Real quick one (as per title):
Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchTopology |? {$_.State -eq "Inactive"} |% { Remove-SPEnterpriseSearchTopology -Identity $_ -Confirm:$false};
SharePoint - Warts and All
Tuesday, July 24, 2012SharePoint 2013 Search – Removing Inactive Search Topologies with PowershellReal quick one (as per title): Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchTopology |? {$_.State -eq "Inactive"} |% { Remove-SPEnterpriseSearchTopology -Identity $_ -Confirm:$false};
SharePoint 2013 – Unable to retrieve topology component health states…
I’ve just started playing with the SharePoint 2013 preview – I had an issue provisioning the search service application in that the Search Service Application Administrative interface in Central Administration was reporting a “Unable to retrieve topology component health states. This may be because the admin component is not up and running.”
At this stage, it’s a single server farm. It was a fresh build of Server 2008 R2 SP1 and the server is not a domain controller or hosting SQL. Initially I did miss a couple of additional hot fixes required after the pre-requisite installer (see step 6 in this article or grab them below)
After installing these hot fixes, i was still getting the same issue… I managed to resolve it by simply running windows update and installing all patches/hotfixes reported as critical. Once this had been done (and a reboot or two later) the problem was resolved!
The updates in installed are below (so it’s one or more of them?)
Subscribe to:
Posts (Atom)
|