Failover cluster installation - BO server

Hi,
I have two BO servers and I have to configure them in failover mode.
If the principal fail, the second one works.
Does anyone try to do it before?
Thanks,
Julio

Hi Durecu
I will follow the steps mentioned but my question is about options to user with sapinst.exe?
When should I have to usr SAPINST_USE_HOSTNAME?
1. Central services instance for ABAP installation.
Use the command line sapinst.exe SAPINST_USE_HOSTNAME=FRSERVERSAP
Note - during the installation time all the cluster resource should be in Node 1
During the time of Central service instance for ABAP & JAVA you have to use the Virtual hosts (that is on MSCS SAP Group DNS name, & Cluster disk before that you have to create in MSCS)
Syntax " SAPINST.EXE SAPINST_USE_HOSTNAME=<*Virtual Host Name*> "
2 First MSCS node installation => on Node I? Do I need to use SAPINST_USE_HOSTNAME=FRSERVERSAP ???
Normal SAPINST.exe Without virtual name
3 Database Instance Installation => Do I need to use SAPINST_USE_HOSTNAME? If yes, do I use FRSERVERSQL???
Normal SAPINST.exe Without virtual name
4 Additional or Second MSCS node installation => on Node II? with SAPINST_USE_HOSTNAME?
Normal SAPINST.exe Without virtual name
Regards
Sriram

Similar Messages

New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Failover cluster installation

Hello,
I would like to install SAP ECC6 EhP4 from System Copy (backup/restore) in Windows failover cluster environnement with two nodes.
So, I have installed MSSQL Server 2008R2 SP2 in cluster mode (using virtual host : FRSERVERSQL).
Now, I have to install SAP ECC. (A virtual host has been created : FRSERVERSAP)
I have created manually SAP SID service on "Failover cluster manager" windows menu.
Inside this service, I have created :
- IP resource
- Shared folder (sapmnt : E:\usr\sap)
- Disque resource (E:)
I have created saploc shared folder (c:\usr\sap)
Following install guide and some SCN threads, I have doubt with the way to install SAP in Windows failover cluster environnement.
I found this way on SCN :
1. Central services instance for ABAP installation.
Use the command line sapinst.exe SAPINST_USE_HOSTNAME=FRSERVERSAP
Note - during the installation time all the cluster resource should be in Node 1
2 First MSCS node installation => on Node I? Do I need to use SAPINST_USE_HOSTNAME=FRSERVERSAP ???
3 Database Instance Installation => Do I need to use SAPINST_USE_HOSTNAME? If yes, do I use FRSERVERSQL???
4 Additional or Second MSCS node installation => on Node II? with SAPINST_USE_HOSTNAME?
5 Enqueue replication server installation for ABAP in Node I
6 Enqueue replication server installation for ABAP in Node II
7 Central Instance Installation in Node I
8 Dialog Instance Installation in Node II
9 Post processing steps after system copy
One more question.
After installation is OK, If I have to refreh this environnement (with homogenous sytem copy - backup/restore),
which option should I have to use after restore? Only Database instance installation or all options described above?
Thanks for your help
Regards

Hi Durecu
I will follow the steps mentioned but my question is about options to user with sapinst.exe?
When should I have to usr SAPINST_USE_HOSTNAME?
1. Central services instance for ABAP installation.
Use the command line sapinst.exe SAPINST_USE_HOSTNAME=FRSERVERSAP
Note - during the installation time all the cluster resource should be in Node 1
During the time of Central service instance for ABAP & JAVA you have to use the Virtual hosts (that is on MSCS SAP Group DNS name, & Cluster disk before that you have to create in MSCS)
Syntax " SAPINST.EXE SAPINST_USE_HOSTNAME=<*Virtual Host Name*> "
2 First MSCS node installation => on Node I? Do I need to use SAPINST_USE_HOSTNAME=FRSERVERSAP ???
Normal SAPINST.exe Without virtual name
3 Database Instance Installation => Do I need to use SAPINST_USE_HOSTNAME? If yes, do I use FRSERVERSQL???
Normal SAPINST.exe Without virtual name
4 Additional or Second MSCS node installation => on Node II? with SAPINST_USE_HOSTNAME?
Normal SAPINST.exe Without virtual name
Regards
Sriram

Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
I've been searching for a "best practices" article for this but have been coming up short. The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
to different hardware without failover cluster volumes.
If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
Currently, my approach is as follows:
1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
3. Stop the VMMS service on the 2008 r2 hostnodes
4. copy the virtual machine files and folders over to the new failover cluster volumes
5. Import vm's into server 2012 r2 hyper-v.
Any feedback on the opertain I have in mind would be helpful.
Thank you,
Rob

Hi Rob,
Yes , I agree with that "file copy " can achieve migration.
Also you can try "copy cluster wizard " :
https://technet.microsoft.com/en-us/library/dn530779.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Active-Passive Failover cluster in Windows Server 2008 R2

Hi,
As per the client requirements, I build an active-passive Oracle 11g R2 database cluster in Windows Server 2008 R2.
(Used Microsoft cluster as Client don't have Fail Safe licence)
As per the configuration, I follow the below mentioned steps:
a)OS vendor configured Active-Passive Windows Cluster
b)Installed Oracle 11g R2 on both the nodes with same ORACLE_HOME name
c)Create Listener and configured it with cluster IP in Node1
d)Create Database from Node1. Physical files location are all in Storage
e)Create Oracle Service with the same name in the 2nd node and copy all the files like spfile,tnsnames.ora,listener.ora,password file to Node2
f)Configure Listener with the same Oracle SID.
g)Test database failover from Node2 with Listener registration
h)Open the Windows Failover Manager to configure the Oracle Database and Listener Service in the Cluster Group
Now I am facing problem by moving Cluster Group movement. Whenever trying to moving the group, Listerner service is not getting up by Cluster Manager as quorum is not included in the group and that quorum disk is not moving in the failover node with the Oracle Cluster Group. As per my understanding Quorum having information of Cluster IP which has been configured with Listener.
But when I am shutdown one node, then in the other node all the resources successfully moving and cluster able to online all the resources. I guess at that time Quorum is also moving and thus cluster can able to make Listener online.
Please suggest how to resolve this issue. Means how can I make Listener up instead having any dependencies with Quorum in the fail over node?
Thanks a lot for your help.

hello
I was going through your post and i am also doing the same thing here at our organisation for Oracle 10g R2
Can you pls send me any docs u r having for configuration of Oracle in windows clusters .
And, can you pls elaborate on this point
e)Create Oracle Service with the same name in the 2nd node and copy all the files like spfile,tnsnames.ora,listener.ora,password file to Node2.
Pls send me the details at [email protected] or you can contact me at 08054641476.
Thanks in advance.

In Failover Cluster 2008 mailbox2 server network status Unavailable (down).

Hi
I am new here, & hope i can get some help for the below issue
let me keep it simple scenario
i have 2 mailbox server ( mbx01 & mbx02)
2 cashub Server ( cshb1-cshb2) all running on hyper-v. last week due to some maintenance in data center i have to bring down all the production environment, once the thing are fixed in DC , i started all the server and found out that my exchange node 2 database
are failed.
In exchange 2010 failover cluster node ( node2 ) is down network status unavailable. due to by exchange node2 database are failed.
also i cannot access the file share witness directory from any of the above server.
can any body assist me on this please
thank you

Make sure both the DAG members have access to the witness directory. Check the location and make sure you have access. Open the DAG properties from Node2 and try to update the witness server and witness directory. Check the firewall/antivirus of the witness
server. Try disabling antivirus and firewall. If witness server is not online your databases will go offline. Pleae check
this
Get-DatabaseAvailabilityGroup -Identity DAG -Status | fl name,servers,witnessserver,witnessdirectory,alternatewitnessserver,alternatewitnessdirectory,operationalservers,primaryactivemanager,witnessshareinuse
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

OS/hw based failover cluster for WebLogic Server 9.2 Standard Edition

Hi
Is it possible to run WebLogic Server 9.2 SE on OS/hardware based cluster?
I want to get an simple failover environment on a cluster of 2 nodes (active-passive).
Oracle Database can be run in such scenario with one license with a limit of up time for passive instance.
Is it the same with WLS licences?
Regards
WD

The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
Regards,
tom
Edited by: TomB on Sep 17, 2010 2:33 PM

2 Node Hyper-V failover cluster with sql server

I have 2 IBM Servers with Server 2012 installed and both machines have SQL server express. Is it possible to create HYPER-V Failover between the 2 servers including the SQL SERVER Instance meaning if the main node fails the second server will take over.
The second will act as virtualized failover of the main node with failover instace to act as active to active approach.
I hope can someone give me an advice with my question.

I have 2 IBM Servers with Server 2012 installed and both machines have SQL server express. Is it possible to create HYPER-V Failover between the 2 servers including the SQL SERVER Instance meaning if the main node fails the second server will take over.
The second will act as virtualized failover of the main node with failover instace to act as active to active approach.
I hope can someone give me an advice with my question.
Sure you can do that. But it's a long story what's better SQL Server FCI or AlwaysOn. See:
FCI Vs. AlwaysOn
http://msdn.microsoft.com/en-us/library/ff929171.aspx
(biggest issue with AlwaysOn - it does require Enterprise license so is COSTY)
Good idea to ask here:
SQL Server High Availability and Disaster Recovery
http://social.technet.microsoft.com/Forums/sqlserver/en-us/home?forum=sqldisasterrecovery
In any case you'll need either physical or virtual shared storage. For FCI to host everything and witness disk and for AlwaysOn just for witness (AlwaysOn does replication between DAS on it's own).
Good luck :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Configure Hyper V Failover Cluster on Window Server 2012 R2

I have 3 node cluster of hyper v and configured csv all machine working fine but after run backup machines get paused, so i have removed backup agent, during starting one virtual machine csv volume get un accessible and all machine pertain to that csv get
offline. subjected are the errors.
Cluster Shared Volume 'Volume2' ('Volume2') is no longer accessible from this cluster node because of error '(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
Cluster Shared Volume 'Volume2' ('Volume2') has entered a paused state because of '(c0000015)'. All I/O will temporarily be queued until a path to the volume is reestablished.
after troubleshooting i found a patch for the related issue but its not working for window server 2012 R2,
Windows8-RT-KB2838669-x64: its not running so kindly assist how to get this fix.
Talha Faraz Malik

Hi TFMalik,
"To avoid CSV failovers, you may have to make additional changes to the computer after you install the hotfix. For example, you may be experiencing the issue described in the "Symptoms" section because of the lack of hardware support
for Offloaded Data Transfer (ODX). This causes delays when the operating system queries for hardware support during I/O requests.
In this situation, disable ODX by changing the FilterSupportedFeaturesMode value for the storage device that does not support ODX to
1 "
For details please refer to the link below :
https://support.microsoft.com/kb/2813630?wa=wsignin1.0
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core

I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition

Hi KamarasJaranger,
According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
and refer to the
PDF file.
1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
2.Discover target portals.
3.Connect targets and configuring Multipathing.
4.Initialize and format the Disks.
5.Verify the Storage Replication Process.
6.Run the Failover Cluster Validation Wizard.
7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
8.Tune Cluster Heartbeat Settings.
9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
12.Test application connectivity.
Regards,
Michelle Li

SQL Server Failover Cluster Questions

Dear All,
            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
1.  I am receiving MSDTC Warning. I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not. I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
2. During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME". Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
3. During the instance creation, one needs to provide "SQL Server Network Name". As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
for all instances that I create or this is only required once in the cluster:
4. During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features. As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
it, so which features should be selected? so that there is less workload on the server.
5. All the instances use TempDB for databases that are present inside it. What would be the best practice with respect to TempDB. One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
should be the ideal size of the TempDB LUN?
6. Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
Thanks in advance.

Hello,
1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
in a failover cluster.
5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SQL Server 2012 Failover Cluster configuration questions

Hi,
I have few questions on , SQL Server 2012 Failover cluserting pleasse provide suggestions:
1) In SQL Server 2012 is there a configuration for active / passive Failover Cluster installation? If so how is it done? if you could provide any links or articles that would help.
OR
Is this been replaced by Always ON Availability Groups?
2) Also in our environment we have done active/active installation but at a time my understanding is only node has the ownership to the shared storage versus both the nodes, is that correct? If not please provide an explanation?
Any additional information would be valuable in clearing my doubts?
Thank youy
Malini=

Hi malinisethi,
If you install SQL Server in a cluster and configure Active-Passive cluster. In the first node, select “New SQL Server Failover Cluster installation” option , when we are installing Active-Passive cluster, we have to specify one virtual/network name. (Note:
For Active-Active clustering you have specify different network names as per the number of nodes). on the other nodes is similar to installing on the first node except that we have select the Add Node to a SQL Server failover cluster option from the initial
menu. For more information, there is a similar issue about SQL Server 2008 Active-Passive/Active-Active cluster installation, you can review the following article.
http://sqldbpool.com/2009/10/07/sql-server-2008-active-passive-cluster-installation/
About Active/Active SQL Cluster, two clustered SQL Server instance are created in different nodes. Then apply Active /Active configuration of both instance. There is an example about creating an Active/Active SQL Cluster using Hyper-V. you can review the
following article.
http://blogs.msdn.com/b/momalek/archive/2012/04/11/creating-an-active-active-sql-cluster-using-hyper-v-part2-the-clustered-instances.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SQL Server 2012 Failover Cluster Setup

I have to set up a Lab Test environment for SQL Server 2012 with failover clustering. What are the most cost effective specifications for H\W & S\W. AFAIK Apart of Enterprise edition, Standard edition can support failover clustering for upto
2 nodes with one node in passive mode. Somewhere (Here) I got that it is possible to configure SQL Server failover clustering On SQL
Server 2012 Developer edition. Also Is it possible to use Windows 7 Platform with SQL Server 2012 Developer Edition for configuring Always on Failover Clustering. Although I have researched alot, but puzzled. Seeking for experts advise. Thanks in advance.
Pranshul Gupta

Yes you can configure and install in windows 7.. but make sure you have made all the proper updates as per the microsoft suggestion..
Software and hardware requirments for sql 2012
http://msdn.microsoft.com/en-us/library/ms143506%28SQL.110%29.aspx
http://www.yourdba.com/?p=123
http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//015100000070000000
Developer Edition..
SQL Server 2012 Developer Edition will continue to be part of the SQL Server 2012 family. The Developer edition provides the same feature set as the Enterprise edition. However, it's licensed per developer and can't be used for production work.
Clustering FAQ's
http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
SQL Server licensing :
http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-licensing.aspx
http://www.microsoft.com/sqlserver/en/us/get-sql-server/how-to-buy.aspx
Overview and support :
http://msdn.microsoft.com/en-us/library/cc645993.aspx
FCI Failover Cluster Instances (SQL Server)
http://technet.microsoft.com/en-us/library/ms189134.aspx
AlwaysOn Availability Groups (SQL Server) -- AG's
http://technet.microsoft.com/en-us/library/hh510230.aspx
Raju Rasagounder Sr MSSQL DBA

SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
Node1: DB Engine 1 (named instance DB01)
Node2: DB Engine 2 (named instance DB02)
Node3: Analysis Services (named instance DBAS)
Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
Thank you much for reading. I appreciate any help to get this resolved.
POSSIBLY NOT RELEVANT...?
I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
help solve the issue.

When connecting to SSAS in a cluster, you do not specify an instance name. In your case, you would use the name of the SSAS IP address to connect.
See:
http://msdn.microsoft.com/en-us/library/dn141153.aspx
For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
"SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
How to Cluster SQL Server Analysis Services for more information and examples.

Failover cluster installation - BO server

Similar Messages

Maybe you are looking for