Failover Cluster 2012 Network Name fails to come online.

Hi,
I created a new one node Windows 2012 failover cluster. The cluster was created successfully, but configuring Client Access Point finished without creating VCO in Active Directory. Then I created computer object in the same OU
with cluster according article
http://technet.microsoft.com/en-us/library/cc732035(v=ws.10).aspx
Permissions on OU and VCO for cluster account where escalated to FULL, DNS A and PTR records where created, quota related to creating computer objects was increased, but has fixed my problem: events 1194 and 1069 are generated on attempt to online
network name. Following one guide, I tried to find the registry key for network name resource that corresponded with the GUID of the object of VCO, but it was absent here.
I've investigated everything I could find and found no solution.
Any help would be appreciated.

Hi,
Please install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters update first, then try again.
Recommended hotfixes and updates for Windows Server 2012-based failover clusters
http://support.microsoft.com/kb/2784261
Hope this helps.
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.

Similar Messages

SCC Cluster name failed to come online on perticular node

Hi all,
I'm working on a 2-node SCC cluster that I've had up and running for quite a while. For some reason now, I cannot move one of my CMS' to a particular node. I am getting two events in the event viewer: 1207 & 1069.
1207 from event viewer is:
Cluster network name resource 'Network Name (EXG)' cannot be brought online. The computer object associated with the resource could not be updated in domain 'ADI.local' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'CLUS$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
"EXG" is Exchange application instance (CMS)Network name which is failing on perticular node. Find cluster log below for more info
So, my question is, does anyone know what needs to be done in Active Directory to rectify this problem?
-------- Cluster log ----------
00001824.000025f4::2012/10/16-23:39:11.550 WARN [RES] Network Name <Network Name (EXG)>: Trying to remove credentials for LocalSystem returned status C0000225, STATUS_NOT_FOUND is a non-critical failure for a remove operation
00001824.000025f4::2012/10/16-23:39:11.613 INFO [RES] Network Name <Network Name (EXG)>: Initiating the Network Name operation : 'Verifying computer object associated with network name resource EXG'
00001824.000025f4::2012/10/16-23:39:11.613 INFO [RES] Network Name <Network Name (EXG)>: Trying to find computer account EXG object GUID(6a0d9900d2122d4480ea5acc1653e0be) on any available domain controller.
00001824.000025f4::2012/10/16-23:39:11.738 INFO [RES] Network Name <Network Name (EXG)>: Found computer account EXG on domain controller
domain.com 00001824.000025f4::2012/10/16-23:39:11.738 INFO [RES] Network Name <Network Name (EXG)>: Trying to obtain the VSToken for Core Cluster Name resource
00001824.000025f4::2012/10/16-23:39:11.784 ERR   [RES] Network Name <Network Name (EXG)>: Can't acquire crypto context for container 814f67ea-6f38-41ed-a331-a421cb4de9cc-Netname Resource Data with provider "1\Microsoft Enhanced Cryptographic
Provider v1.0". status 2148073494.
00001824.000025f4::2012/10/16-23:39:11.784 ERR   [RES] Network Name <Network Name (EXG)>: Unable to decrypt Core netname resource's ResourceData, status 2148073494.
00001824.000025f4::2012/10/16-23:39:11.784 INFO [RES] Network Name <Network Name (EXG)>: GetCoreNetnameObject_VSToken returning status 2148073494
00001824.000025f4::2012/10/16-23:39:11.784 ERR   [RES] Network Name <Network Name (EXG)>: This Netname resource can not be brought online, Failed getting token for CNO
00001824.000025f4::2012/10/16-23:39:11.800 WARN [RES] Network Name <Network Name (EXG)>: Trying to remove credentials for LocalSystem returned status C0000225, STATUS_NOT_FOUND is a non-critical failure for a remove operation
00001824.000025f4::2012/10/16-23:39:11.800 ERR   [RHS] Online for resource Network Name (EXG) failed.

Hello,
How this is done ? I couldn't find any documentation, and i struggle with the issue
"ERR [RES] Network Name <Cluster Name>: Can't acquire context handle for container 24263d98-4b17-4cff-866c-80f90ea0623f-Netname Resource Data with provider "1\Microsoft Enhanced Cryptographic
Provider v1.0". status 0X80090016."
ERR [RES] Network Name <Cluster Name>: Unable to Decrypt the password. status 2148073494."
Thanks for the help

Failover Cluster Network Name Failed and Can't be Repaired

I have an issue that seem to be a different problem than any others have encountered.
I've scoured everything I can find and nothing has fixed my problem.
The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster. The computer object was still in AD and appeared to be fine so it was not the common problem of the object
getting deleted somehow. At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
Since it was in the failed state, I tried to do the repair on the object to no avail.
We run a "locked down" DC environment so all computer objects have to be pre-provisioned. They were all pre-provisioned successfully and successfully assigned during cluster creation. The cluster was running with no issues for a month
or so before this problem came up.
When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
I believe this is what is causing the repair failure. All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain. I can't seem to find
a way to do this with the cluster network name. If there's a way please let me know.
I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster? I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
Any help would be appreciated

Hi,
I don’t find out the similar issue with yours, base on my experience, the 4096 error
often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started. I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
repetitive, could you explain further?
The cluster validates successfully with a few warnings:
Validating cluster resource Name: DT-FileCluster.
This resource is marked with a state of 'Failed' instead of
'Online'. This failed state indicates that the resource had a problem either
coming online or had a failure while it was online. The event logs and cluster
logs may have information that is helpful in identifying the cause of the
failure.
- This is because the cluster name is in the failed state
Validating the service principal names for Name:
DT-FileCluster.
The network name Name: DT-FileCluster does not have a valid
value for the read-only property 'ObjectGUID'. To validate the service principal
name the read-only private property 'ObjectGuid' must have a valid value. To
correct this issue make sure that the network name has been brought online at
least once. If this does not correct this issue you will need to delete the
network name and re-create it.
- This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
The user running validate, does not have permissions to create
computer objects in the 'ad.unlv.edu' domain.
- This is correct, we run a restricted domain. I have a delegated OU that I can pre-provision accounts in. The account was pro-provisioned successfully and was at one point setup and working just fine.
There are no other errors nor warnings.

UDLM rac-udlm-rs failing to come online

