I have an intermittent problem 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 happening?

  • SQL Slammer fallout. Commented May 28, 2012 at 9:41
  • @RemusRusanu - on what basis do you think this might be connected to SQL Slammer? The symptoms seem totally unrelated, and it's inconsistent. We have none of the symptoms described, and even if we had viruses on our computers, one might at least expect the behavior to be consistent, no?
    – Shaul Behr
    Commented May 28, 2012 at 9:45
  • @ShaulBehr Because disabling SQL Browser would have prevented a machine from being infected by SQL Slammer.
    – StuartQ
    Commented Oct 30, 2015 at 19:11

1 Answer 1


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.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.