Exchange Search Indexer service failed to stop

Exchange Search IndexerHi,
 I have SBS2011/Exchange 2010 and whenever I tried to stop Exchange Search Indexer service in Services.msc, it fails with "Error 1053" and status is stuck in "Stopping". So I run:
(1) sc queryex MSExchangeSearch - to obtain processor ID
(2) taskkill /f /pid 8580 - to kill the processor
Then the status changes back to "Started".
What is causing this problem? How do I fix this?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sounds like the recovery is starting it automatically because it detected a failure.
What are the settings on the recovery tab in the Exchange Search Indexer service?
sgleeAuthor Commented:
recovery tab in the Exchange Search Indexer serviceHere is recovery tab in the Exchange Search Indexer service.
as a test, set the first failure to 'Take no action'
Are you then able to stop/kill the service?

If not, are there any dependencies ?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

sgleeAuthor Commented:
Exchange Search Indexer Service - with Take no actionYes it changed the status to "Stopping".
I killed the processor and I manually started it successfully.
sgleeAuthor Commented:
How can I research the cause of this problem?
Pushpakumara MahagamageVPCommented:
Hi Sglee,

Please check event log for administrator events, there should be errors logged, and Do you have enough resources on your exchange server,  How is the CPU RAM Disk read and write. Upgrade/correct the issue if there is high resources usage. and other question, check whether you have applied all service packs and updates.

and try to do same at late night [when no users connected]
has not been closed yet, after a long time.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.