SQL Server Errors or Failures from Error: 35257 to Error: 35279

SQLServerF1

Error: 35257, Severity: 16, AlwaysOn Availability Groups Send Error (Error code 0x%X, “NOT OK”) was returned when sending a message for database ID %d. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters

Error: 35259, Severity: 16, Database ‘%.*ls’ is already participating in a different availability group.
Error: 35260, Severity: 16, During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and group database ID %ls. Recovery was terminated. The most likely cause of this error is that the availability group
Error: 35261, Severity: 16, Attempt to perform an AlwaysOn Availability Groups operation on a system database, ‘%ls’, failed. System databases are not supported by AlwaysOn Availability Groups.

Error: 35262, Severity: 17, Skipping the default startup of database ‘%.*ls’ because the database belongs to an availability group (Group ID: %d). The database will be started by the availability group. This is an informational message only. No user action is required.
Error: 35263, Severity: 16, During the undo phase, a function call (%ls) to the primary replica returned an unexpected status (Code: %d). Check for a possible cause in the SQL Server error log for the primary replica. If an error occurred on the primary database, you might need to s
Error: 35264, Severity: 10, AlwaysOn Availability Groups data movement for database ‘%.*ls’ has been suspended for the following reason: “%S_MSG” (Source ID %d; Source string: ‘%.*ls’). To resume data movement on the database, you will need to resume the database manually. For infor
Error: 35265, Severity: 10, AlwaysOn Availability Groups data movement for database ‘%.*ls’ has been resumed. This is an informational message only. No user action is required.
Error: 35266, Severity: 10, AlwaysOn Availability Groups connection with %S_MSG database established for %S_MSG database ‘%.*ls’ on the availability replica with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is
Error: 35267, Severity: 10, AlwaysOn Availability Groups connection with %S_MSG database terminated for %S_MSG database ‘%.*ls’ on the availability replica with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is r

Error: 35268, Severity: 16, Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will enter the RESTORING state. To complete recovery and bring the database online, use current log backups from the primary dat
Error: 35269, Severity: 21, Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will be marked SUSPECT. To return the database to a consistent state, restore it from a clean database backup followed by all su
Error: 35270, Severity: 10, Received a corrupt FileStream transport message. The ‘%ls’ message section is invalid.
Error: 35272, Severity: 16, Either nvalid parameters were supplied for sys.sp_availability_group_command_internal or user does not have permissions to execute this procedure.
Error: 35273, Severity: 10, Bypassing recovery for database ‘%ls’ because it is marked as an inaccessible availability database. The session with the primary replica was interrupted while reverting the database to the common recovery point. Either the WSFC node lacks quorum or the c
Error: 35274, Severity: 10, Recovery for availability database ‘%ls’ is pending until the secondary replica receives additional transaction log from the primary before it complete and come online. Ensure that the server instance that hosts the primary replica is running.
Error: 35275, Severity: 16, A previous RESTORE WITH CONTINUE_AFTER_ERROR operation or being removed while in the SUSPECT state from an availability group left the ‘%.*ls’ database in a potentially damaged state. The database cannot be joined while in this state. Restore the database
Error: 35276, Severity: 17, Failed to allocate and schedule an AlwaysOn Availability Groups task for database ‘%ls’. Manual intervention may be required to resume synchronization of the database. If the problem persists, you might need to restart the local instance of SQL Server.
Error: 35278, Severity: 16, Availability database ‘%.*ls’, which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required.
Error: 35279, Severity: 16, The attempt to join database ‘%.*ls’ to the availability group was rejected by the primary database with error ‘%d’. For more information, see the SQL Server error log for the primary replica.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *