I had this problem as well and just resolved it with Microsoft support. My
Environment:

SQL 2005 x64 2 node cluster

Upon trying to install SP2, Failed Server Engine to update and remained at SP1

When I looked more closely to the passive node logs, it stated that it was
not able to START SQLBROWSER.

I had this problem for a while and would from time to time poke at the SQL
Browser to fix the problem, but no luck until today.

It turned out that SQL 2005 x32 was accidentally installed and then
uninstalled before x64 was loaded on the cluster previous to my working here,
and it left the Registry stubs for x32 SQL 2005. SQLBrowser became confused
because it was looking first in the x32 location of the registry for SQL
Server information and only found the stubs, with no data in the registry.

Here are the notes from my technician who solved the issue:

-----------------
<Old Case>

We found the issue appears to be isolated to x64 boxes as we found some left
over registry keys from what appears to have been a 32-bit install that did
not get
completely uninstalled. The current sql server install was 64-bit.

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Microsoft SQL
Server\MSSQL.1\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.1\MSSQLServer

TO

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

Try to start SQL Browser, and it works

Problem solved. You may want to clean out the registry by deleting that key.
I chose not to until I can verify that all works as expected.

I had this problem as well and just resolved it with Microsoft support. My
Environment:

SQL 2005 x64 2 node cluster

Upon trying to install SP2, Failed Server Engine to update and remained at SP1

When I looked more closely to the passive node logs, it stated that it was
not able to START SQLBROWSER.

I had this problem for a while and would from time to time poke at the SQL
Browser to fix the problem, but no luck until today.

It turned out that SQL 2005 x32 was accidentally installed and then
uninstalled before x64 was loaded on the cluster previous to my working here,
and it left the Registry stubs for x32 SQL 2005. SQLBrowser became confused
because it was looking first in the x32 location of the registry for SQL
Server information and only found the stubs, with no data in the registry.

Here are the notes from my technician who solved the issue:

-----------------
<Old Case>

We found the issue appears to be isolated to x64 boxes as we found some left
over registry keys from what appears to have been a 32-bit install that did
not get
completely uninstalled. The current sql server install was 64-bit.

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Microsoft SQL
Server\MSSQL.1\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.1\MSSQLServer

TO

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

Try to start SQL Browser, and it works

Problem solved. You may want to clean out the registry by deleting that key.
I chose not to until I can verify that all works as expected.

I had this problem as well and just resolved it with Microsoft support. My
Environment:

SQL 2005 x64 2 node cluster

Upon trying to install SP2, Failed Server Engine to update and remained at SP1

When I looked more closely to the passive node logs, it stated that it was
not able to START SQLBROWSER.

I had this problem for a while and would from time to time poke at the SQL
Browser to fix the problem, but no luck until today.

It turned out that SQL 2005 x32 was accidentally installed and then
uninstalled before x64 was loaded on the cluster previous to my working here,
and it left the Registry stubs for x32 SQL 2005. SQLBrowser became confused
because it was looking first in the x32 location of the registry for SQL
Server information and only found the stubs, with no data in the registry.

Here are the notes from my technician who solved the issue:

-----------------
<Old Case>

We found the issue appears to be isolated to x64 boxes as we found some left
over registry keys from what appears to have been a 32-bit install that did
not get
completely uninstalled. The current sql server install was 64-bit.

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Microsoft SQL
Server\MSSQL.1\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.1\MSSQLServer

TO

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

Try to start SQL Browser, and it works

Problem solved. You may want to clean out the registry by deleting that key.
I chose not to until I can verify that all works as expected.

I had this problem as well and just resolved it with Microsoft support. My
Environment:

SQL 2005 x64 2 node cluster

Upon trying to install SP2, Failed Server Engine to update and remained at SP1

When I looked more closely to the passive node logs, it stated that it was
not able to START SQLBROWSER.

I had this problem for a while and would from time to time poke at the SQL
Browser to fix the problem, but no luck until today.

It turned out that SQL 2005 x32 was accidentally installed and then
uninstalled before x64 was loaded on the cluster previous to my working here,
and it left the Registry stubs for x32 SQL 2005. SQLBrowser became confused
because it was looking first in the x32 location of the registry for SQL
Server information and only found the stubs, with no data in the registry.

Here are the notes from my technician who solved the issue:

-----------------
<Old Case>

We found the issue appears to be isolated to x64 boxes as we found some left
over registry keys from what appears to have been a 32-bit install that did
not get
completely uninstalled. The current sql server install was 64-bit.

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Microsoft SQL
Server\MSSQL.1\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.1\MSSQLServer

TO

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

Try to start SQL Browser, and it works

Problem solved. You may want to clean out the registry by deleting that key.
I chose not to until I can verify that all works as expected.

I had this problem as well and just resolved it with Microsoft support. My
Environment:

SQL 2005 x64 2 node cluster

Upon trying to install SP2, Failed Server Engine to update and remained at SP1

When I looked more closely to the passive node logs, it stated that it was
not able to START SQLBROWSER.

I had this problem for a while and would from time to time poke at the SQL
Browser to fix the problem, but no luck until today.

It turned out that SQL 2005 x32 was accidentally installed and then
uninstalled before x64 was loaded on the cluster previous to my working here,
and it left the Registry stubs for x32 SQL 2005. SQLBrowser became confused
because it was looking first in the x32 location of the registry for SQL
Server information and only found the stubs, with no data in the registry.

Here are the notes from my technician who solved the issue:

-----------------
<Old Case>

We found the issue appears to be isolated to x64 boxes as we found some left
over registry keys from what appears to have been a 32-bit install that did
not get
completely uninstalled. The current sql server install was 64-bit.

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Microsoft SQL
Server\MSSQL.1\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.1\MSSQLServer

TO

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

Try to start SQL Browser, and it works

Problem solved. You may want to clean out the registry by deleting that key.
I chose not to until I can verify that all works as expected.

I had this problem as well and just resolved it with Microsoft support. My
Environment:

SQL 2005 x64 2 node cluster

Upon trying to install SP2, Failed Server Engine to update and remained at SP1

When I looked more closely to the passive node logs, it stated that it was
not able to START SQLBROWSER.

I had this problem for a while and would from time to time poke at the SQL
Browser to fix the problem, but no luck until today.

It turned out that SQL 2005 x32 was accidentally installed and then
uninstalled before x64 was loaded on the cluster previous to my working here,
and it left the Registry stubs for x32 SQL 2005. SQLBrowser became confused
because it was looking first in the x32 location of the registry for SQL
Server information and only found the stubs, with no data in the registry.

Here are the notes from my technician who solved the issue:

-----------------
<Old Case>

We found the issue appears to be isolated to x64 boxes as we found some left
over registry keys from what appears to have been a 32-bit install that did
not get
completely uninstalled. The current sql server install was 64-bit.

The problematic registry key was:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Microsoft SQL
Server\MSSQL.1\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.1\MSSQLServer

TO

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

Try to start SQL Browser, and it works

Problem solved. You may want to clean out the registry by deleting that key.
I chose not to until I can verify that all works as expected.