DAG Failover Cluster Service Errors

Hi all,
I have six Exchange 2013 SP1 mailbox servers installed on Server 2008 R2 configured in two seperate DAG's (3 and 3).
I'm using a single NIC on all the servers for replication and server connectivity. 
I pre-staged the DAG computer object in AD (and assigned permissions), and configured DNS entries for both (confirmed and resolvable). I also configured the DAG network subnet and DAG IP address via EAC. 
At the moment I have active DB's on each server and then a passive copy on each other server, and all instances are healthy.
However, when I look in the WFC on each server, there are a ton of errors in the cluster event logs. All of the nodes show up as green, along with the cluster network, but the cluster shows "The cluster network name is not online". 
Cluster resource 'Cluster Name' in clustered service or application 'Cluster Group' failed.
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'contoso.com' 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 'DAG$' 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.
I've removed and re-added DNS records, and double checked the permissions on the CNO object. What else can I do?

Hi,
Its not a good idea to add a static DNS-Record for the DAG - Remove it and on the member holding the PAM, run ipconfig /registerdns.
Martina Miskovic
It also turns out that the CNO objects were never re-enabled by Exchange during the DAG creation process. Once I followed your steps above, and manually enabled the object in AD, the DNS entries auto-populated and everything came online.
Thanks for the help!

