Link to home
Start Free TrialLog in
Avatar of it-support-at
it-support-atFlag for Austria

asked on

SQL Browser Service won't start

Hi:

I have issue starting SQL Server Browser service on a SQL 2k5 Win2003 x64 machine. when I start it from the services applet in control panel, I get the following error message:

The SQL Server Browser service on Local computer started and then stopped.

I tried starting it from the surface area configuration tool as well but could not start. I also tried to start sql browser from the command prompt using the sqlbrowser.exe -c. I get the following message:

C:\Program Files\Microsoft SQL Server\90\Shared>sqlbrowser.exe -c
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.

I found the following workaround working for me, but just temporary.

==========WORKAROUND START===========

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL
Server\MSSQL.4\MSSQLServer

The Wow6432Node part of the registry should be only for 32 bit applications. This key was empty but the mere presence of the key confused the sqlbrowswer
service since it was listed as mssql.1 as was the correctly installed 64-bit instance.

Precise resolution would be to remove the above registry key (assuming there is no 32 bit install on the box).

---------------
to resolve:

Change current Registry key name

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL
Server\MSSQL.4\MSSQLServer

TO

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL
Server\MSSQL.4\MSSQLServer_x

==========WORKAROUND END===========

This workaround works but each time the node is restarted these entries are rebuilt and the issues persist again. Do we know what application creates these entries and how this can be fixed permanently.. This would be helpful to understand what's going wrong and how we could fix it too permanently.

Any help is really appreciated.

Thanks

Avatar of Raja Jegan R
Raja Jegan R
Flag of India image

This should help you out in your proper configurations:

http://msdn.microsoft.com/en-us/library/ms143293(SQL.90).aspx
Avatar of it-support-at

ASKER

There was never a 32bit SQL installed on this cluster. That is the difference from the workaround.
The environment did run without problem for more then 2 years ...
If it was working without problems for the last 2 years then what is the recent configuration change done to the system like any one of the below:

1. Change is host name or system name
2. Change in user accounts of any services involved.
3. Password reset or expired for any of the accounts involved.
4. IIS reset or changes done.
5. Or any other recent configurations to the system( which you are aware in that machine).
ASKER CERTIFIED SOLUTION
Avatar of it-support-at
it-support-at
Flag of Austria image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial