unable to start SQLBrowser | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

unable to start SQLBrowser

Hi all, Have a sql 2005 x64 sp2 two node a/p cluster setup.
On both nodes it’s not possible to start sqlbrowser service.
Compared registry and configuration to a 2nd equal system found no differences 🙁
netstat showed no usage of port 1434. In eventlog I get:
Warning: The configuration of the SQL instance MSSQLServer is not valid.
Warning: The configuration of the SQL instance MSSQLSERVER is not valid.
Error: The SQLBrowser service was unable to establish SQL instance and connectivity discovery. Data: 0000: 08 00 00 00
Info: The SQLBrowser is enabling SQL instance and connectivity discovery support.
Warning: The configuration of the SQL instance MSSQLServer is not valid.
Info: The SQLBrowser service has started.
Info: The SQLBrowser service has shutdown. I tried to start sqlbroswer.exe manualy (sqlbrowser.exe -c) and getting the following output: SQLBrowser: starting up in console mode
SQLBrowser: starting up SSRP redirection service
SQLBrowser is successfully listening on 0.0.0.0[1434]
SQLBrowser: failed starting SSRP redirection services — shutting down. Any help is highly appreciated.
TIA
acki

Check SQL Server service account & cluster admin account has local admin prvileges on both the nodes. KBAhttp://support.microsoft.com/kb/912397 fyi. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Satya,
Adding service account to local domain does not help.
As mentioned all params under
SoftwareMicrosoftMicrosoft SQL ServerMSSQL.xMSSQLSERVER looks equal to another system (I do not need to correct somthing there)

I guess this is due SQLServr.exe is already started and using same port, try going to control panel Services and stop all SQL Server services you see, then start SQL Browser. Once SQL Browser loads up it will automatically disable the other SQL Server services from binding to UDP 1434. Then you can restart the other SQL Server services. Look in Services for things like MSSQL$<Something> these are SQL Server instances. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Satya,
Actualy I’m on the inactive node.
Will say no sql server service running on passive node.
netstat shows no other prog listening on port 1434
ON Inactive node the services will be disabled by default as it is active/passive setup, so you are trying to confuse the cluster by starting the services on unrelevant node. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
Satya,
I do not agree.
SQLBroswer server is not a cluster resource. And therefor it is not stopped on the inactive node. He’s running on all nodes no matter if active or not.
(At least that’s what I saw on several a/p setups here).
It just happened to me last week when installing Cumulative Update #4 on SQL 2005 64-bit
Here is a temporal workaround modifying registry key
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMicrosoft SQL
ServerMSSQL.1MSSQLServer
You can whether delete it or change the name.

This has been fixed on that CU4 SQL 2005 SP2 and your workaround needs a thorough testing too.

]]>