cluster SSAS and SQL

Hi,
We have a default clusterd SQL server 2005 with sp2 installed in one cluster
group and then I have installed a default SSAS clustered instance in another
cluster group and it works fine (can failover and user can connect). However,
when I applying the sp2 to SSAS instance (with SSAS checked only) and it
failed; it not noly just failed but also take down my default clustered sql
server! We have to call MS to get our server up. It seems that, somehow,
registry for default sql server got messed up by SSAS sp2. My question are:
1.Is it possible or supported to install a default SQL server and a default
Analysis server on a cluster (each one in its own cluster group) with sp2;
2.why applying sp2 on a default AD instance in one cluster group affect a
default sql instance in another cluster group.
thanks much in advance.
Zack.
The answer is that SQL services share some common components. Plus, the
installer has some generic setup logic. Finally, are you using the same
service account for both services? If so, then permissions can get hosed
during a broken update.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"dp" <dp@.discussions.microsoft.com> wrote in message
news:90BAC728-916F-4497-B293-55920962EDE8@.microsoft.com...
> Hi,
> We have a default clusterd SQL server 2005 with sp2 installed in one
> cluster
> group and then I have installed a default SSAS clustered instance in
> another
> cluster group and it works fine (can failover and user can connect).
> However,
> when I applying the sp2 to SSAS instance (with SSAS checked only) and it
> failed; it not noly just failed but also take down my default clustered
> sql
> server! We have to call MS to get our server up. It seems that, somehow,
> registry for default sql server got messed up by SSAS sp2. My question
> are:
> 1. Is it possible or supported to install a default SQL server and a
> default
> Analysis server on a cluster (each one in its own cluster group) with sp2;
> 2. why applying sp2 on a default AD instance in one cluster group affect a
> default sql instance in another cluster group.
> thanks much in advance.
> Zack.
>
|||Zack, were you ever able to upgrade your SSAS in the cluster?
We are having the same or similar issues. We upgraded our cluster from SP1
to SP2. The SQL Server components upgraded to SP2, but the SSAS failed and
is still at SP1. After the upgrade one of our clustered instances did not
come back online. Error logs read something like, "...Cluster IP/Network
resource already in use..."
Well, I called MS because our production SQL 2005 cluster was hosed. The
issue, reg key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microso ft SQL
Server\MSSQL.1\Cluster\ClusterName" had the incorrect instance name for the
MSSQL.1 instance (in our case). We had to run some cluster commands to
remove the MSCS checkpoint, changed the key value to the correct instance
name, then reapply MSCS checkpoint.
This got our SQL Server instance back online. But we still can't update
SSAS to SP2. Maybe the two issues are not related, but I have a gut feeling
they are. The incorrect 'ClusterName' value happened to be the instance name
for our SSAS.
I still have the MS support ticket open trying to determine if the cluster
registry keys are in the correct state on both nodes.
Anyone else having issues with failover cluster anaylsis server upgrade to
SP2?
"dp" wrote:

> Hi,
> We have a default clusterd SQL server 2005 with sp2 installed in one cluster
> group and then I have installed a default SSAS clustered instance in another
> cluster group and it works fine (can failover and user can connect). However,
> when I applying the sp2 to SSAS instance (with SSAS checked only) and it
> failed; it not noly just failed but also take down my default clustered sql
> server! We have to call MS to get our server up. It seems that, somehow,
> registry for default sql server got messed up by SSAS sp2. My question are:
> 1.Is it possible or supported to install a default SQL server and a default
> Analysis server on a cluster (each one in its own cluster group) with sp2;
> 2.why applying sp2 on a default AD instance in one cluster group affect a
> default sql instance in another cluster group.
> thanks much in advance.
> Zack.
>