Similar Messages

  • Failover cluster validation errors

    We are trying to set up a failover cluster file server between two domain controllers running Windows Server 2012 RC.
    When we go through the Validate Configuration wizard, we receive the following errors messages against the Active Directory configuration (names have been changed).
    "It could not be determined whether node computer1.example.com is a read only domain controller because of this error: The object does not exist."
    and
    "Node(s) computer1.example.com computer2.example.com cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers."
    Does anyone have any ideas why this might be happening? Replication and DNS appear to be working fine for all other services.

    I did some tracking down of the problem, and it appears that it stems from the cluster not being able to retrieve the node names.  The function specifically is called GetFqdnNodeNamesFromCluster( ).
    It can be seen if you run "Get-ClusterLog" while the cluster is in the process of being created.  This error seems to be the root of the cluster creation failure.  Here is a stacktrace:
    PS C:\Users\gamroot> Get-ClusterLog -v
    VERBOSE: Connecting to cluster on local computer TESTNODE1.
    VERBOSE: at MS.Internal.ServerClusters.Cluster.GetNodes()
    at Microsoft.FailoverClusters.PowerShell.FCCmdlet.GetFqdnNodeNamesFromCluster(Cluster cluster, Boolean onlineOnly)
    at Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand.WrappedProcessRecord()
    at Microsoft.FailoverClusters.PowerShell.FCCmdlet.ProcessRecord()
    VERBOSE: at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
    at MS.Internal.ServerClusters.SafeFilteredEnumHandle..ctor(Cluster cluster, Boolean filterCoreGroups, Boolean
    filterCoreResources)
    at MS.Internal.ServerClusters.SafeClusterEnumHandle..ctor(Void* enumHandle, Cluster cluster, ClusterEnumType
    enumType, SafeClusterEnumHandleOptions options, SafeClusEnumHandleType safeClusEnumHandleType)
    at MS.Internal.ServerClusters.NativeMethods.ClusterOpenEnum(Cluster cluster, ClusterEnumType enumType,
    SafeClusterEnumHandleOptions options)
    at MS.Internal.ServerClusters.Cluster.GetNodes()
    VERBOSE: at MS.Internal.ServerClusters.ClusterRegistryKey.GetValue(String name)
    at MS.Internal.ServerClusters.Cluster.GetCoreClusterGroup()
    VERBOSE:
    Get-ClusterLog : Failed to retrieve the list of nodes for 'TESTCLUSTER1'.
    Could not retrieve the core cluster group for the cluster 'TESTCLUSTER1'.
    An error occurred while querying the value 'ClusterGroup'.
    Element not found
    At line:1 char:1
    + Get-ClusterLog -v
    + ~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (:) [Get-ClusterLog], ClusterCmdletException
    + FullyQualifiedErrorId : NotFound,Microsoft.FailoverClusters.PowerShell.GetClusterLogCommand

  • Exchange 2013 DAG - Failover Cluster Warnings

    I have two new Exchange servers (PROD1 and DR1) that I recently updated to CU8 in preparation for going into production.  After reboots, I noticed that I had a warning on the "Server Manager" window.
    PROD1 lists itself, DR1, and DAG1 as servers though it marks DAG1 as not accessible.
    DR1 lists only itself and PROD1.  It does not list DAG1.
    PROD1 is generating a ton of failover cluster errors (1205, 1254, 1069, 1044) while DR1 is clean.
    In the Failover Cluster Manager of each server, the object of DAG1 is listed as "Offline".  It has two IPs - one for each of the Exchange servers' subnets (this is where I think I screwed up).  The IP for PROD1's subnet is 10.2.8.131
    and is "Failed" and the IP of DR1 is 10.4.8.131 and is "Offline".  The IP of PROD1 is 10.2.8.132 and DR1 is 10.4.8.132.
    Attempts to bring the cluster object online fail "due to the failure of one or more provider resources".
    The instructions I followed to set up the DAG did not mention the need for multiple NICs.  I now think this is incorrect and would be willing to use separate subnets and NICs for the DAG if necessary.  (I could use 10.2.12.X and 10.4.12.X instead.)
    I am currently still able to fail the database copy between DR1 and PROD1 without any problems.

    Hi Jkm,
    As you said :PROD1 is generating a ton of failover cluster errors (1205, 1254, 1069, 1044) while DR1 is clean.
    I suggest you post failover cluster errors to
    [email protected] for our troubleshooting.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Windows Failover Cluster Manager Error

    I have a node that is not able join the Hyper-V cluster that it was previously running in the cluster without problems.
    The cluster service encountered an unexpected problem and will be shut down. The error code was '2'.
    C:\Windows\Cluster>clussvc.exe -s
    -----------------------------+ LOG BEGIN +-----------------------------
    [CS] Starting clussvc as a service
    [CS] cluster service logging level is 5
    [CS] Caught exception ERROR_FAILED_SERVICE_CONTROLLER_CONNECT(1063)' because of 'StartServiceCtrlDis
    patcher( ServiceTable )'
        000007fe:fda6aa7d( ERROR_MOD_NOT_FOUND(126) )
        00000000:0018f5d0( ERROR_MOD_NOT_FOUND(126) )
        00000000:0018fbb0( ERROR_MOD_NOT_FOUND(126) )
        00000000:ffd1a368( ERROR_MOD_NOT_FOUND(126) )
        00000000:0018f5a0( ERROR_MOD_NOT_FOUND(126) )
        00000001:e06d7363( ERROR_MOD_NOT_FOUND(126) )
    [CS] About to exit process...
    C:\Windows\Cluster>
    thank you for any guidance you may provide
    ron
    Ron Finnegan DHHS NIH NIMH LNT

    Hi Ron,
    Thank you for the reply.
    Have you installed this hotfix?
    http://support.microsoft.com/kb/975486
    Related information:
    http://blogs.technet.com/b/rspitz/archive/2010/08/26/the-cluster-service-service-terminated-with-service-specific-error-183-0xb7.aspx
    http://technet.microsoft.com/en-us/library/cc756369(WS.10).aspx
    Tim Quan
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact [email protected]  
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
    your question. This can be beneficial to other community members reading the thread. 

  • Network DR test causes Exchange DAG network to fail (Failover Cluster Manager reports comms errors)

    We have a DAG configured between 2 mailbox servers, one in each of our main data centres. Our comms team recently performed a DR test between our 2 data centres, switiching from the main production link to the backup link. During this outage the Failover
    Cluster Manager reported errors, with each mailbox server reporting the other as uncontactable. The Events that were logged include the following:
    Isatap interface isatap.{02ADE20A-D5D4-437F-AD00-E6601F7E7A9D} is no longer active. (EventID 4201)
    Cluster node 'MAILBOX_SERVER' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the
    Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is
    connected such as hubs, switches, or bridges. (EventID 1135)
    File share witness resource 'File Share Witness (\\WITNESS_SERVER\SHARE_NAME)' failed to arbitrate for the file share '\\WITNESS_SERVER\SHARE_NAME'. Please ensure that file share '\\WITNESS_SERVER\SHARE_NAME' exists and is accessible by the cluster. (EventID
    1564)
    Cluster resource 'File Share Witness (\\\WITNESS_SERVER\SHARE_NAME)' in clustered service or application 'Cluster Group' failed. (EventID 1069)
    The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. Run the Validate a Configuration wizard to check your network
    configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. (EventID 1177)
    The Cluster Service service terminated with service-specific error A quorum of cluster nodes was not present to form a cluster. (EventID 7024)
    The Microsoft Exchange Information Store service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service. (EventID 7031)
    Looking at the Cluster Events in the Failover Cluster Manager Snap-In i see a heap of Event ID 47 (cannot activate the DAG databases as the server is not up according to Windows Failover Cluster Service) and:
    Node status could not be recorded. This could prevent some network failure logic from functioning correctly. NodeStatus:IsHealthy=True,HasADAccess=True,ClusterErrorOverrideFalse,LastUpdate=5/2/2011 8:25:42 AMUTC Failure:An Active Manager operation failed.
    Error: An error occurred while attempting a cluster operation. Error: Cluster API '"ClusterRegSetValue() failed with 0x6be. Error: The remote procedure call failed"' failed.. (EventID 184)
    Forcefully dismounting all the locally mounted databases on server 'BACKUP_MAILBOX_SERVER. (EventID 307).
    Our Comms team doesn't believe it is a comms issue as they did not log any network communication errors between the servers in the two sites (using icmp). So if it is not a comms issue, how can I configure the Failover Cluster Manager to be resilient to
    this type of network failover event.
    Thanks
    Dan

    Isn't it also true that in a stretched DAG with even numbered nodes, the PAM needs to be in the same site as the active DAG node?  If the connection between both nodes goes down, and the PAM is in the "passive" site, the primary node will
    dismount the databases since it can't check with the PAM to make sure its safe for it to be up.  
    In a even-numbered node stretched DAG, the PAM changes to the DR/passive site everytime a failover occurs, but doesn't automatically switch back when you reactivate the primary node.

  • Microsoft update KB 3002657 and 2008 R2 failover cluster for virtualization

    After installing Microsoft update KB 3002657 on my Windows 2008 R2 failover cluster for virtualization, nodes in cluster lost connection to CSV and all my VM's were moved to node owning the volume.
    I lost whole day to solve that problem.
    But should i keep that update not installed on cluster nodes or anyone maybe has a solution for that ?

    Hi a3pl,
    Unfortunately, the available information is not enough to have a clear view of the occurred behavior from the cluster perspective. Please offer us
    more information such as the failover cluster validation error, the failover error event ID, with the current information it is difficult to presume which part may cause this issue, we strongly suggest you install the following update when you use failover
    cluster.
    Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters
    http://support.microsoft.com/en-us/kb/980054
    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]

  • The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

    I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
    The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
    Thanks,
    Venu S.
    Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

    Hi Venu S,
    Based on my research, you might encounter a known issue, please try the hotfix in this KB:
    http://support.microsoft.com/kb/928385
    Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
    The version of Windows Server you are using
    The result of SELECT @@VERSION
    The scenario when you get this error
    If anything is unclear, please let me know.
    Regards,
    Tom Li

  • Reporting Services as a generic service in a failover cluster group?

    There is some confusion on whether or not Microsoft will support a Reporting Services deployment on a failover cluster using scale-out, and adding the Reporting Services service as a generic service in a cluster group to achieve active-passive high
    availability.
    A deployment like this is described by Lukasz Pawlowski (Program Manager on the Reporting Services team) in this blog article
    http://blogs.msdn.com/b/lukaszp/archive/2009/10/28/high-availability-frequently-asked-questions-about-failover-clustering-and-reporting-services.aspx. There it is stated that it can be done, and what needs to be considered when doing such a deployment.
    This article (http://technet.microsoft.com/en-us/library/bb630402.aspx) on the other hand states: "Failover clustering is supported only for the report server database; you
    cannot run the Report Server service as part of a failover cluster."
    This is somewhat confusing to me. Can I expect to receive support from Microsoft for a setup like this?
    Best Regards,
    Peter Wretmo

    Hi Peter,
    Thanks for your posting.
    As Lukasz said in the
    blog, failover clustering with SSRS is possible. However, during the failover there is some time during which users will receive errors when accessing SSRS since the network names will resolve to a computer where the SSRS service is in the process of starting.
    Besides, there are several considerations and manual steps involved on your part before configuring the failover clustering with SSRS service:
    Impact on other applications that share the SQL Server. One common idea is to put SSRS in the same cluster group as SQL Server.  If SQL Server is hosting multiple application databases, other than just the SSRS databases, a failure in SSRS may cause
    a significant failover impact to the entire environment.
    SSRS fails over independently of SQL Server.
    If SSRS is running, it is going to do work on behalf of the overall deployment so it will be Active. To make SSRS Passive is to stop the SSRS service on all passive cluster nodes.
    So, SSRS is designed to achieve High Availability through the Scale-Out deployment. Though a failover clustered SSRS deployment is achievable, it is not the best option for achieving High Availability with Reporting Services.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • [SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

    Hi there!
    I have a problem which makes me very angry already :)
    I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
    I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
    Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
    LOGS on the second nodes: 
    Application Log
    "Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
    Failover Clustering Diagnostic Log
    "[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
    CMDLET Error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:06:21
    MSC-CO-EXC-02V
    Failed
    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
    (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
    An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
    This operation returned because the timeout period expired
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
    Warning:
    Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
    Elapsed Time: 00:06:21
    UPD:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.
    Please, help me if you can.

    Hi, Jared! Thank you for the reply.
    Of course I did it already :) I have new info:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.

  • Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

    I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
    Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
    When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
    Any suggestion on resolving this problem?
    Thanks
    Ikad

    Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
    Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
    Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
    to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
    Ikad

  • SSL Cert for 2008 R2 Reporting Services that is installed on a Failover Cluster - server address mismatch?

    I utilized the idea from
    http://www.mssqltips.com/sqlservertip/2778/how-to-add-reporting-services-to-an-existing-sql-server-clustered-instance/ to install 2008 R2 Reporting Services on a new Clustered SQL instance.  In short, create the new Clustered SQL instance on Node1,
    installing Reporting Services with it.  Then on Node2, Add a Failover Cluster Node (without choosing Reporting Services); following that up with starting the SQL setup.exe with a cmd to bypass a check so that I can then install the Reporting Services
    feature on Node2.  It points out using the SQL Cluster Network name for connecting to Reporting Services.
    I verified upon failover that I could still access the Reports and ReportServer URLs.  However, when wanting to add an SSL certificate to the RS configuration, I run into the warning of "mismatched address - the security certificate presented by
    this website was issued for a different website's address", where I can continue and get to the Reports or ReportManager URLs.
    I played with different certs (internal CA created) and SANs and other things, but I still get this error with the cert.  The Reports URL, for example, is <a href="https:///Reports">https://<SQLClusterNetworkName>/Reports, and the
    cert has a CN and Friendly Name of SQLClusterNetworkName (with SAN of DNS: SQLClusterNetworkName.<domain>), but the error still happens.
    What am I missing to eliminate the mismatched address warning when using the SQLClusterNetworkName as the base of the URLs?

    I got it working by using the FQDN as the common name on the SSL cert, with FQDN in RS URLs.

  • Failover Cluster in SQL 2012 in not auto switch when stop service SQL

    Good Morning to all,
    I'm Mr.Tuyen from VietNam. I have a big problem with AlwaysOn High Availabity in SQL 2012.
    I setup 3 server and join Availabilty Group. Ex: Server A (Primary), Server B (Secondary), Cluster Qourum is only node. I have test:
    1. Stop service SQL server A, immediately server B is Primary
    Start servicel SQL server A, Server A is secondary
    2. Stop service SQL server B, server is not Primary and "status is Resloving" and role cluster failed with error as belows
    [i]Clustered role 'XXX' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role
    online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after
    the restart delay period.[/i]
    or 
    The Cluster service failed to bring clustered role 'XXX' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.
    Do you have same error?

    http://blogs.msdn.com/b/sqlserverfaq/archive/2012/03/15/inf-alwayson-the-secondary-database-doesn-t-come-automatically-when-the-primary-instance-of-sql-server-goes-down.aspx
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • Windows 2008 Failover Cluster - Cannot add a generic service

    Trying to add a generic service in a failover cluster.
    Select the option Services and Application and it opens the wizard and then displays the error "An error was encountered while loading the list of services. QueryServiceConfig failed. The system cannot find the file specified"
    The cluster validation wizard completes successfully. Permissions do not appear to be an issue as this account can seemly do everything else so I am at a loss to understand why this API is failing when it tries to query the server for services information.
    Having searched the Internet the only thing I have found was someone posting a similar issue in the Greek language Technet forum(if I recall correctly) and their comment was they rebuild their cluster.
    Windows 2008 (SP2) x64 two node cluster running a non-Microsoft database. We need to add a non-Microsoft Enterpirse backup solution and this is their documented method (adding it as a generic service) - both bits of software are from big vendors.
    Symantec AV, but have tried with that disabled so don't think it has anything to do with that. Something is stopping the API from reporting back but I can't find what.
    Really appreciate some help before we have to log a chargable call with Microsoft support
    Thank you

    Hi,
    Have you tried the suggestion? I want to see if the information provided was helpful. Your feedback is
    very useful for the further research. Please feel free to let me know if you have addition questions.
    Best regards,
    Vincent Hu

  • Windows Failover Cluster (Errors retrieving file shares)

    I'm having an issue with Windows Failover Cluster with a Windows Server 2012 R2  machine. I have two cluster nodes (nodeA and nodeB). My issue is that when nodeA is the owner node, and I open failover cluster manager  <clusterName> >>
    roles >> <fileserver role> >> shares tab it will hang and say that it is loading, but this will occur infinitely. Although when I go to nodeB (not the owner node) and I go to shares it will show me all of the shares that I have. Next when
    I go to <clusterName> >> Nodes  >> click on Roles tab the information says "There were errors retrieving file shares."
    Now when I switch the nobeB to the owner node, I cannot view the shares on that machine but can now view them on nodeA. 
    We alse have a test network where I have recreated the machines, environment and the failover cluster to as close as the production network as I can except everything works great in the test network 

    For anybody searching on this later...
    I was getting "There were errors retrieving file shares" no matter which node of my cluster
    owned the fileshare service.  Turns out my problem was that my servers don't have internet access and I had set a system proxy.  The fix described in the link below was to exclude the local domain from the proxy.
    http://blogs.technet.com/b/askcore/archive/2012/12/03/cluster-aware-updating-cau-interaction-with-proxy-servers.aspx

  • Failover cluster name missing subnet on DAG

    I've seen this multiple times and can't figure it out and end up having to recreate the DAG. On Server 2012 / Exchange 2013 I've experienced problems with the IP / subnet in failover cluster.
    Its like the DAG name loses the ip address (or someone deleted it).
    But the problem is when I open failover cluster manager and look at the properties of the "DAG Name" and try to add an IP address, it doesn't have the subnet that DAG nic is on. Each server has a MAPI and a DAG nic. Why does it only show the MAPI
    nic subnet and not the DAG nic?

    Hi,
    Based on the description, you can't check "Allow clients to connect through this network" on MAPI network.
    Is there any error message when you try to check "Allow clients to connect through this network"?
    Besides, please check if there is any related events in the application log.
    And please check the network settings on DAG member, you can look at the folllowing article.
    https://technet.microsoft.com/en-us/library/ff622321(v=exchg.141).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

Maybe you are looking for