Hi all,
I'm setting up a zonecluster that will be running RAC. This has gone well, up to the point where, using clsetup, I attempt to create the rac-framework-rg (and associated rac-udlm-rs, rac-framework-rs).
In attempting to create the resourcegroup, the rac-udlm-rs fails to come online, causing the rest of the framework to fail.
The error in the logfile for UDLM (/var/cluster/ucmm/dlm_<zone>/logs/dlm.log is:
CONNECT ERROR: 'Invalid argument', family=0, port=6009, in=0.0.0.0
This repeats 5 times per second on both zonecluster nodes. regularly the error changes port (i.e. it cycles through the ports).
I've tried rebuilding the zonecluster, to no avail. I am at a loss as to what the error might be, or where to start looking, since there is no evidence anyone has ever hit this error before.
Any suggestions on where to look and what I can try to fix this is will be appreciated.
Possibly related, or even the cause, is that the zonecluster has been configured with:
add net
address=xxx.xxx.xxx.xxx
end
at the zonecluster level, but these addresses are not showing up under 'ifconfig -a'. Maybe I'm misunderstanding how they are used, and when they should show up though.
Some notes:
the zonecluster in all other respects seems fine - I have QFS resources configured and these appear to successfully work in all circumstances.
the ORCLudlm package is installed (the one that comes with Oracle 11.2.0.3)

Right, in case this helps someone else in future:
I found the problem. In a fully working zonecluster configuration the /etc/nsswitch.conf file includes these lines:
hosts: cluster files
netmasks: cluster files
but for sad, sad, reasons on the system I was setting up this file had:
hosts: files
netmasks: files
and you know what, this allows you to go:
ping clusternode1-priv
and this does a lookup and resolves correctly. Now, if this doesn't resolve correctly, basically the UDLM daemon cannot communicate with the other cluster nodes, because it must do a nameserver lookup on clusternode1-priv internally.
So, in essence, make sure your nsswitch.conf file looks up the cluster first for hostname lookups.
This issue shows itself if you do a traceroute to the IP of the other cluster node (from one of the zonecluster nodes) using the private interconnect IP address. In a working system it'll show the name (clusternode1-priv). In a non-working system it shows the IP only.

Cable Modem fails to come online ?

Hi,
Cable modem fails to come online
Never gets beyond state init(i) wend I try to boot
other than defaul file ??
cisco CMTS uBR7114E IOS-Version: 12.1(13)EC3
Cable modem Motorola SB5100
----- CMTS Konfig ----
cable config-file platinum.cm
service-class 1 max-upstream 256
service-class 1 guaranteed-upstream 256
service-class 1 max-downstream 2250
service-class 1 max-burst 1600
cpe max 2
timestamp
!- This config not work ? -
ip dhcp pool cm-0011.1a04.9944
host 10.10.6.63 255.255.255.0
client-identifier 01.111a.0499.44
bootfile silver.cm

Are you getting any errors when you run the "debug cable mac log ". Under normal conditions ,when you run the "debug cable mac log" command and you see nothing, it means that the modem has completed the process of coming online. If you run the "show controller cable 0 mac state" command, you should see the MAC state set to "maintenance_state", which is code in the DOCSIS world for "online". Check if you are getting any errors and if yes what is the error message that you find...

Enable Shadow Copies for Shared Folders in a Failover Cluster (2012 R2)

I cannot find a reference on how to Enable Shadow Copies for Shared Folders in a Failover Cluster
using separate disks for Data and Shadow Copies, using Windows Server 2012 R2. I found an article for Server 2003, but that doesn't solve my issue.
Enable Shadow Copies for Shared Folders in a cluster. Can someone point me to documentation on how to setup properly?
I have a 3 server failover cluster, a single fileserver role with a 2 TB data storage drive and a 200 GB disk for shadow copy drive. The 2 TB is ReFS and being used by Home Directories. The 200 GB is also ReFS, but I didn't have a letter
assigned, but it is associated with the fileserver role.
Any help is appreciated.
Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

As mentioned above I spotted Shadow Copy configuration problems in clustered environment on Windows 2012 R2 with latest updates.
Enabling Shadow Copy via Cluster Manager on disk will enable schedule and snapshots but schedule is not-cluster aware (is created locally on node) and "Previous Versions" are visible only locally but not via shared folders (UNC path accesible by
clients)
When I spotted this behavior I tried different way going via Computer Management and cluster resource name but console always hangs for me when using "Configure Shadow Copies". After many minutes configuration window is opened (Hurray!) but any
action there will hang whole console again. Enabling Shadow Copies will fail with "0x80004005: Unspecified
error" for creating scheduled task but "Next Run Time" column still shows "Disabled". Checking disk resource via Cluster Manager shows it is enabled and ?local? scheduled task is created.
Computer management console still shows DISABLED and any action freezes whole console (only when cluster resource name is used).
This fix I found, unfortunately, is not applicable to 2012 R2 OS: https://support.microsoft.com/en-us/kb/2894464
To sum up there is a major bug in MS implementation in Shadow Copies for Shared Folders when clustering is used or it is still not supported in 2012 R2? Doing it outside cluster works as it should (without freezes and Previous Versions are available via
UNC)
There is no documentation about FileServer Clustering on 2012(R2) unfortunately.
Could someone from MS clarify it?
Many thanks
Filip
EDIT:
Ok, one correction:
Scheduled task is not created in "Failover Clustering" hive of Scheduled tasks as user may expect but failover of fileshare to other node will unregister/reregister it on active node only.

Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2. I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster. After upgrading the cluster I am unable to migrate some VMs from one node to another. When trying to do
a live migration, I get the following notifications under the Rating Explanation tab:
Warning: There currently are not network adapters with network optimization available on host Node7.
Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue.
I get this error for 3 out of the 4 nodes in the cluster. I do not get this error for Node10 and I can live migrate to that node in VMM. It has a green check for Network optimization. The others do not. These errors only affect
VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues. In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to. I've checked the network
adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM. I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
queue" and Enable IPsec task offloading" checked. I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1. Why is this an issue now but it wasn't before
running on the new cluster? How do I resolve the issue? VMM is useless if I can't migrate all my VMs with it.

I checked the settings on the physical nics on each node and here is what I found:
Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading". I unchecked those
2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
It seems to me that if I could adjust those VM settings from VMM that it might fix the problem. Why isn't that an option to do so in VMM?
Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager? That would be a lot of unnecessary work but I don't know what else to do at this point.

Selecting VHDx as storage for File Server Role (Failover Cluster 2012 R2)

Is it possible to select an already existing (offline) VHD or VHDX as storage when creating the "File Server" role? Reason I want to do that is because I already have a file server setup as a virtual machine and causing issues so my company
decided to make the change towards a File Server role.
Thank you
David

Hi David,
Do you mean you configured it to file server failover cluster via "High Availability Wizard" ?
I think you need to choose a shared volume between two nodes to achieve high availability .
Please refer to following link :
http://technet.microsoft.com/en-us/library/cc731844(v=WS.10).aspx
If you do not select a shared volume , I think there is no difference than sharing a mounted VHDX file on a standalone file server .
I would suggest to copy these files to CSV and share them .
Hope it helps
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.

Hyper-V Failover Cluster - Inconsistent Network Availability

We've got a Small cluster with, 7 hosts and a dozen or two VM's. For some reason i'm getting inconsistent availability with the Cluster networks. The host seem to function fine on there own but theres all types of issues using Migration which
i'm assuming is because certain hosts think other hosts are unavailable. For Example:
Cluster Network 1 - From Host 8
Cluster Network 1 - From Host 10
As far as I can tell all of the networks are UP. I can ping all hosts on all interfaces. What criteria goes into determining host availability?

Hi,
Maybe you forgot to configure the Live migration Settings,
In the Failover cluster manager->right click networks-> select the livemigration network.
Hope this helps.
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.

Network connection failed resistance 2 online

im trying to play resistance 2 online and the ps3 only says network connection failed disconnecting from network 00180000. And i have a good connection i tested it. im playing in sweden by the way

TheDudeAhmed wrote:
the servers are closed I believe, however I think there are some user created rooms that you can play in
No there not closed all the Resistance series games are still online Resistance 2 is actually the busiest co-op and unranked mainly. As for the OP try rebooting your network equipment and also check your routers firmware is up-to-date particularly if it's a Netgear, Resistance games can be picky with some routers had trouble myself in the past.

Failover Cluster - Hyperv Networking

Hi All
I am in the middle of a private cloud project and i am having a few issues with my Fail over Clustering
I ended up creating my fail over which ran successfully but later complained about my Networking
This is a fully virtualized environment with 3 hyper v hosts running windows server 2012 R2.
These are my network settings.
I have put the main and cluster ip addresses as shown above on vmnet 3 and 4.(vmware workstation)
I am not sure of how to configure the hyper v virtual switch network tho.
so i have a feeling this could be the error i am getting when i try to validate my fail-over cluster.The error is shown below
Regards to all

"is there any other way i can just create a two node fail over in vmware workstation without having to use physical servers "
Absolutely! You will need at least three VMs. One VM will be your Active Directory domain controller and your shared storage server (not a best practice, but it seems like you are creating a lab, so it will work). Then you will need two
to be the nodes of the cluster. On the first machine you will need to set up either iSCSI or SMB - SMB is a lot easier.
http://blogs.technet.com/b/josebda/archive/2013/08/16/3587652.aspx provides a step by step guide for setting up a configuration that is more complex than you want, but it should
help you get started. He uses a three node cluster, but two will do. And, he is doing things under Hyper-V, so some things will have to be translated to the VMware environment. Of course, if you use Hyper-V on a Windows 8.1 system instead
of VMware workstation, more will apply.
. : | : . : | : . tim

Windows 2012 Failover Cluster - File server role (vCO)

Hi,
I wonder if anybody can shed some light on a query i have.
A windows 2012 failover cluster will be built in AD domain example.uk. Cluster File server roles will be created and will reside in this domain also.
We also have a requirement to run a cluster file server role in the child domain off secure.example.uk. Is this possible? or do the file server roles and related vCO's have to reside in the same domain as the cluster (CNO).
I know the CNO can be used to create the VCO but could a prestage a VCO in the child domain of secure.example.uk.
Mark

Hi Mark,
By default CNO will create
VCO automatically in default domain computer OU, we generally use the
KISS principle to place the CNO and VCO to the same OU, and as far as I know there no known design document indicate the VCO can be placed in different domain, therefore I suggest you place the CNO and V CO at same OU.
More information:
When Creating a New Resource or Role in Windows Server 2012 R2 Failover Cluster, the Network Name Fails to Come Online or Failed to Create Associated Computer Object in Domain
http://blogs.technet.com/b/askpfeplat/archive/2014/11/17/when-creating-a-new-resource-or-role-in-windows-server-2012-r2-failover-cluster-the-network-name-fails-to-come-online-or-failed-to-create-associated-computer-object-in-domain.aspx
CNO Blog Series: Increasing Awareness around the Cluster Name Object (CNO)
http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
How to Create a Cluster in a Restrictive Active Directory Environment
http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
Prestage Cluster Computer Objects in Active Directory Domain Services
https://technet.microsoft.com/en-us/library/dn466519.aspx
I’m glad to be of help to you!
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 Support, contact [email protected]

FailSafe - Intelligent Agent - Network Name

Here's the ordeal.
A client has a windows 2000 cluster (gak). I set up Oracle FailSafe 3.3.1 and for several months it has worked fine. THey had a poweroutage the other day and the UPS battery was running low. They shut the servers down without taking the group offline (dough). When the first box went down a failover occured. Then the second was shutdown. Upon restarting they did not realize the database was set to not failback automatically. Then it is unclear what occured as panic set in. Now I have repaired most of the damage and the group is back ionline with the two datbaase and listener functioning properly. Howwever the Agent has failed to be restored because the Network Name resource fails to come online. Windows provides little info on why.
For a brief time I was able to get the Network Name to come online by removing it an recreating it with the Microsoft Cluster Administrator. With the fully qulified name and domain machinename.foobar.local. Then the intelligent agent was added and everything came on line. Meanwhile, back at the OEM management server, it was restarted and an atemmpt was made to refresh the node. WANK! WOn't refresh the node. An error says that there is a conflict between the Intelligent Agent version and the OEM Management server....both however are found to be 2.2 (I suspect though the agent was reinstalled on the cluster but I have not confirmed. Here come the questions:
Why does now the Network Name fail to come online? (tried everything now excpet rebooting the entire shooting match.)
Verifying the INtelligent Agent version?
Anythoughts on troubleshooting the agent would be appreciated before I rebuild the whole freakin' mess....
Brad

Tks for your reply
For this moment i've deployed one agent agent OFF on each node .This part of configuration is ok ,
i can monitor database from grid control.
the goal is configuring agent for failsafe now and integrate agent OFS to ressource . ,
I've got an error while step 'add ressource to group ' ( refer to NOTE:396659.1 paragraf 11)
The added ressouce ( grid agent) hang online pending on the screen of failsafe manager.
In the note it's notified to add Network name ,and IP address as dependencies, but i can find only Virtual IP adress in the scrolling box.
any idea ??

Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.

Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
I keep getting this error message. Can someone please help. Thank You.
Kranp.

Hi Kranp,
As the issue is more related to Windows Server high availability
, I recommend you post the question in the
Windows Server High Availability (Clustering)
forum. It is appropriate and more experts will assist you.
Besides, there are similar threads regarding to the above error for your reference.
2012 Cluster service name failing
SQL 2012 Failover Cluster - unable to start because
of 'Network Name' failed
Issues with resource creation on W2K12 SQL
failover cluster, confirm procedures
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SQL Server Agent fails to connect to DB after enabling mirror on failover cluster

Hello:
We have multiple databases running in a Failover Cluster instance: SQL 2012SP1 on Server 2008 R2 failover cluster (NOT AlwaysOn). We are trying to add a high-performance mirror in a standalone instance for DR. My understanding is that should be a perfectly
normal, supported configuration.
The mirroring is working properly; however, the clustered SQL Server agent is unable to run jobs that run in the mirrored databases.
We get the following in the job log: Unable to connect to SQL Server 'VIRTUALSERVERNAME\INSTANCE'. The step failed.
There is a partner message in the agent log: [165] ODBC Error: 0, Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. [SQLSTATE IMH01]
The cluster is not a mulitsubnet cluster. All hosts are connected to the same subnets and there is no storage replication. I can not find any place where I can adjust the connect string options for SQL Agent.
Any guidance or suggestions on how to resolve this would be appreciated.
~joe

SQL Team - MSFT:
Thank you for taking the time to research and provide a clear answer.
This seems very much a workaround and very unsatisfactory.
You are correct, there is an IP dependency with OR condition. Moving to an AND condition is not viable for us. The whole point is to provide network redundancy. With an AND condition, if EITHER network interface fails, the service will go offline or fail
to come online without manual intervention. This is arguably worse for uptime than having a single interface available.
We are in process of rewriting all our SQL jobs to start in tempdb before transitioning to the appropriate target database. If this works for all of our jobs, I will mark the above response as answer.
Again, thank you for the answer.
Regards,
Joe M.

Failover Cluster 2012 Network Name fails to come online.

Similar Messages

Maybe you are looking for