[Case sharing] 41131 error when building SQL AlwaysOn on Azure IaaS vm

Source: Internet
Author: User

Tags: azure;sql;always;on;41131;wsfc

Azure environment: 1 dc+2 SQL 2012 (with SQL VM in library, not VM self-built SQL Server)


In the AlwaysOn Wizard, this error message appears:

Failed to bring availability Group ' HADB ' online. The operation timed out. Verify The local Windows Server Failover Clustering (WSFC) node is online. Then verify, the availability group resource exists in the WSFC cluster. If the problem persists, you might need to drop the availability group and create it again.

Failed to create Availability group ' HADB '.  The operation encountered SQL Server error 41131 and have been rolled back.  Check the SQL Server error log for more details. When the cause of the error has been resolved, retry CREATE availability GROUP command. (Microsoft SQL Server, error:41131)



Use [Master]gocreate LOGIN [NT Authority\System] from WINDOWS with Default_database=[master]go
GRANT ALTER any availability GROUP to [NT Authority\system]gogrant CONNECT SQL to [NT Authority\system]gogrant VIEW SERVER State to [NT Authority\system]go

PS: In the IaaS VM deployment AlwaysOn Note Oh, manually configure the cluster IP after the cluster is created.

This article from "Gs_hao" blog, declined reprint!

[Case sharing] 41131 error when building SQL AlwaysOn on Azure IaaS vm

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

Tags Index: