So I have been up and down this issue for the past couple of days and was wondering if there is a more obvious explanation to my problem.
Environment: Windows Server 2003 SP1, SQL Server 2005, SharePoint V2 installed as well.
All other SQL services run well, this includes analysis, reporting, etc. But I cannot start the SQL Browser service - it starts and immediately stops. It poops out two rather unhelpful messages into the event log, which I will post below.
Error 1:
==========================
==========
==========
======
Event Type: Error
Event Source: SQLBrowser
Event Category: None
Event ID: 7
Date: 8/16/2006
Time: 9:56:30 AM
User: N/A
Computer: DWSANDBOX
Description:
The SQLBrowser service port is unavailable for listening, or invalid.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 62 09 00 00 b...
Error 2:
==========================
==========
==========
======
Event Type: Error
Event Source: SQLBrowser
Event Category: None
Event ID: 10
Date: 8/16/2006
Time: 9:56:30 AM
User: N/A
Computer: DWSANDBOX
Description:
The SQLBrowser service was unable to establish SQL instance and connectivity discovery.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 62 09 00 00 b...
Stuff I have tried already:
I used PortQryV2 to ensure that the TCP port used by SQL Browser wasn't already being listened on (1433 - Returned "Not Listening").
I checked firewall settings - Windows Firewall is disabled.
I used PortQryV2 to ensure the UDP port (1434) used by SQL Browser wasn't already being listened on.
I have reinstalled SQL server from scratch.
I hope someone has an easy answer to this. It is the last step on the road to Team Foundation Server!!
Thanks,
-SM
Start Free Trial