Created a new Search service Application

Got a A server and a W server...previously had the components on both servers - now I had to build a new SSA - and I can't change the Search Topology...

On the W server the services regarding Search looks like this:

I got the topology that all components runs on Server A

I would like to add components (index and query) that runs on server W

How to I fix the 'error starting' and when I provision the SSA it just give me the status provisioning continuously - and it takes forever. 

can someone assist?





  • Edited by JmATK Saturday, February 07, 2015 10:01 AM
February 7th, 2015 1:55am

What does the ULS logs say? Is search service and timer service running on those servers?

Free Windows Admin Tool Kit Click here and download it now
February 7th, 2015 7:42pm

can't find any info in the ULS that relates to this 

search host service is status disable ...(started via "service on server" in SP)  - timer service is running

February 7th, 2015 9:58pm

First stop the  search service instance from server W from PS:-

Get-spserviceinstance -server server w

Make a note of the search server service's ID and try to provision it using below PS:-

$ w =Get-spserviceinstance -id 

$w.provision()

Moving search topology is easy.

1) First make a clope of existing topology

2) Add/remove components

3) Apply the clone

Take a look at below article which has all the necessary information

https://technet.microsoft.com/en-us/library/jj862354.aspx

https://altfo.wordpress.com/2013/04/19/move-search-components-to-different-server-in-sharepoint-2013/

Free Windows Admin Tool Kit Click here and download it now
February 7th, 2015 10:17pm


If I try to Provision with the ID listed it shows me : 

Exception calling "Provision" with "0" argument(s): "Attempted to perform an unauthorized operation."

And in the services on server in CA it states: "starting"

- in the windows services on the server W it's status: disabled 

The service account is in the local admin group /wss_admin etc. etc. and my account is farm admin





  • Edited by JmATK Sunday, February 08, 2015 5:21 AM
February 8th, 2015 7:53am

When you call the variable $w do you see search service instance?If not then you haven't stored the search service instance in the variable and If you do then follow below

You will have to stop it by running stop-spserviceinstance -id and then try to provision 

If it still fails then stop it yet again and run below cmd :-

stsadm -o provisionservice -action start -servicename osearch15 -servicetype "Microsoft.Office.Server.Search.Administration.SearchService, Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"

If it still gets stuck at starting then you will have to capture ULS logs in verbose and filter by process powershell and check what is exact error.


Free Windows Admin Tool Kit Click here and download it now
February 8th, 2015 11:08am

I see this (Search related) when I run the Get-ServiceInstance

Role                                  : None
DedicatedWebFrontEndServer            : 
DefaultIndexLocation                  : C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications
IndexLocations                        : {}
Description                           : Index content and serve search queries
ManageLink                            : Microsoft.SharePoint.Administration.SPActionLink
ProvisionLink                         : Microsoft.SharePoint.Administration.SPActionLink
UnprovisionLink                       : Microsoft.SharePoint.Administration.SPActionLink
SystemService                         : False
MinutesBetweenCrawlSchedulingAttempts : 5
CrawlComponents                       : {}
AdminComponents                       : {}
Components                            : {}
RequiresAdministrationService         : True
TypeName                              : SharePoint Server Search
Server                                : SPServer Name=SERVER W
Service                               : SearchService Name=OSearch15
Instance                              : 
Roles                                 : 
Hidden                                : False
CanUpgrade                            : True
IsBackwardsCompatible                 : True
NeedsUpgradeIncludeChildren           : False
NeedsUpgrade                          : False
UpgradeContext                        : Microsoft.SharePoint.Upgrade.SPUpgradeContext
Name                                  : 
DisplayName                           : 
Id                                    : 8a1c24c5-992a-4644-9985-93636bfa4875
Status                                : Provisioning
Parent                                : SPServer Name=SERVER W
Version                               : 4685031
Properties                            : {}
Farm                                  : SPFarm Name=SP_Config
UpgradedPersistedProperties           : {}


TypeName                    : Search Query and Site Settings Service
Server                      : SPServer Name=Server W
Service                     : SearchQueryAndSiteSettingsService
Instance                    : 
Roles                       : 
Hidden                      : False
SystemService               : False
Description                 : 
ManageLink                  : Microsoft.SharePoint.Administration.SPActionLink
ProvisionLink               : Microsoft.SharePoint.Administration.SPActionLink
UnprovisionLink             : Microsoft.SharePoint.Administration.SPActionLink
CanUpgrade                  : True
IsBackwardsCompatible       : True
NeedsUpgradeIncludeChildren : False
NeedsUpgrade                : False
UpgradeContext              : Microsoft.SharePoint.Upgrade.SPUpgradeContext
Name                        : 
DisplayName                 : 
Id                          : b114d5c2-0cc8-4785-9147-8d4b7570d094
Status                      : Online
Parent                      : SPServer Name=SERVER W
Version                     : 3666478
Properties                  : {}
Farm                        : SPFarm Name=SP_Config
UpgradedPersistedProperties : {}

February 8th, 2015 11:40am

the sts command

Provision of service osearch15 failed. Additional information: Attempted to perform an unauthorized operation..
If this is a Web service, IIS must be restarted for the change to take effect.  To restart IIS, open a command prompt window and type "iisreset /noforce"

unauthorized??... hmmm 

Free Windows Admin Tool Kit Click here and download it now
February 8th, 2015 11:57am

By what account are you logged on to the server?

Login to the server with the farm a/c ( Timer service a/c ) >Run shell as admin.

If it still fails then check ULS Logs

 
February 8th, 2015 12:09pm

tried when logged in as the farm (timer job account and with the search service acoount ) 

running the

do {$online = Get-SPEnterpriseSearchServiceInstance -Identity $ssi; Write-Host "Waiting for service: " $online.Status} 
until ($online.Status -eq "Online")

ULS: gets a lot of these....starts with provisioning goes over to disabled...:

Entering BeginProcessing Method of Get-SPEnterpriseSearchServiceInstance. f18f3a51-d65b-4e60-8300-fb2bed4c4cf6

Leaving BeginProcessing Method of Get-SPEnterpriseSearchServiceInstance. f18f3a51-d65b-4e60-8300-fb2bed4c4cf6

Can it be there's some kind of "leftovers" from the previous Search Service Application?

Free Windows Admin Tool Kit Click here and download it now
February 8th, 2015 1:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics