Re: Upgrade from SQL 2000 to SQL 2005 Problem in Active/Active Cluster Environment

Well moving all VMs over to one node in the cluster didn't seem to be
the solution. Here's the Summary.txt file that was returned after the
install failed.

Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise
Edition Service Pack 1 (Build 3790)
Time : Sat Aug 04 22:16:55 2007

NODE2 : Microsoft Internet Information Services (IIS) is either not
installed or is disabled. IIS is required by some SQL Server
features. Without IIS, some SQL Server features will not be available
for installation. To install all SQL Server features, install IIS from
Add or Remove Programs in Control Panel or enable the IIS service
through the Control Panel if it is already installed, and then run SQL
Server Setup again. For a list of features that depend on IIS, see
Features Supported by Editions of SQL Server in Books Online.
NODE2 : To change an existing instance of Microsoft SQL Server 2005 to
a different edition of SQL Server 2005, you must run SQL Server 2005
Setup from the command prompt and include the SKUUPGRADE=1 parameter.
NODE2 : No nodes to operate on were specified by the user. Please run
setup and specify the nodes to install on.


NOTE: NODE2 is not the node in the cluster that I'm logged into or the
node the SQL instance I want to upgrade is on. I'm logged into NODE1
as that's where the instance is. Additionally I moved all the VMs to
NODE1 just to make sure this wasn't the reason for the problem after
trying the install when some SQL Instances were on NODE1 and others
were on NODE2.

Again, if anyone has any idea why this is not working or any
suggestions for me to try, please pass them along.

Thanks,

John


On Aug 3, 5:00 pm, John <John.Eisbre...@xxxxxxxxx> wrote:
I'm running into a problem upgrading a SQL 2000 instance in an Active/
Active Cluster Environment to SQL 2005. This is not the first time
the cluster has been upgraded to 2005. It currently has 8 instances
of SQL running on it, however only 2 are SQL 2005. The previous
upgrade happened before I started here, so there isn't any
documentation for me to reference, and I haven't found any
documentation online that pertains to this situation. When I click
through the upgrade process one step is not consistent with the
installation instructions I've found on MSDN.

I do not encounter a screen that prompts me to input a Virtual SQL
Server Name. I'm assuming this is due to my situation being an
upgrade and not a new install.

Additionally when I try to finish the installation, I receive the
following error:

TITLE: Microsoft SQL Server 2005 Setup
------------------------------

SQL Server Setup did not install SQL Server on one or more remote
nodes of your failover cluster. To continue, log off of all remote
nodes and then run Setup again from the primary node.

For help, click:http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Se...

------------------------------
BUTTONS:

OK
------------------------------

I've tried performing this update by logging into the VM, the current
node the VM is on (this is also the node where the cluster IP VM is
located), and the failover node the VM isn't on. All of which result
in the same lack of entering a Virtual SQL Server Name step and the
failure noted above. The only thing I've found online is to failover
all VMs to one node in the cluster and then perform the upgrade
process. I will try this later this weekend during off hours to
ensure that no one experiences a dropped connection to the other
instances on the cluster.

If anyone has any suggestions or experience with this, please pass
that information on.

Thanks,

John


.