Why does SQL Browser service get disabled?

Question

I am struggling with intermittent problems with a software installation package that installs our product (written using InstallShield/InstallScript). During the process of the installation, we restart the SQL Browser Service. Most of the time this works fine. But occasionally - and I have not worked out how to reproduce this predictably - the service fails to restart, and I find in my "Services" manager that the service status is set to "Disabled".

Any ideas what would be causing the service to be disabled, and how to prevent it from happening? And what to do when sql server browser is disabled?

Akansha Chawla · Accepted Answer

When it is get disabled, go to Control Panel->Administrative Tools->Services, and look for the SQL Server Agent. Right-click, and select Properties From the Startup Type dropdown, change from Disabled to Automatic. Make sure that you run the SQL Server Configuration Manager snap-in as Administrator if UAC is enabled. The SQL Server Browser Service is installed often in Disabled state (and this is what my SQL Slammer link is about, it gives the history why the Browser service is preffered to be disabled unless required). It is only required for named instances or instances listening on non-default ports. Your application installer should only restart the Browser service if needed, and certainly should check for a disabled service and ask an administrator permission to enable the service (ie. display a confirmation dialog) before messing with it.

Why does SQL Browser service get disabled?

About this question

Your answer

1 Answer

More SQL Server discussions

Learn & Explore

SQL Server Tutorials

SQL Server Interview Q&A

Latest SQL Server Blogs

Want answers to more SQL Server questions?

Stay in the loop — it’s free

You’re on the list!