Hi,
I am just setting up a new SharePoint 2013 environment (Windows server 2008 R2 + SQL Server 2008 R2) and I am getting this error message in powershell when I try to save my new search topology: No system manager locations set, search application might not be ready yet. The installation script used to install and create the search service originates from this link: http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=378 and I receive the error message after running $clone.Activate().
ULS is writing this:
05-29-2013 14:57:00.94 mssearch.exe (0x19C0) 0x1A68 SharePoint Server Search Crawler:Content Plugin cd11 Critical Content Plugin can not be initialized - list of CSS addresses is not set. 05-29-2013 14:56:08.27 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration dkd5 High synchronizing search service instance 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:08.27 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration eff0 High synchronizing search data access service instance 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:09.38 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration ajzc7 Medium Cleanup of Orphan Systems in server SR00667 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:09.46 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration agwve Medium Synchronizing legacy admin 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:09.46 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration ai4f1 High Unable to get systemmanagerlocation from db 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:09.46 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration ai84s Medium Skipping legacy admin sync as there is no system manager location set 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:09.46 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration agwvc Medium Skipping Topology Synchronize.The active topology does not have any Components. 8f28209c-5d35-a0cc-7fad-bd7b088335ee 05-29-2013 14:56:09.46 OWSTIMER.EXE (0x09B0) 0x1304 SharePoint Server Search Administration ajnco Medium Cleaning up Orphan nodes in system : 7B4831 8f28209c-5d35-a0cc-7fad-bd7b088335ee
So basically all else is going fine before saving the clone. Application pool is created, search service and it´s proxy is created (the databases are also created in SQL). The clone is after this created and then the components are added.
I have tested with both March and April CU. I use separate accouns for search service, installation and so on. I have tested giving the search application pool account local admin right but didnt make any difference.
Some posts in Internet around this matter is pointing towards there might be 4 missing patches like here: http://blog.steigis.ch/sharepoint/sps2013/search-in-starting-state/ They are all installed on my server.
Search host controller service and SharePoint Server Search are started.
Before creating the service I ran this. I have done this on all my other installations of search to solve the problem with the host service is in "starting" state. Info taken from here: http://mmman.itgroove.net/2012/12/search-host-controller-service-in-starting-state-sharepoint-2013-8/
$acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName
$person = [System.Security.Principal.NTAccount] "Users"
$access = [System.Security.AccessControl.RegistryRights]::FullControl
$inheritance = [System.Security.AccessControl.InheritanceFlags] "ContainerInherit, ObjectInherit"
$propagation = [System.Security.AccessControl.PropagationFlags]::None
$type = [System.Security.AccessControl.AccessControlType]::Allow
$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)
$acl.AddAccessRule($rule)
Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl
$sh = Get-SPServiceInstance | ? {$_.TypeName -eq "Search Host Controller Service"}After this I do a server restart and continue with creating the search service and its components.
Any ideas?