SQL Server 2000 Failover Cluster upgrade to SQL Server 2005

[Mark D Powell]

I attempted to upgrade my SQL Server 2000 Enterprise Edition (32 bit)
to SQL Severer 2005 EE 32 bit and while the prereqs passed the
installer will not let me select the version 8.00.x (2000 SP4)
database that it finds on the server.

When I ckeck the install details it tells me that
"Your upgrade is blocked becuase of cluster upgrade rules"

I have tried searching the MS site but none of the entries I found
appear to apply.

Any ideas?

-- Mark D Powell --

[Erland Sommarskog]

Mark D Powell (Ma*********@eds.com) writes:

I attempted to upgrade my SQL Server 2000 Enterprise Edition (32 bit)
to SQL Severer 2005 EE 32 bit and while the prereqs passed the
installer will not let me select the version 8.00.x (2000 SP4)
database that it finds on the server.

When I ckeck the install details it tells me that
"Your upgrade is blocked becuase of cluster upgrade rules"

I have tried searching the MS site but none of the entries I found
appear to apply.

Any ideas?

Exactly when do you get this error? And do you have a cluster in the first
place?

I have not run that many upgrades (if any at all) to SQL 2005, but do you
really select which *database* to upgrade? The upgrade is per instance,
as far as I know.

In any case, it may be simpler to install a new server instance rather
than upgrading, not the least on a cluster.

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

[Mark D Powell]

On Sep 6, 5:37*am, Erland Sommarskog <[e-mail]:

Mark D Powell ([e-mail]) writes:

I attempted to upgrade my SQL Server 2000 Enterprise Edition (32 bit)
to SQL Severer 2005 EE 32 bit and while the prereqs passed the
installer will not let me select the version 8.00.x (2000 SP4)
database that it finds on the server.

When I ckeck the install details it tells me that
"Your upgrade is blocked becuase of cluster upgrade rules"

I have tried searching the MS site but none of the entries I found
appear to apply.

Any ideas?

Exactly when do you get this error? And do you have a cluster in the first
place?

I have not run that many upgrades (if any at all) to SQL 2005, but do you
really select which *database* to upgrade? The upgrade is per instance,
as far as I know.

In any case, it may be simpler to install a new server instance rather
than upgrading, not the least on a cluster.

--
Erland Sommarskog, SQL Server MVP, [e-mail]

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:http://www.microsoft.com/sql/prodinf...ons/books.mspx

I figured the probme out. I apparently missed the check box where you
have to tell it you are on a cluster even though when it runs the pre-
install checks it finds both nodes and runs the checks on them.

I have a new problem after performing the upgrade, applying SP2, and
then hot fix pack 7 in that the SQL Agent will no longer run.
Searching on SQL Server Agent (Agent XP Disabled) found me 3 potential
fixes.

1- use sp_configure to enable routines
2- http://technet.microsoft.com/en-us/l.../ms190730.aspx --
verify ID has privilege to page lock
3- http://support.microsoft.com/kb/943525
-- change Id to non-domain administrator Id

Item 1 did not fix the issue, item 2 was already true, so item 3.
Jobs run but now 1/3 of my jobs which all obtain data from Oracle are
failing with an invalid user/password. The link connects to Oracle
with a different Id depending on who uses it but all the jobs are
being ran by the Id that used to run the agent. I do not know if that
is a change from the upgrade or if this was always true. I manually
tested the id/passwords from the server but what passwords are in use
in the link are hidden. Still it should not have changed since it was
working prior to the upgrade.

-- Mark D Powell --

[Mark D Powell]

On Sep 6, 3:16*pm, Mark D Powell <[e-mail]:

On Sep 6, 5:37*am, Erland Sommarskog <[e-mail]:

Mark D Powell ([e-mail]) writes:

I attempted to upgrade my SQL Server 2000 Enterprise Edition (32 bit)
to SQL Severer 2005 EE 32 bit and while the prereqs passed the
installer will not let me select the version 8.00.x (2000 SP4)
database that it finds on the server.

When I ckeck the install details it tells me that
"Your upgrade is blocked becuase of cluster upgrade rules"

I have tried searching the MS site but none of the entries I found
appear to apply.

Any ideas?

Exactly when do you get this error? And do you have a cluster in the first
place?

I have not run that many upgrades (if any at all) to SQL 2005, but do you
really select which *database* to upgrade? The upgrade is per instance,
as far as I know.

In any case, it may be simpler to install a new server instance rather
than upgrading, not the least on a cluster.

--
Erland Sommarskog, SQL Server MVP, [e-mail]

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:http://www.microsoft.com/sql/prodinf...ons/books.mspx

I figured the probme out. *I apparently missed the check box where you
have to tell it you are on a cluster even though when it runs the pre-
install checks it finds both nodes and runs the checks on them.

I have a new problem after performing the upgrade, applying SP2, and
then hot fix pack 7 in that the SQL Agent will no longer run.
Searching on SQL Server Agent (Agent XP Disabled) found me 3 potential
fixes.

1- * use sp_configure to enable routines
2-http://technet.microsoft.com/en-us/library/ms190730.aspx* * *--
verify ID has privilege to page lock
3-http://support.microsoft.com/kb/943525
-- *change Id to non-domain administrator Id

Item 1 did not fix the issue, item 2 was already true, so item 3.
Jobs run but now 1/3 of my jobs which all obtain data from Oracle are
failing with an invalid user/password. *The link connects to Oracle
with a different Id depending on who uses it but all the jobs are
being ran by the Id that used to run the agent. *I do not know if that
is a change from the upgrade or if this was always true. *I manually
tested the id/passwords from the server but what passwords are in use
in the link are hidden. *Still it should not have changed since it was
working prior to the upgrade.

-- Mark D Powell --- Hide quoted text -

- Show quoted text -

To get the sqlagent to run we changed the connection to run as a local
system account instead of a domain user. The jobs that reference the
link to Oracle would then fail.

Then I dropped and re-created the link to Oracle. The jobs then
resumed working,

-- Mark D Powell --