January 7, 2010 at 8:33 am
Here’s a nice puzzle
Just a few day’s ago, one of our sql cluster nodes had a memory problem. Fixed it and reboot this server. Switched the sql instances again…. But there was no way of connecting to the databases.
Both servers are Microsoft windows 2003 r2 Enterprise x64 service Pack 2, with Microsoft SQL 2005 x64 SP 3
We did some nice detective work and found that the sqlbrowser service did not run, rebooting or restarting did not work.
We found that for every instance (database) there are registry entry’s like :
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER.
When we renamed the MSSQLSERVER key to MSSQLSERVER_x the sqlbrowser service starts.
(ok found this hint on the net and looking at the service that starts "C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe")
So this was strange. Why is there a wow6432 registry? It points to 32 bit programs on 64 bit OS. So probably someone made a big mistake.
So one thinks “let’s keep the registry entry’s and continue life” but when switching an instance a new key MSSQLSERVER is created and restarting the SQLBROWSER fails.
Clearly this has to be solved but how? How can one remove the 32 bit coding and is the SQLbrowser in a normal 64 bit sql server also 32 bit??
Tips?
April 1, 2012 at 6:13 am
Checked the same under my 64 bit environment where SQL Browser service is in x86 Progra~1 & its advance properties say Running under 64 bit OS as NO.
Is it that SQL Browser is always a 32 bit app no matter the SQL Install type selected ?
Looking at the following key, does it means SQL Browser si a component from SQL 9.0 ?
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\SQL Browser
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply