Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Setup / June 2005

Tip: Looking for answers? Try searching our database.

SP4 install problem on Win2003Ent-cluster when adding new node

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bearface@newsgroup.nospam - 25 Jun 2005 16:15 GMT
We have a Windows 2003 Ent edition two node cluster running SQL 2000 SP4
happily, we are adding a new pair of bigger/better servers to the cluster
with the intent of retiring the existing nodes once we trust the new ones.

Built the new server, joined it to the cluster, installed SQL Ent without
issues. Tried to install SP4 and after asking for password for the SQL
Services accounts the install breaks complaining that it cannot verify/set
the logon as a service priviledge for the service account. I verified that
that the priviledge is already in place and found all google references to
the error message occuring and made sure all those priviledges were in
place. The setup still fails. The service account has been promoted to
Domain Admin and the setup still fails. I even tried logging on as that user
and running SP4 setup under that account, still doesn't work.Since I had
been working for 19 hours straight I tried installing SP3 and it worked.
Now the SP4 setup fails differently, it now fails right after I tell it the
virtual server. It says "All cluster disks available to this virtual server
are owned by other node(s)."
I do not see anyway around this problem now, I know I cannot fail the
virtual machine onto the SP3 node from a SP4 node, so how am I going to get
through this?

Any help would be appreciated, we have a big spike in load coming on Monday
and we are scrambling to get these new servers into play in time.
Michael Cheng [MSFT] - 27 Jun 2005 07:26 GMT
Hi,

Welcome to use MSDN Managed Newsgroup!

From your descriptions, I understood you failed to upgrade to SQL Server
SP4 on your Cluster Server. If I have misunderstood your concern, please
feel free to point it out.

Based on my knowledge, we have a Knowledge Base article lists an overview
of the tasks that you must perform before you install SQL Server 2000
Service Pack 3 (SP3), SQL Server 2000 SP3a, or SQL Server 2000 SP4 on a SQL
Server 2000 virtual server for failover clustering.

SQL Server 2000 Service Pack 3, Service Pack 3a, or Service Pack 4
pre-installation checklist for SQL Server 2000 virtual server for failover
clustering
http://support.microsoft.com/kb/811168

You could also view follow section in SQL Server SP4 readme file

3.4 Install on a Failover Cluster
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b
0d2a3/ReadmeSql2k32asp4.htm#_installing_on_a_failover_cluster

If above two articles does not resolve your issue, please post your log
file c:\windows\sqlsp.log for us.

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

bearface@newsgroup.nospam - 28 Jun 2005 22:07 GMT
Actually I was successful applying SP4 to the SQL cluster, but that was a
week or two ago.

I was trying to add a new node to the cluster, SP4 would not install. I got
desparate and figured out SP3a would install, then SP4 gave a cluster disk
ownership error that I worked around by taking our server out of production
for 5 minutes over the weekend and got SP4 to install.

Everything seems to be fine now.

> Hi,
>
[quoted text clipped - 38 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Michael Cheng [MSFT] - 29 Jun 2005 06:59 GMT
Hi,

It's great to hear you have resolved it by let the server offline for about
5 minutes. I guess some resources was occupied? Anyway, thanks for sharing
this information with us :)

If you have any questions or concerns next time, don't hesitate to let me
know. We are always here to be of assistance!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.