0

I am in a process of adding databases to availability group. In one of the steps it was asking "data synchronization prefferences" as shown below

enter image description here

I have put the mapped drive location path, which was FILESHARE created in azure portal.

Now availability group validation fails as shown below, it says "Primary server '[MYNODENAME]' can not write to shared drive during availability group configuration"

enter image description here

Update

IP for listener was wrong . issue resolved .

New Error

The Windows Server Failover Clustering (WSFC) resource control API returned error code 87. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation. The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. The attempt to create the network name and IP address for the listener failed. The WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. (.Net SqlClient Data Provider)

Here is screenshot

enter image description here

  • Does the SQL Server service account have proper access to the share and folder? – Shawn Melton Mar 22 '16 at 15:13
  • Yes it has the access . read write access – kudlatiger Mar 22 '16 at 18:24
  • generally you have to have something to close to a Domain Admin account to create the Listener and IP address, you are actually updating DNS and AD at that point. Since this is all in Azure though they must have this all documented well. Start with your WSFC, run the validate to make sure it is totally healthy, and then attempt the AG set up. Sounds like your WSFC might have issues. – IanG Mar 22 '16 at 21:49
0

PORT 5022 was not added to secondary node's firewall

After adding rule, it worked like charm

This is how I found the solution

Open command prompt

     Telnet NODE2 5022 

This failed

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.