Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

Hi Everybody,
I have two node cluster and trying to add the third node (which is a Virtual Machine), all nodes are in different subnet and can communication with each other. While adding the third node it gives the error at the end of wizard " This operation
returned because the timeout period expired ". My domain controller is 2008 Enterprise Server and nodes are all running Windows Server 2012 Standard Edition. Any idea what is causing the issue.
thanks

Hi,
Before you add a server (node) to a failover cluster, we strongly recommend that you run the Validate a Configuration Wizard for the existing cluster nodes and the new node
or nodes. The Validate a Configuration Wizard helps you confirm the configuration in a variety of important ways. For example, it validates that the server to be added is connected correctly to the networks and storage and that it contains the same software
updates. Please post the error or warning report.
Please try to install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters:
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

"Error: 0x800705B4. This operation returned because the timeout period expired"

Hello,
I deployed security updates Mid October 201, however some clients failed to install with the error "0x800705B4 this operation returned because the timeout period expired when installing updates".
Although, i saw an article but this did not address the issue. It was advised i temporarily disable any third party antivirus software and firewall.
Unfortunately, we use SEP antivirus and any attempt to disable it would yanck the clients off the network. Windows Firewall is also disabled on these clients.
Can anyone help urgently?

Hi,
What's the status in Software Center about the updates?
Have you checked SCCM updates logs on the clients?
http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
Please also check the boundary groups associated with DPs have been configured correctly.
Best Regards,
Joyce
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.

Windows 2008 R2 Failover Clustering Issue - The operation returned because the timeout period expired.

I am trying to get a new Windows 2008 R2 cluster to work on two VMware servers (VMware ESXi 5.0.3) and am experiencing some form of timeout issue during the creation of the cluster according to the logs.
All validation checks pass successfully, whether trying to create a single node or dual node cluster, but the same error message is seen when creating the cluster. I have tried various suggestions found but none of them have made a difference. In an effort
to further diagnose the issue I enabled the following diagnostic logs:
- FailoverClustering
- FailoverClustering-Manager
- FailoverClustering-Client
The only useful error I can find is in the FailoverClustering-Client log which reports an error 'Couldn't resolve tcp binding to cluster' for each physical node to be part of the cluster.
In order to further diagnose the cause of the issue, I am looking for any options for increasing logging when attempting to create the cluster. Is there a way to increase the logging to see what the actual timeout is occurring with?
Alex.

Sorry, I should have been more clear ...The servers I am attempting to create a cluster with are Virtual Servers running on a VMware ESXi (5.0.3). They have access to two shared disks (connected to each VM using a separate SCSI Controller from that for the
disk used to install the OS) with Virtual SCSI Bus Sharing set within VMware.
Each Virtual Server has two NICs configured (with static IPs) - one for internal (domain connectivity) and the other for heartbeat connectivity. The servers can ping each other via both interfaces, as expected, but only domain connectivity works via the
internal NIC.
I have tried creating a single node or dual node cluster and get the same error each time. When the cluster is attempting to be created I can see the new computer object is created in Active Directory (which is then deleted when the cluster creation fails)
and I have also tried pre-creating the computer object and specifically setting permissions on it.
When creating the cluster I have tried via the GUI and via PowerShell (both with and without the option to attach the shared storage) but always get the same type of timeout error message. I am hoping there are further debugging options that can be used
to provide a better output as to what the timeout is occurring with.

VM will not boot after moving using Failover Cluster Manager - "a disk read error occurred......"

My current Configuration:
3 node cluster, using clustered shared storage and about 22 VM's.   The Host servers are running 2012 Data Center while all guest are running 2012 Standard. The SAN is EqualLogic and we are using HIT Kit 4.5.
I have a CSV that is running out of space, so I created another CSV so that I could move some of the VM's to a new home.    I tested this by creating a test VM, and moved it successfully 3 times.     I then moved an actual
LIVE VM and while it seemed to move ok, it will now not start.   The message is "a disk read error occurred Press ctrl+alt+del to restart".     I moved the test VM and it failed as well.
I have read several things about this, but nothing seems to relate to my specific issue.   I have verified that VSS is working and free of errors as well.    From the Settings menu for the VM, if I select "Inspect" the drive,
the properties all look fine.    It is a VHDX and both the current file size and maximum disk size seem correct.
The VM's were moved using the "move - virtual machine storage" option within Failover Cluster Manager.
Suggestions?
Thanks.

Lets see if I can answer all of those and I appreciate the brain storming.   This really needs to work, correctly.
1. The Storage is moving.
2.   VM's and SAN are on same device.
3. No, my Clustered Shared Volume, CSV, is out of room, (more one that later)
4. No, I actually have 2 sans grouped together.   However, I'm moving the VM', form one CSV to another CSV on the Same san. EqualLogic PS 6110 is the one I am trying to move VMS around on, and the other SAN not involved in any way except
for it is in a SAN group is an EqualLogic PS6010.
5. No error During move, it took about 5-10 minutes, no error messages.   Note, I did a test and it worked GREAT 3 times.   Now both a live VM, and the test VM are doing the same thing.
6. No, the machine is not to large.   The test making was a 50 gig drive, just 2012 standard installed with updates.   The live VM was a 75 gig VM that was my Trend Micro Server, or anti-virus host.
7. Expand the existing SCV?   Yes I should be able to, but there is an issue there.   The volume was expanded correctly, Equallogic sees the added space, Fail Over cluster manager sees the added space, however disk manager only
sort of does.    When looking at disk manager, there are 2 areas that tell you a little bit about the drive.   The top part and then the bottom part.   The top part only shows 500G, the original size, while the bottom part
says that it is 1 TB in size.   I call Dell's technical support and after they looked at it I was told by the technician that they had seen this a couple of times and the only way to fix it was to move all the VM's to another CSV and delete the troubled
CSV.   I thought about adding more space to the troubled CSV, but its on a production server with about 12 VM's running on it and I did not want to take a chance.   The Trend VM was running on CSV-1 and working fine.
I must admit that the test VM, was on CSV-2.    I moved the Test VM from csv-2 to csv-3 back and forth several times with no errors.   The Trend Server was on CSV-1 and was moved to CSV-3, however it failed. Again, I then moved
the test VM from CSV-2 to CSV-3 and it failed the same way.   I could not test the "TEST - VM" on csv-1 due to csv-1 not having enough space.
8.   I did disable the network from the VM to see if that mattered it did not.
9.   I have not yet had a chance to connect the VHDX to a new VM, but I will do that in about an hour, hopefully.    Once I am able to test that suggestion I will post the results as well.
Again, thanks for all the suggestions and comments, as I had rather have lots to look at and try.   I hope I answered them well enough.
Kenny

Getting error 'proc_createNewAppSiteDomainIds' when I try to install SharePoint on Windows Server 2012

I have a Windows Server 2012 setup with SQL 2012 SP1 installed. I have tried to install Sharepoint Foundation 2013 and also full blown Sharepoint version...but during the wizard setup I always get 'Cannot find the object 'proc_createNewAppSiteDomainIds',
because it does not exist or you do not have permission.
The install created my db in sql 'team1p-vm' but that is it.
What am I missing?
During the install I have tried both Complete and Stand-alone as the Server Type.
When it gets to the product configuration wizard I use:
Create a new server farm
I enter my database server name: team1p-vm
Database name: SharePoint_Config
I enter my db access account
I enter a farm security settings passphrase
I use 17012 as my port number, select NTLM
I see my configuration settings...
Click Next and I get the error on task 3 of 10.
here is the dump of the application Log: At least some of it.
An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Cannot find the object 'proc_createNewAppSiteDomainIds', because it does not exist or you do not have permission.
System.Data.SqlClient.SqlException (0x80131904): Cannot find the object 'proc_createNewAppSiteDomainIds', because it does not exist or you do not have permission.

Can you see if there is anything in the SQL ERRORLOG on the SQL Server that may help at the time you see this error?
Does your user account (the user you're installing SharePoint with) have the sysadmin fixed role in SQL Server?
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Error: Invalid Parameter when trying to extend volume in Windows Server 2012

From VMware, I added space to a Hard Drive to a Windows Server 2012 VM. I then went into the WinServer console, and opened Disk Management. I did a rescan on the disk. It found the extra space. I right mouse click on the Disk,
and choose Extend Volume, choose the available space, and then an error returned of 'Invalid Parameter'.
In Disk Manager, the new larger space is assigned, but Windows Explorer and everything else only recognizes the original smaller size.
EventManager shows Event ID 265: A pointer device did not report a valid unit of angular measurement. Event ID 257: A pointer device reported a bad angular physical range. Event ID 258: A pointer device reported a bad angular logical range.
Anyone have a solution for this problem?

Hi,
Please try to use the command line utility diskpart to extend the drive.
1. Open a command prompt
2. Type in diskpart
3. Type list volume
4. Type select volume #
5. Type extend [size=n] [disk=n]
For more detailed information about diskpart, please see:
DiskPart Command-Line Options
http://technet.microsoft.com/en-us/library/cc766465(v=ws.10).aspx
You could refer to the article below to troubleshoot the issue:
Windows Server 2008 drive doesn’t expand correctly after extending in VMware VI client
http://consultingblogs.emc.com/greggrobertson/archive/2010/05/27/windows-server-2008-drive-doesn-t-expand-correctly-after-extending-in-vmware-vi-client.aspx
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
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.

Setup Error 1603 with Exchange 2013 incl. SP1 on Windows Server 2012 R2

Hello all,
i've started the installation of a new Exchange 2013 with SP1 in a Windows 2012 R2 environment. New AD, no Exchange previously installed. Exchange ISO from
Volume Licensing Service Center (Filename: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118.iso)
All the prerequisites are ok, installed also the “Unified Communications Managed API (UCMA) 4.0″ as requested.
Setup.exe i've started with "run as administrator" and all went well, until Step 11 of 15 (Mailbox role:Mailbox service).
Setup stopped and gives an error:
The following error was generated when "$error.Clear();
Install-MsiPackage `
-PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi")) `
-PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
-LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-nb-NO.msilog"))
" was run: "Installing product F:\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The cabinet file 'EngineInstanceData.cab'
required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.'.".
Exchange ECP is not working (HTTP Error 404.0 - Not Found), EMS (Shell) is working - if i try a get-mailboxserver it gives me the correct servername.
Exchange Services are running:
Running MSExchangeADTop... Microsoft Exchange Active Directory...
Running MSExchangeAntis... Microsoft Exchange Anti-spam Update
Running MSExchangeDelivery Microsoft Exchange Mailbox Transpor...
Running MSExchangeDiagn... Microsoft Exchange Diagnostics
Running MSExchangeEdgeSync Microsoft Exchange EdgeSync
Running MSExchangeHM Microsoft Exchange Health Manager
Stopped MSExchangeIMAP4BE Microsoft Exchange IMAP4 Backend
Running MSExchangeIS Microsoft Exchange Information Store
Running MSExchangeMailb... Microsoft Exchange Mailbox Replication
Running MSExchangeMigra... Microsoft Exchange Migration Workflow
Stopped MSExchangePOP3BE Microsoft Exchange POP3 Backend
Running MSExchangeRPC Microsoft Exchange RPC Client Access
Running MSExchangeServi... Microsoft Exchange Service Host
Running MSExchangeSubmi... Microsoft Exchange Mailbox Transpor...
Running MSExchangeTrans... Microsoft Exchange Transport
Running MSExchangeTrans... Microsoft Exchange Transport Log Se...
Running MSExchangeUM Microsoft Exchange Unified Messaging
So, how to proceed ? Try to download a new ISO for Exchange 2013 incl. SP1 and run the setup again ?
What happens to the existing (corrupt) installation of the exchange which is not working ?
Thanks for your help
Bruno

Hi,
From the error message, the cabinet file 'EngineInstanceData.cab' required for this installation is corrupt and cannot be used. I'm afraid you have to download a new ISO for Exchange 2013 incl. SP1 and run the setup again.
If it still doesn't work, I recommend you remove the failed Exchange server installation, then re-install Exchange server.
Best regards,
Belinda
Belinda Ma
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.

Error in creating Failover Clutser - Windows Server 2012 R2

Hello,
I have created a single node Failover Cluster in Windows Server 2012 R2. When I am trying to add second node to this cluster, it gives the error: “Cluster
service on node Node1did not reach the running state. The error code is 0x5b4. For more information check the cluster log and the system event log from node Node1. This operation returned because the timeout period expired.
The server 'Node1.mydomain.com' could not be added to the cluster.
An error occurred while adding node 'Node1.mydomain.com' to cluster 'My_Cluster'.
This operation returned because the timeout period expired.”
I have attached the screenshots of Event ID.
Firewalls are turned off on both servers (Node1 and Node2). I have successfully created single node clusters on both servers, but when I try to add second node, it
gives error.
Before starting the creation of new cluster I don't forget to Destroy previous cluster and run "Clear-ClusterNode".
Every time they successfully pass the Validate Configuration Test, but give the error on creating failover cluster.
I'm using the service account which has full permissions on CNU and both nodes, plus it has permissions to create computer accounts in AD.
Can anyone please help?
Thank you.
Best regards,
Hasan Bin Hasib

Thank you fellows!
The issue just resolved when I moved the Node1 and Node2 on the same host, and the cluster was successfully created.
After the creation of cluster, as soon as I moved the Node2 to some other host, then the Failover Cluster Manager console started showing Node2 is Down. Error: Cluster node Node2 could not to join the cluster because it failed
to communicate over the network with any other node in the cluster. Verify the network connectivity and configuration of any network firewalls. Event ID: 1653
IP Address of Node1: 172.16.1.186 ; IP Address of Node2: 172.16.1.187
And yes, the ‘Microsoft Failover Cluster Virtual Adapter Performance Filter’ is already disabled on all virtual adapters. All firewalls are disabled, no antivirus installed. I’m using same type of NICs.
I don’t know where the blockage is, and I am badly stuck. Please help.
Thank you.
~ Hasan Bin Hasib

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.

Missing a VM in Failover Cluster Manager

We did eventually cut the power when shutting down the second of the two hosts in the cluster, because it got stuck at some stage during shutdown. The reason we shut down was that there were problems piling up while we moved VMs between the two nodes.
After boot, we no longer see one of the virtual machines in the Failover Cluster Manager. In Hyper-V Manager we see it, and it runs just fine.
How can we add the missing VM back in Failover Cluster Manager? Is there a simple way?
All the servers are Win 2008 R2.
Maybe a simple question - I don't know - but we just don't have enough knowledge right now, nor has searching the net resulted in anything useful. Appreciate a bit of help holding our heads above water while we learn to swim.
Bent Tranberg

You mean what I see in Cluster Events in Failover Cluster Manager? I saved it, opened it in Event Viewer, and saved it as tab delimited text. Is that ok?
I have removed the text after the event IDs whenever the text was exactly identical to the preceding event with the same event ID, to shorten my post. I also cut away a long list of repetitive events where you see the ellipsis'.
Level Date and Time
Source Event ID
Task Category
Error 05.01.2012 10:25:15
Microsoft-Windows-FailoverClustering
1205 Resource Control Manager
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Error 05.01.2012 10:25:15
Microsoft-Windows-FailoverClustering
1069 Resource Control Manager
Cluster resource 'Cluster IP Address' in clustered service or application 'Cluster Group' failed.
Error 05.01.2012 10:25:15
Microsoft-Windows-FailoverClustering
1049 IP Address Resource
Cluster IP address resource 'Cluster IP Address' cannot be brought online because a duplicate IP address '10.10.1.16' was detected on the network. Please ensure all IP addresses are unique.
Error 05.01.2012 10:25:07
Microsoft-Windows-FailoverClustering
1069
Error 05.01.2012 09:24:43
Microsoft-Windows-FailoverClustering 1205
Error 05.01.2012 09:24:43
Microsoft-Windows-FailoverClustering
1069
Error 05.01.2012 09:24:43
Microsoft-Windows-FailoverClustering
1049
Error 05.01.2012 09:24:35
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 14:04:33
Microsoft-Windows-FailoverClustering 1205
Error 04.01.2012 14:04:33
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 14:04:33
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 14:04:25
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 14:04:25
Microsoft-Windows-FailoverClustering
1049
Critical 04.01.2012 13:59:40
Microsoft-Windows-FailoverClustering
1135 Node Mgr
Cluster node 'VSH2' 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.
Error 04.01.2012 13:06:52
Microsoft-Windows-FailoverClustering
1205
Error 04.01.2012 12:00:38
Microsoft-Windows-FailoverClustering 1205
Error 04.01.2012 12:00:38
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 12:00:37
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 12:00:25
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 12:00:25
Microsoft-Windows-FailoverClustering
1049
Critical 04.01.2012 11:54:36
Microsoft-Windows-FailoverClustering
1146 Resource Control Manager
The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource
vendor.
Error 04.01.2012 11:54:36
Microsoft-Windows-FailoverClustering
1230 Resource Control Manager
Cluster resource 'SCVMM AP Configuration' (resource type '', DLL 'vmclusres.dll') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.
Critical 04.01.2012 11:49:35
Microsoft-Windows-FailoverClustering
1146
Error 04.01.2012 11:49:35
Microsoft-Windows-FailoverClustering
1230
Critical 04.01.2012 11:44:33
Microsoft-Windows-FailoverClustering
1146
Error 04.01.2012 11:34:23
Microsoft-Windows-FailoverClustering
1205
Error 04.01.2012 11:34:23
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 11:34:23
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 11:24:22
Microsoft-Windows-FailoverClustering 1069
Critical 04.01.2012 11:24:22
Microsoft-Windows-FailoverClustering
1564 File Share Witness Resource
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\sm\QuorumFolder_Do_Not_Delete'. Please ensure that file share '\\sm\QuorumFolder_Do_Not_Delete' exists and is accessible by the cluster.
Error 04.01.2012 11:24:21
Microsoft-Windows-FailoverClustering
1069
Warning 04.01.2012 11:24:21
Microsoft-Windows-FailoverClustering
1562 File Share Witness Resource
File share witness resource 'File Share Witness' failed a periodic health check on file share '\\sm\QuorumFolder_Do_Not_Delete'. Please ensure that file share '\\sm\QuorumFolder_Do_Not_Delete' exists and is accessible by the cluster.
Error 04.01.2012 11:23:39
Microsoft-Windows-FailoverClustering
1069 Resource Control Manager
Cluster resource 'SCVMM vs2005Bent' in clustered service or application 'SCVMM vs2005Bent Resources' failed.
Error 04.01.2012 11:19:39
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 11:19:19
Microsoft-Windows-FailoverClustering
1069
Critical 04.01.2012 11:05:36
Microsoft-Windows-FailoverClustering
1135 Node Mgr
Cluster node 'VSH2' 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.
Critical 04.01.2012 10:48:51
Microsoft-Windows-FailoverClustering
1135
Critical 04.01.2012 10:41:47
Microsoft-Windows-FailoverClustering
1135
Error 04.01.2012 10:33:51
Microsoft-Windows-FailoverClustering
1205
Error 04.01.2012 10:33:51
Microsoft-Windows-FailoverClustering
1069
Error 04.01.2012 10:33:51
Microsoft-Windows-FailoverClustering
1049
Error 04.01.2012 08:33:10
Microsoft-Windows-FailoverClustering 1069
Error 04.01.2012 08:33:10
Microsoft-Windows-FailoverClustering
1049
Bent Tranberg

Windows Server 2012 - Hyper-V - Cluster Sharded Storage - VHDX unexpectedly gets copied to System Volume Information by "System", Virtual Machines stops respondig

We have a problem with one of our deployments of Windows Server 2012 Hyper-V with a 2 node cluster connected to a iSCSI SAN.
Our setup:
Hosts - Both run Windows Server 2012 Standard and are clustered.
HP ProLiant G7, 24 GB RAM. This is the primary host and normaly all VMs run on this host.
HP ProLiant G5, 20 GB RAM. This is the secondary host that and is intended to be used in case of failure of the primary host.
We have no antivirus on the hosts and the scheduled ShadowCopy (previous version of files) is switched off.
iSCSI SAN:
QNAP NAS TS-869 Pro, 8 INTEL SSDSA2CW160G3 160 GB i a RAID 5 with a Host Spare. 2 Teamed NIC.
Switch:
DLINK DGS-1210-16 - Both the network cards of the Hosts that are dedicated to the Storage and the Storage itself are connected to the same switch and nothing else is connected to this switch.
Virtual Machines:
3 Windows Server 2012 Standard - 1 DC, 1 FileServer, 1 Application Server.
1 Windows Server 2008 Standard Exchange Server.
All VMs are using dynamic disks (as recommended by Microsoft).
Updates
We have applied the most resent updates to the Hosts, VMs and iSCSI SAN about 3 weeks ago with no change in our problem and we continually update the setup.
Normal operation:
Normally this setup works just fine and we see no real difference in speed in startup, file copy and processing speed in LoB applications of this setup compared to a single host with two 10000 RPM Disks. Normal network speed is 10-200 Mbit, but occasionally
we see speeds up to 400 Mbit/s of combined read/write for instance during file repair.
Our Problem:
Our problem is that for some reason a random VHDX gets copied to System Volume Information by "System" of the Clusterd Shared Storage (i.e. C:\ClusterStorage\Volume1\System Volume Information).
All VMs stops responding or responds very slowly during this copy process and you can for instance not send CTRL-ALT-DEL to a VM in the Hyper-V console, or for instance start task manager when already logged in.
This happens at random and not every day and different VHDX files from different VMs gets copied each time. Some time it happens during daytime wich causes a lot of problems, especially when a 200 GB file gets copied (which take a lot of time).
What it is not:
We thought that this was connected to the backup, but the backup had finished 3 hours before the last time this happended and the backup never uses any of the files in System Volume Information so it is not the backup.
An observation:
When this happend today I switched on ShadowCopy (previous files) and set it to only to use 320 MB of storage and then the Copy Process stopped and the virtual Machines started responding again. This could be unrelated since there is no way to see
how much of the VHDX that is left to be copied, so it might have been finished at the same time as I enabled ShadowCopy (previos files).
Our question:
Why is a VHDX copied to System Volume Information when scheduled ShadowCopy (previous version of files) is switched off? As far as I know, nothing should be copied to this folder when this functionis switched off?
List of VSS Writers:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error
Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error
Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {7848396d-00b1-47cd-8ba9-769b7ce402d2}
   State: [1] Stable
   Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {8b6c534a-18dd-4fff-b14e-1d4aebd1db74}
   State: [5] Waiting for completion
   Last error: No error
Writer name: 'Cluster Shared Volume VSS Writer'
   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Writer Instance Id: {d46c6a69-8b4a-4307-afcf-ca3611c7f680}
   State: [1] Stable
   Last error: No error
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {fc530484-71db-48c3-af5f-ef398070373e}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {3792e26e-c0d0-4901-b799-2e8d9ffe2085}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {6ea65f92-e3fd-4a23-9e5f-b23de43bc756}
   State: [1] Stable
   Last error: No error
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {71dc7876-2089-472c-8fed-4b8862037528}
   State: [1] Stable
   Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {cb0c7fd8-1f5c-41bb-b2cc-82fabbdc466e}
   State: [1] Stable
   Last error: No error
Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {23320f7e-f165-409d-8456-5d7d8fbaefed}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f23d0208-e569-48b0-ad30-1addb1a044af}
   State: [1] Stable
   Last error: No error
