| Author |
Topic |
|
tomasi
Starting Member
7 Posts |
 Posted - 2004-09-08 : 05:59:45
|
| We just installed a SQL 2000 instance in a 2 nodes W2003 cluster. The services are running with a domain account which is local administrator on both nodes. When we start the setup for the SQL SP3a on the active node, we get to the remote setup window, where it asks username, password, and domain for the setup on both cluster nodes, we enter the info about the same domain account we used for the SQL2K setup, it gets backs saying "The caller is not the owner of the desired credentials", and won't let us continue. Any idea ? |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-08 : 23:12:16
|
| just to clarify you have active/passive cluster?also what cluster system are you using? we had the same problem, we upgraded the OS to Win2003 from Win2k on an HP cluster system, we called them up and they told us some drivers are not supported which may have caused the sp3a failure. |
 |
|
|
tomasi
Starting Member
7 Posts |
Posted - 2004-09-09 : 03:38:01
|
| Hi,At the moment is more of an active/passive. we've only set up one instance on one of the server. The goal is to have it active/active, setting up another instance on the other server. but first things first... get the first instance fully installed and functional.I'm not sure what the server hardware is, I'm new here, but given what I see around me, I bet they would be IBM or DELL.Did you then end up resolving the problem ? How did you do it ?Thanks. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-09 : 05:10:34
|
| as i mentioned, both nodes have been added as part of the cluster when we made the upgrade. so basically we will have a different scenario.so you only have one active node first (one member only).is the cluster working? i mean all disks are online? you can view this on cluster admin window. Basically when you do clustering, the sql appl is now on the shared drives not on the server machines.since you only have one node, applying the patch will only look for node 1 and it is the only owner of the data.also i find it really easy to manage the system if the cluster account is the same as the sql service account. |
|
|
|
tomasi
Starting Member
7 Posts |
Posted - 2004-09-09 : 08:02:58
|
| The cluster is definitely working, the SQL resources are correcty defined in the group with the shared drive which is online.I think that the sp3a goes on the other node, not only on node1. I confirmed this by looking into the event log at all connections on both nodes. In our setup though we did not use the cluster account; we created specific domain accounts for running the SLQ services. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-09 : 08:11:35
|
quote:
"The caller is not the owner of the desired credentials"
so what you're saying is that you've only ran the sp3a setup on active node and it didn't updated both nodes? you only need to apply it on the active node,usually.if this fails, since this is not yet in production, offline passive first, then apply the patch, see what happens.i'm not claiming this will work but it's an idea. |
|
|
|
tomasi
Starting Member
7 Posts |
Posted - 2004-09-09 : 08:32:55
|
| Well actually it did not apply the patch even on the primary, as the setup will not do the install after the credential error message. I might be tempted to do what you suggest, but I'd rather look at other options first. The problem is if we do that, I'm not sure how we would get the service pack software piece installed on the other node, where it needs to go too. It's not like we'll be able to rerun the sp3a setup on the secondary node, there is no instance there, so it would probably fail. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-09-09 : 23:00:52
|
what do you mean by :quote:
It's not like we'll be able to rerun the sp3a setup on the secondary node, there is no instance there,
don't you need sql installed on the 2nd node? |
|
|
|
tomasi
Starting Member
7 Posts |
Posted - 2004-09-10 : 03:10:50
|
| there are 2 components to the install : software components and database components. The way it should work is that when installing on the primary, the setup copies the sofware on the primary and remote installs also the same software on the secondary. It would also install the database components on the instance on the primary.so, I would guess that if we would reinstall the service pack on the secondary node, it would complain that it does not find the instance. I have not seen a way to tell it to only install the software. Or... we could balance the instance on the secondary. But then we would find ourselves with a setup where the software does not have the sp3a while the databases have it. Not very clean, I'm not sure how the setup would react to that. |
|
|
|
tomasi
Starting Member
7 Posts |
Posted - 2004-09-10 : 05:59:31
|
| for anybody interested in the issue... the problem was that the account used for the setup was in a different domain than the server. Using an account in the same domain resolved the problem. |
|
|
|
|
problem when installing sp3a