Search Instance Stuck at "Starting" in WFE

Question

My Search Instance Stuck in "Starting" in my WFE.But its "Started" in my App Server.

I Just followed this article SharePoint 2013 Search Configuration PowerShell Script to configure my search topology...

anything in event log or uls log? what is your search topology? — Waqas Sarwar MVP, Commented Sep 22, 2016 at 17:01
I just followed the above URL(1WFE and 1 Apps Server) to configure search topology in my 3 tier farm and i did't find any error meesage in the Event log — user52682, Commented Sep 22, 2016 at 17:24
Without log details, we cannot help. Do you find any error in uls? — coc2coc, Commented Sep 22, 2016 at 17:43

Benny Skogberg · Accepted Answer · 2016-09-22 18:17:51Z

1

Check permission on

In 9 out of 10 cases, there is something wrong with permission.

answered Sep 22, 2016 at 18:17

Benny Skogberg♦

25.5k12 gold badges68 silver badges163 bronze badges

Add a comment |

Paul Lucas · Accepted Answer · 2016-09-23 03:33:11Z

0

In addition to Benny's answer, check the SharePoint Timer Service and SharePoint Admin Services are running on the WFE. Possibly even restart them.

answered Sep 23, 2016 at 3:33

Paul Lucas

4,2811 gold badge17 silver badges18 bronze badges

Now,i able to stop the search instance in my WFE.However i would like know few things 1.Do the SharePoint Timer service should run on same service accounts which is running in the Apps server?
– user52682
Commented Sep 23, 2016 at 15:47
The SharePoint Timer Service should be running as the farm account on all servers.
– Paul Lucas
Commented Sep 25, 2016 at 1:51
FYI the farm account is used to run timer jobs, of which should be a separate account to the application pools.
– James Randal
Commented Jul 14, 2018 at 4:58

Add a comment |

2 Answers 2