Please note:
Please only answer our question and do not offer any general optimization tips that do not directly adress the issue! We want the problem to go away, not to finish a bit faster!

Hallo Lawrence!
Thankyou for youre reply, some comments to help you and others who read this thread:
First of all, we use Windows Server 2012 and the VHDX as I wrote in the headline and in the text in my post. We have not had this problem in similar setups with Windows Server 2008 R2, so the problem seem to be introduced in Windows Server 2012.
These posts that you refer to seem to be outdated and/or do not apply to our configuration:
The post about Dynamic Disks:
http://technet.microsoft.com/en-us/library/ee941151(v=WS.10).aspx is only a recommendation for Windows Server 2008 R2 and the VHD format. Dynamic VHDX is indeed recommended by Microsoft when using Windows Server 2012 (please look in the optimization guide
for Windows Server 2012).
Infact, if we use fixed VHDX then we would have a bigger problem since fixed VHDX are generaly larger then Dynamic Disks, i.e. more data would be copied and that would take longer time = the VMs would be unresponsive for a longer time.
The post "What's the deal with the System Volume Information folder"
http://blogs.msdn.com/b/oldnewthing/archive/2003/11/20/55764.aspx is for Windows XP / Windows Server 2003 and some things has changed since then. for instance In Windows Server 2012, Shadow Copies cannot be controlled by going to Control panel -> System.
Instead you right-click on a Drive (i.e. a Volume, for instance the C drive/Volume) in Computer and then click "Configure Shadow Copies".
Windows Server 2008 R2 Backup problem
http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/0fc53adb-477d-425b-8c99-ad006e132336 - This post is about the Antivirus software trying to scan files used during backup that exists in the System Volume Information folder and we do not
have any antivirus software installed on our hosts as I stated in my post.
Comment that might help us:
So according to “System Volume Information” definition, the operation you mentioned is Volume Shadow Copy. Check event viewer to find Volume Shadow Copy related event logs and post them.
Why?
Furhter investigation suggests that a volume shadow copy is somehow created even though the Schedule for Shadows Copies is turned off for all drives. This happens at random and we have not found any pattern. Yesterday this operation took almost all available
disk space (over 200 GB), but all the disk space was released when I turned on scheduled Shadow Copies for the CSV.
I therefore draw these conclusions:
The CSV Volume has about 600 GB of disk space and since Volume Shadows Copy used 200 GB, or about 33% of the disk space, and the default limit is 10% then I conclude that for some reason the unscheduled Volume Shadow Copy did not have any limit (or ignored
the limit).
When I turned on the Schedule I also change the limit to the minimum amount which is 320 MB and this is probably what released the disk space. That is, the unscheduled Volume Shadow Copy operation was aborted and it adhered to the limit and deleted the
Volume Shadow Copy it had taken.
I have also set the limit for Volume Shadow Copies for all other volumes to 320 MB by using the "Configure Shadow Copies" Window that you open by right clicking on a drive (volume) in Computer and then selecting "Configure Shadow Copies...".
It is important to note that setting a limit for Shadow Copy Storage, and disabaling the Schedule are two different things! It is possible to have unlimited storage for Shadow Copies when the Schedule is disabled, however I do not know if this was the case
Before I enabled Shadow Copies on the CSV since I did not look for this.
I now have defined a limit for Shadow Copy Storage to 320 MB on all drives and then no VHDX should be copied to System Volume Information since they are all larger than 320 MB.
Does this sound about right or am I drawing the wrong conclusions?
Limits for Shadow Copies:
Below we list the limits for our two hosts:
"Primary Host":
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Shadow Copy Storage association
   For volume: (\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\)\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\
   Shadow Copy Storage volume: (\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\)\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 320 MB (91%)
