SQLBrowser.exe won't start

Question

SQLBrowser.exe won't start

Jeff Moden

SSC Guru

Points: 1004409
More actions
July 29, 2009 at 6:35 am

#140189

I'm running 32 bit SQL Server (Developer's Edition sp2) on a 32 bit Windows XP (sp2) machine. Apparently my computer went through an automatic "windows update" last night because my machine had been rebooted. When I logged in and SQL Server began it's startup sequence, McAfee warned me about changes to SQLBrowser.exe and I rejected them because I didn't know what the heck was happening and didn't want to take a chance especially since McAfee said it didn't know what was happening.
Now, SQL Server 2005 won't start. I checked Services and SQLBrowser.exe says its "starting" but never finishes.
Does anyone know a fix for this or am I going to have to reinstall SQL Server 2005?
p.s. I've turned of automatic updates. This is a huge pain.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

SQLEgan SSC Veteran Points: 204 More actions · Answer 1

You could check the windows update log(%windir%\windowsupdate.log), see which updates where installed which would have affected the SQL browser service and then removing and re-applying the update or simply reinstalling the update

Jeff Moden SSC Guru Points: 1004409 More actions · Answer 2

Thanks, Paul... I tried the reinstall of the update. No joy. Fortunately, this isn't a production system and I've really not lost anything important. Guess I'll just have to suffer through a reinstall.

Thanks for answering.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)