As from above screenshots getting error about Witness Server not matching (screenshot2) I've trying running Se-DatabaseAvaliabilityGroup cmdlet but it fails (screenshot1)
WitnessShareinUse: Invalid Configuration.
I've tried changing the directory on the same server. shutdown cluster and rebooted but servers. Made sure CNO has full sharing and security permissions to the Witness server - not sure what else to do please help
I suspect rtdocs.redacted.com is not in the same forest as your mailbox servers. Please see
https://technet.microsoft.com/en-us/library/dd298065.aspx#Cr
Hello,
The above issue is might be Missing permissions in the Witness Server.
Also I would like to follow the below articles
http://exchangeserverpro.com/configure-file-share-witness-exchange-2010-database-availability-group/
http://www.techrid.com/category/exchange-server-2010/high-availability/dag/page/7/
https://technet.microsoft.com/en-us/library/dd298065.aspx#Cr
Regards,
Praveen
----------------------------------------------------------------------
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts @ Techrid.com
Praveen,
For WSF we are using the same server for our Exchange 2010 DAG enviroment. I matched the permissions for the folder exactly as for 2010 DAG that is functioning. Also Exchange Trusted Subsystem is a member of local admin group. And it is in the same location/domain/forest. I see that 2 folders in WSF were created successfully and are updating howewer I still get WitnessShareInUse as blank - I tried swtiching witness servers multiple times but result is the same which leads me to believe there is something else going on. We also have 2 2010 Exchange servers in a DAG (MAILDAG) and when I run Get-DatabaseAvailiabilityGroup cmdlet I noticed that exchange versions for 2010 and 2013 display as same version?? Please refer to the screenshotHi Alex,
Would you like to tell me the version of your Exchange server.
Based on my knowledge, this issue may occur if you are using Exchange 2013 SP1.
More details to see following KB:
http://support.microsoft.com/kb/2958430
To solve this issue, please try to upgrade to CU5 or later.
Thanks
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com
Mavis, I've installed latest rollup 6 on both servers but still getting same error. It looks like it is network related.
We have EX01 on premises and EX02 in a remote location with point to point line between two locations.
I've tripled checked all network settings MAPI Network adapter for ex1 is on 10.11.1.0/24 network MAPI for ex02 is on 10.11.13.0/24 network; REPLICATION network is 192.168.0.1/29 with .1 and .2 ips for each server. Everytime I begin to seed a database I get this error: