The specified secondary replica is not currently synchronized, therefore performing failover of this availability group might result in the loss of any transaction that did not reach the secondary replica prior to the availability group failing over. To confirm the failover of the availability group '$$TypeName:AvailabilityGroup@urn$$' to the specified secondary replica '$$ssms:Name@context$$', click OK. Following successful completion of the failover operation, the new primary databases will be online, but all the secondary databases will be suspended. You will need to manually resume data movement on each of them.
The specified replica has one or more databases that are not synchronized. Failing over to this replica may result in the ...
The specified report folder is not valid. Specify a value for the TargetReportFolder property in the deployment settings. ...
The specified sa password does not meet strong password requirements. For more information about strong password requirements, ...
The specified schema name '%1!s!' for classifier user-defined function either does not exist, or the user does not have permission ...
The specified secondary replica is not currently synchronized, therefore performing failover of this availability group might ...
The specified service account is not supported. Depending on the operating systems Virtual Accounts and Managed Service Accounts ...
The specified sets in the %{func/} function have incompatible hierarchies at position %{iHier/}. The sets are incompatible. ...
The specified source object must be a user-defined aggregate object if it is published as an 'aggregate schema only' type ...
The specified source object must be a user-defined function object if it is going to be published as a 'func schema only' ...