So, again, another issue that is meant to be fixed by SP1, isnt.......................
Currently I have a DAG member that is reporting as offline, failed......
Dont msft test anything anymore?????
Gaz
23 May 2011 3:52 PM
23 May 2011 3:55 PM
@GAZ
Are you sure your issue is not fixed by SP1. We have had no reported cases of any issues post SP1 when the instructions are followed. As a reminder, if you had the issue pre-SP1 SP1 alone does not fix the issue, the workaround must be followed. The issue is simply prevented from re-occuring.
Also - just becuase you have a resource offline does not mean you have this issue - there are multiple reasons a resource maybe reporting offline.
TIMMCMIC
7 Jul 2011 5:46 PM
I have a two node Exchange SP1 DAG, and have just noticed this error. My two servers are clean Exchange SP1 installs.
Whilst all appears to be OK with the DAG, seeing the "resource offline" error in the Failover Cluster Manager is a little disconcerting.
I attempted to amend the settings for "Cluster Network 2" and check the “Allow clients to connect through this network” box but each time I apply the setting and then go back into the netowrk properties, the box is unticked again.
The powershell and cluster.exe commands didn't work for me either.
I have managed to bring the cluster online however, by manually changing the "Role"=dword:00000001 in the registry (as described above) to "Role"=dword:00000003.
After doing this, I have managed to bring the resource online successfully.
BlackCat
4 Oct 2011 1:44 PM
I had the same experience as @MattP_75, I had to change the role in registry: http://lokna.no/?p=998
19 Jun 2012 6:19 PM
The solutions above do not work. I do not have SP1 installed yet.
When bringing the IP ADDRESS online I get error code: 0x80071737
When bringing the dag name online I get: Error code: 0x80071736 The resource failed to com online due to the filure of one or more provider resources.
Any other fixes for this?
22 Jun 2012 10:14 PM
@mfahey
Assuming you actually have this issue if you followed the workaround then you should have been fine. Take a look at my collapsing DAG networks blog post as this could be another reason your cluster networks are not maintained correctly.
TIMMCMIC
30 Sep 2012 7:56 AM
@Tim,
We're still encountering this problem numerous times in SP2 with Update Rollup 4. We've to manually bring the cluster online!
30 Sep 2012 1:47 PM
@Sadda:
If you can bring the cluster core resources online then this is not your issue. This issue would prevent you from manually brining the cluster core resources online.
I would suggest reviewing the application and system logs for events regarding the cluster core resources.
TIMMCMIC
Corbett
29 May 2013 5:38 PM
I had the same problem where the cluster IP Address wouldn't come online. I tried the workaround but it didn't seem to make a difference. It wasn't until I changed the setting to "Do not allow cluster network communication on this network" that the cluster was able to come online. After changing that setting it must have reset the network because it immediately went to an online state and the setting was reverted back to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
Corbett
29 May 2013 5:39 PM
Oh, and this was with Exchange 2010 SP2.
jash
23 Jul 2013 9:21 AM
I also have the same issue. I have exchange 2010 Sp3 RU1 on the server. when i tried to select the "Allow clients to connect through this network" option and click ok.
after few second it again deselect the option automatically. I dont know why this is misbehaving.
James
6 Aug 2013 8:17 AM
My exchange 2010 SP1 dag went down on one network only, saying it could not comunicate on this network. "•Uncheck the box to “Allow clients to connect through this network”. and recheck worked for me.
James
6 Aug 2013 8:20 AM
Also fixed partitioned network and event ID's 1129, 1126 and 1564
21 Aug 2013 2:29 AM
@James:
We do not expect this to fix any underlying cluster network communications problems.
TIMMCMIC
Rahamat
9 Sep 2013 1:43 PM
I have Exchange 2010 SP3 RU1 with DAG and see the same issue where the resource would not come online. Any fix for this?