During the undo phase, a function call (%1!s!) to the primary replica returned an unexpected status (Code: %2!s!). 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 suspend the secondary database, fix the issue on the primary database, and then resume the database.
During the database upgrade process on database '%1!s!', a user object '%2!s!' named '%3!s!' was found to already exist. ...
During the database upgrade, the full-text filter component '%1!s!' that is used by catalog '%2!s!' was successfully verified. ...
During the database upgrade, the full-text protocol handler component '%1!s!' that is used by catalog '%2!s!' was successfully ...
During the database upgrade, the full-text word-breaker component '%1!s!' that is used by catalog '%2!s!' was successfully ...
During the undo phase, a function call (%1!s!) to the primary replica returned an unexpected status (Code: %2!s!). Check ...
During undo of a logged operation in database '%1!s!', an error occurred at log record ID %2!s!. The row was not found. Restore ...
During undoing of a logged operation in database '%1!s!', an error occurred at log record ID %2!s!. Typically, the specific ...
During unistall either the "INSTANCENAME" or the "INSTANCEID" setting can be specified. Retry uninstall again after removing ...
During upgrade, database raised exception %1!s!, severity %2!s!, state %3!s!, address %4!s!. Use the exception number to ...