Shadow Copy Storage association
   For volume: (E:)\\?\Volume{dc0a177b-ab03-44c2-8ff6-499b29c3d5cc}\
   Shadow Copy Storage volume: (E:)\\?\Volume{dc0a177b-ab03-44c2-8ff6-499b29c3d5cc}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 320 MB (0%)
Shadow Copy Storage association
   For volume: (G:)\\?\Volume{f58dc334-17be-11e2-93ee-9c8e991b7c20}\
   Shadow Copy Storage volume: (G:)\\?\Volume{f58dc334-17be-11e2-93ee-9c8e991b7c20}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 320 MB (3%)
Shadow Copy Storage association
   For volume: (C:)\\?\Volume{e3ad7fec-178b-11e2-93e8-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{e3ad7fec-178b-11e2-93e8-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 320 MB (0%)
C:\>cd \ClusterStorage\Volume1
Secondary host:
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Shadow Copy Storage association
   For volume: (\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\)\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\
   Shadow Copy Storage volume: (\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\)\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 35,0 MB (10%)
Shadow Copy Storage association
   For volume: (D:)\\?\Volume{5228437e-9a01-4690-bc40-1df85a0e6736}\
   Shadow Copy Storage volume: (D:)\\?\Volume{5228437e-9a01-4690-bc40-1df85a0e6736}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 27,3 GB (10%)
Shadow Copy Storage association
   For volume: (C:)\\?\Volume{b2951139-f01e-11e1-93e8-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{b2951139-f01e-11e1-93e8-806e6f6e6963}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: 6,80 GB (10%)
C:\>
There is something strange about the limits on the Secondary host!
I have not in any way changed the settings on the Secondary host and as you can see, the Secondary host has a maximum limit of only 35 MB storage on the CSV, but it also shows that this is 10% of the Volume. This is clearly not the case since 10% if 600
GB = 60 GB!
The question is, why does it by default set a too small limit (i.e. < 320 MB) on the CSV and is this the cause of the problem? I.e. is the limit ignored since it is smaller than the smallest amount you can provide using the GUI?
Is the default 35 MB maximum Shadow Copy limit a bug, or is there any logical reason for setting a limit that according to the GUI is too small?

Adobe 10 error #1460 - Timeout period expired

We have been having a problem with saving documents since the upgrade to Adobe 10. If the document is not saved fast enough,
we get the timeout period expired error #1460. Is there some way to adjust this timeperiod?

http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5b439fe-1aa9-4823-a3ac-d0be643a5073/query-using-ad-module-timed-out?forum=winserverDS
has some more information on this, though I don't know if there were any improvements to the AD Module in the last year that might change this situation.
Long story short, the AD module is good for small scale, but beyond that, you might be better off using the System.DirectoryServices classes for better performance and finer control.

Windows server 2012 R2 PXE boot is unworkable slow, I have this exact same set-up working in 2008 R2 What can I do?

Hi there
I'm trying to deploy a windows 7 image through Windows deployment services via PXE boot from a 2012 R2 server.
Issue: PXE boot is extremely slow, it takes up to more than 60 minutes for the device to download download the PXE boot
Things I already tried to get this up and running:
I've tried to change the TFTP block size via command prompt and via regedit
I've changed the settings on the tab of the WDS role (go to WDS role -> properties on server -> Tab "tftp")
Both actions resulted in PXE boot being even slower than it already was.
To make sure this is not because of our environment I’ve set up the same configuration on a windows server 2008 R2, here PXE boot image is downloaded to the machine within 3 minutes.
Both servers are set up through Hyper-V this is the configuration:
2008 R2:
Memory: 4096 MB
1 Virtual processor
IDE controller 2 hard drives
Network adapter
2012 R2:
Memory: 4096 MB
32 virtual processors
SCSI controller 2 hard drives
Network adapter
I can’t imagine that PXE boot is not working because of the differences of the Hard drives controllers or because of the amount of the virtual processors.
Windows server 2012 R2 seems to handle PXE boot TFTP differently in comparison to 2008 R2.
Do you guys know what I can do/try to get this working?

Hi Jacques Rodrigues,
You can run Windows Deployment Services on Hyper-V virtual machines,
that the performance will often be degraded, particularly during the Trivial File Transfer Protocol (TFTP) download phase. This phase is very resource-intensive and may
fail if insufficient resources are available on your server running Hyper-V.
If you are using multicast, Check if IGMP Snooping is enabled i.e. Routers that support multicasting. In particular, Internet Group Membership Protocol (IGMP) snooping should
be enabled on all devices. This will cause your network hardware to forward multicast packets only to those devices that are requesting data. If IGMP snooping is turned off, multicast packets are treated as broadcast packets, and will be sent to every device
in the subnet.
The related KB:
Windows Deployment Services Overview
http://technet.microsoft.com/en-us/library/hh831764.aspx
I’m glad to be of help to you!
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.

Can't add VM to Failover Cluster Manager

I have two VMs: a virtual DC and a virtual SCVMM. I opened up a Failover Cluster Manager and tried to add both machines. The DC added successfully but I can't get the SCVMM to add.
The error is:
"There was a failure configuring the virtual machine role for '<my_machine_name>'
The RASD '\\<cluster>\\root\virtualization\V2:Msvm_ResourceAllocationSettingData.InstanceID="Microsoft:BBA1664E-07AB-41FA-B3B4-DBA795117449\\663F3FFA-8784-4E92-9A9B-99FC3D705BAC\\0\\0\\D" is not a valid disk type."
I have no idea what this error is trying to tell me...any help would be greatly appreciated!

Thank you for your response.
I double-checked and the VM is located on the shared cluster container. I went into Hyper-V Manager and looked at the paths and both the virtual machine and virtual hard disks are in the cluster container.
I have two VM XML files in the cluster container which I've noted with their GUIDs. For a sanity check, I also went into the specific host and navigated to C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines and found that the same XML files
there too. Should those be there? They are both there so I don't see why I could add the virtual DC but not my virtual SCVMM.

Failover Cluster Manager : Add node wizard Error " This operation returned because the timeout period expired" Windows Server 2012

Similar Messages

Maybe you are looking for