SQL Server Errors or Failures from Error: 41151 to Error: 41171

SQLServerF1

 

Error: 41151, Severity: 16, Error accessing the Availability Groups manager. The local Availability Groups manager has not been initialized. Wait until the Availability Groups manager is in a state that allows access, and retry the operation.
Error: 41152, Severity: 16, Failed to create availability group ‘%.*ls’. The operation encountered SQL Server error %d and has 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
Error: 41153, Severity: 16, Failed to create availability group ‘%.*ls’. The operation encountered SQL Server error %d. An attempt to roll back the operation failed. Check the SQL Server error log for more details. Then execute the DROP AVAILABILITY GROUP command to clean up any

Error: 41154, Severity: 16, Cannot failover availability group ‘%.*ls’ to this SQL Server instance. The availability group is still being created. Verify that the specified availability group name is correct. Wait for CREATE AVAILABILITY GROUP command to finish, then retry the op
Error: 41155, Severity: 16, Cannot failover availability group ‘%.*ls’ to this instance of SQL Server. The availability group is being dropped. Verify that the specified availability group name is correct. The availability group may need to be recreated if the drop operation was
Error: 41156, Severity: 16, Cannot drop availability group ‘%.*ls’ from this instance of SQL Server. The availability group is either being dropped, or the local availability replica is being removed from the availability group. Verify that the specified availability group name is
Error: 41157, Severity: 16, Cannot remove the local availability replica from availability group ‘%.*ls’ from this instance of SQL Server. The availability group is either being dropped, or the local availability replica is being disjoined. Verify that the specified availability g

Error: 41158, Severity: 16, Failed to join local availability replica to availability group ‘%.*ls’. The operation encountered SQL Server error %d and has been rolled back. Check the SQL Server error log for more details. When the cause of the error has been resolved, retry the A
Error: 41159, Severity: 16, Failed to join local availability replica to availability group ‘%.*ls’. The operation encountered SQL Server error %d. An attempt to rollback the operation failed. Check SQL Server error log for more details. Run DROP AVAILABILITY GROUP command to cl
Error: 41160, Severity: 16, Failed to designate the local availability replica of availability group ‘%.*ls’ as the primary replica. The operation encountered SQL Server error %d and has been terminated. Check the preceding error and the SQL Server error log for more details about
Error: 41161, Severity: 16, Failed to validate the Cyclic Redundancy Check (CRC) of the configuration of availability group ‘%.*ls’. The operation encountered SQL Server error %d, and the availability group has been taken offline to protect its configuration and the consistency of
Error: 41162, Severity: 16, Failed to validate sequence number of the configuration of availability group ‘%.*ls’. The in-memory sequence number does not match the persisted sequence number. The availability group and/or the local availability replica will be restarted automatical
Error: 41163, Severity: 16, An error occurred while waiting for the local availability replica of availability group ‘%.*ls’ to transition to the primary role. The operation encountered SQL OS error %d and has been terminated. Verify that the Windows Server Failover Clustering (WS
Error: 41164, Severity: 16, An error occurred while waiting for the local availability replica of availability group ‘%.*ls’ to transition to the resolving role. The operation encountered SQL OS error %d and has been terminated. Verify that the Windows Server Failover Clustering (
Error: 41165, Severity: 16, A timeout error occurred while waiting to access the local availability replica of availability group ‘%.*ls’. The availability replica is currently being accessed by another operation. Wait for the in-progress operation to complete, and then retry the
Error: 41166, Severity: 16, An error occurred while waiting to access the local availability replica of availability group ‘%.*ls’. The operation encountered SQL OS error %d, and has been terminated. Verify that the local availability replica is in the correct state, and then retr
Error: 41167, Severity: 16, An error occurred while attempting to access availability replica ‘%.*ls’ in availability group ‘%.*ls’. The availability replica is not found in the availability group configuration. Verify that the availability group and availability replica names are
Error: 41168, Severity: 16, An error occurred while attempting to access availability replica with ID ‘%.*ls’ in availability group ‘%.*ls’. The availability replica is not found in the availability group configuration. Verify that the availability group name and availability repl
Error: 41169, Severity: 16, An error occurred while attempting to access the availability group database with ID ‘%.*ls’ in availability group ‘%.*ls’. The availability database is not found in the availability group configuration. Verify that the availability group name and avail
Error: 41170, Severity: 10, Post-online processing for availability group ‘%.*ls’ has been terminated. Either post-online processing has already completed, the local availability replica is no longer the primary replica, or the availability group is being dropped. This is an infor

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.

 

SQL Server Errors or Failures from Error: 41068 to Error: 41087

SQLServerF1

Error: 41068, Severity: 16, Failed to enumerate the Windows Server Failover Clustering (WSFC) registry key (Error code %d). 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 c

Error: 41069, Severity: 16, The existence of availability group data for the availability group ‘%.*ls’ in the Windows Server Failover Clustering (WSFC) store could not be determined. The local WSFC node may be down, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROU
Error: 41070, Severity: 16, Configuration data for the availability group with Windows Server Failover Clustering (WSFC) resource ID ‘%.*ls’ is not found in the WSFC data store. The availability group may have been dropped, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILI
Error: 41071, Severity: 16, Cannot read the persisted configuration of AlwaysOn availability group with corresponding Windows Server Failover Clustering (WSFC) resource ID ‘%.*ls’. The persisted configuration is written by a higher-version SQL Server that hosts the primary availabi

Error: 41072, Severity: 16, The ID of availability group ‘%.*ls’ in local data store does not exist in the Windows Server Failover Clustering (WSFC) data store. The availability group may have been dropped but the current WSFC node was not notified. To resolve this error, try to r
Error: 41073, Severity: 16, The database ‘%.*ls’ cannot be removed from availability group ‘%.*ls’. This database does not belong to the availability group.
Error: 41074, Severity: 10, AlwaysOn: The local replica of availability group ‘%.*ls’ is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required
Error: 41075, Severity: 10, AlwaysOn: The local replica of availability group ‘%.*ls’ is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is requir

Error: 41076, Severity: 10, AlwaysOn: Availability group ‘%.*ls’ is going offline because it is being removed. This is an informational message only. No user action is required.
Error: 41077, Severity: 16, Cannot bring the Windows Server Failover Clustering (WSFC) group (ID ‘%.*ls’) online at this time. The WSFC group is not in a state that could accept the request. Please wait for the WSFC group to enter a terminal state and then retry the operation. Fo
Error: 41078, Severity: 16, Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name ‘%.*ls’, because a registry entry with the specified name does not exist. Check that the registry value name is correct, and retry the operation.
Error: 41079, Severity: 16, Cannot drop the Windows Server Failover Clustering (WSFC) group (ID or name ‘%.*ls’), because the WSFC group does not exist. Specify a valid WSFC group ID or name and retry the operation. For information about this error, see error code 5013 in “System
Error: 41080, Severity: 16, Failed to delete SQL Server instance name to Windows Server Failover Clustering node name map entry for the local availability replica of availability group ‘%.*ls’. The operation encountered SQL Server error %d and has been terminated. Refer to the SQL
Error: 41081, Severity: 16, Failed to destroy the Windows Server Failover Clustering group corresponding to availability group ‘%.*ls’. The operation encountered SQL Server error %d and has been terminated. Refer to the SQL Server error log for details about this SQL Server error
Error: 41082, Severity: 16, Failed to obtain the name of local Windows Server Failover Cluster (Error code %d). The WSFC service may not be running or may not be accessible in its current state. For information about this error code, see “System Error Codes” in the Windows Develop
Error: 41083, Severity: 16, Failed to obtain the cluster quorum resource (Error code %d). The WSFC service may not be running or may not be accessible in its current state. For information about this error code, see “System Error Codes” in the Windows Development documentation.
Error: 41084, Severity: 16, The Windows Server Failover Clustering (WSFC) cluster control API returned error code %d. The WSFC service may not be running or may not be accessible in its current state. For information about this error code, see “System Error Codes” in the Windows De
Error: 41085, Severity: 16, Failed to find a DWORD property (property name ‘%s’) of the Windows Server Failover Clustering (WSFC) (Error code %d). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For informa
Error: 41086, Severity: 16, Failed to retrieve the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify whether the ‘HKLM\Cluster\PaxosTag’ registry value exists in the WSFC registry hive.
Error: 41087, Severity: 16, Error in parsing the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might be corrupt. Verify whether the ‘HKLM\Cluster\PaxosTag’ is in the format outlined in the Microsoft Knowledge Base article KB 94771

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.

 

SQL Server Errors or Failures from Error: 35210 to Error: 35233

SQLServerF1

Error: 35210, Severity: 16, Failed to modify options for availability replica ‘%.*ls’ in availability group ‘%.*ls’. The specified availability group does not contain an availability replica with specified name. Verify that availability group name and availability replica name are c

Error: 35211, Severity: 16, The %ls operation is not allowed. The operation attempted to change the configuration of availability replica ‘%.*ls’ to the asynchronous-commit availability mode with automatic failover, which is an invalid configuration. Either change the failover mod
Error: 35212, Severity: 16, The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d synchronous-commit availability replicas in availability group ‘%.*ls’. Change one of the existing synchronous-commit
Error: 35213, Severity: 16, The %ls operation is not allowed by the current availability-group configuration. This operation would exceed the maximum number of %d automatic failover targets in availability group ‘%.*ls’. Change one of the existing synchronous-commit replicas to th

Error: 35214, Severity: 16, The %ls operation failed for availability replica ‘%.*ls’. The minimum value for session timeout is %d. Retry the operation specifying a valid session-timeout value.
Error: 35215, Severity: 16, The %ls operation is not allowed on availability replica ‘%.*ls’, because automatic failover mode is an invalid configuration on a SQL Server Failover Cluster Instance. Retry the operation by specifying manual failover mode.
Error: 35217, Severity: 16, The thread pool for AlwaysOn Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This may degrade AlwaysOn Availability Groups performance. Use the “max worker threads” configuration option
Error: 35220, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is waiting for the host computer to start a Windows Server Failover Clustering (WSFC) cluster and join it. Either the local computer is not a cluster node, or the local cluster
Error: 35221, Severity: 16, Could not process the operation. AlwaysOn Availability Groups replica manager is disabled on this instance of SQL Server. Enable AlwaysOn Availability Groups, by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry t
Error: 35222, Severity: 16, Could not process the operation. AlwaysOn Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster. Disable and re-enable AlwaysOn Availability Groups by using the SQL Server Configuration Manager. The

Error: 35223, Severity: 16, Cannot add %d availability replica(s) to availability group ‘%.*ls’. The availability group already contains %d replica(s), and the maximum number of replicas supported in an availability group is %d.
Error: 35224, Severity: 16, Could not process the operation. AlwaysOn Availability Groups failed to load the required Windows Server Failover Clustering (WSFC) library. Verify that the computer is a node in a WSFC cluster. You will need to restart the SQL Server instance to reload
Error: 35225, Severity: 16, Could not process the operation. The instance of SQL Server is running under WOW64 (Windows 32-bit on Windows 64-bit), which does not support AlwaysOn Availability Groups. Reinstall SQL Server in the native 64-bit edition, and re-enable AlwaysOn Availab
Error: 35226, Severity: 16, Could not process the operation. AlwaysOn Availability Groups has not started because the instance of SQL Server is not running as a service. Restart the server instance as a service, and retry the operation.
Error: 35228, Severity: 16, The attempt to set the failure condition level for availability group ‘%.*ls’ failed. The specified level value is out of the valid range [%u, %u]. Reenter the command specifying a valid failure condition level value.
Error: 35229, Severity: 16, The attempt to set the health check timeout value for availability group ‘%.*ls’ failed. The specified timeout value is less than %u milliseconds. Reenter the command specifying a valid health check timeout value.
Error: 35230, Severity: 16, The specified computer name is either an empty string or is longer than %d Unicode characters. Reenter the command specifying a valid computer name.
Error: 35231, Severity: 16, The specified server instance name, ‘%ls’, is invalid. Reenter the command specifying a valid instance name.
Error: 35232, Severity: 16, The specified endpoint URL ‘%.*ls’ is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online.
Error: 35233, Severity: 16, Cannot create an availability group containing %d availability replica(s).

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.

 

SQL Server Errors or Failures from Error: 35003 to Error: 35210

SQLServerF1

Error: 35003, Severity: 16, Cannot move node to one of its children

Error: 35004, Severity: 16, Could not find server group
Error: 35005, Severity: 16, An invalid value NULL was passed in for @server_group_id.
Error: 35006, Severity: 16, An invalid value NULL was passed in for @server_id.
Error: 35007, Severity: 16, Could not find shared registered server.
Error: 35008, Severity: 16, Cannot delete system shared server groups.
Error: 35009, Severity: 16, An invalid value NULL was passed in for @server_type.

Error: 35010, Severity: 16, An invalid value %d was passed in for parameter @server_type.
Error: 35011, Severity: 16, The @server_name parameter cannot be a relative name.
Error: 35012, Severity: 16, You cannot add a shared registered server with the same name as the Configuration Server.
Error: 35100, Severity: 16, Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647.
Error: 35201, Severity: 10, A connection timeout has occurred while attempting to establish a connection to availability replica ‘%ls’ with id [%ls]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint
Error: 35202, Severity: 10, A connection for availability group ‘%ls’ from availability replica ‘%ls’ with id [%ls] to ‘%ls’ with id [%ls] has been successfully established. This is an informational message only. No user action is required.

Error: 35203, Severity: 16, Unable to establish a connection between instance ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] due to a transport version mismatch.
Error: 35204, Severity: 10, The connection between server instances ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] has been disabled because the database mirroring endpoint was either disabled or stopped. Restart the endpoint by using the ALTER ENDPOINT Transact-SQL statement with STAT
Error: 35205, Severity: 16, Could not start the AlwaysOn Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the message dispatcher started up. If so, other internal tasks might also have experienced errors. Check the SQL
Error: 35206, Severity: 10, A connection timeout has occurred on a previously established connection to availability replica ‘%ls’ with id [%ls]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
Error: 35207, Severity: 16, Connection attempt on availability group id ‘%ls’ from replica id ‘%ls’ to replica id ‘%ls’ failed because of error %d, severity %d, state %d.
Error: 35208, Severity: 16, Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, and retry your availability-group DDL command.
Error: 35209, Severity: 16, The %ls operation failed for availability replica ‘%.*ls’, because the backup priority value is outside the valid range. The valid range is between %d and %d, inclusive. Set the backup priority to a value within this range, and retry the operation.

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.

 

SQL Server Errors or Failures from Error: 5124 to Error: 5170

SQLServerF1

 

Error: 5124, Severity: 16, The file header in ‘%ls’ does not match the expected contents for file ‘%ls’ of database ‘%ls’. The mismatch is possibly between the full-text catalog files and the related database. Perform a restore if necessary.
Error: 5125, Severity: 24, File ‘%ls’ appears to have been truncated by the operating system. Expected size is %I64d KB but actual size is %I64d KB.
Error: 5127, Severity: 16, All files must be specified for database snapshot creation. Missing the file “%ls”.
Error: 5128, Severity: 17, Write to sparse file ‘%ls’ failed due to lack of disk space.
Error: 5129, Severity: 10, The log cannot be rebuilt when the primary file is read-only.
Error: 5130, Severity: 10, The log cannot be rebuilt when database mirroring is enabled.
Error: 5131, Severity: 10, The log was not rebuilt because there is more than one log file.

Error: 5132, Severity: 16, The path specified by ‘%.*ls’ cannot be used for FILESTREAM files because it is a raw device.
Error: 5133, Severity: 16, Directory lookup for the file “%ls” failed with the operating system error %ls.
Error: 5134, Severity: 16, The path that is specified by ‘%.*ls’ cannot be used for FILESTREAM files because it is not on a supported file system.
Error: 5135, Severity: 16, The path ‘%.*ls’ cannot be used for FILESTREAM files. For information about supported paths, see SQL Server Books Online.
Error: 5136, Severity: 16, The path specified by ‘%.*ls’ cannot be used for a FILESTREAM container since it is contained in another FILESTREAM container.
Error: 5144, Severity: 10, Autogrow of file ‘%.*ls’ in database ‘%.*ls’ was cancelled by user or timed out after %d milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.

Error: 5145, Severity: 10, Autogrow of file ‘%.*ls’ in database ‘%.*ls’ took %d milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.
Error: 5149, Severity: 16, MODIFY FILE encountered operating system error %ls while attempting to expand the physical file ‘%ls’.
Error: 5150, Severity: 16, The size of a single log file must not be greater than 2 TB.
Error: 5159, Severity: 24, Operating system error %.*ls on file “%.*ls” during %ls.
Error: 5161, Severity: 16, An unexpected file id was encountered. File id %d was expected but %d was read from “%.*ls”. Verify that files are mapped correctly in sys.master_files. ALTER DATABASE can be used to correct the mappings.
Error: 5169, Severity: 16, FILEGROWTH cannot be greater than MAXSIZE for file ‘%.*ls’.
Error: 5170, Severity: 16, Cannot create file ‘%ls’ because it already exists. Change the file path or the file name, and retry the operation.

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.

 

SQL Server Errors or Failures from Error: 5095 to Error: 5123

SQLServerF1

 

Error: 5095, Severity: 16, A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file “%ls” before attempting to transition to read-only.
Error: 5096, Severity: 16, The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file “%ls” before attempting to transition to SIMPLE.
Error: 5097, Severity: 16, The container cannot be set to the offline state because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE statement.
Error: 5098, Severity: 16, The container can not be dropped because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE operation.
Error: 5102, Severity: 22, Attempted to open a filegroup for the invalid ID %d in database “%.*ls”.

Error: 5103, Severity: 16, MAXSIZE cannot be less than SIZE for file ‘%ls’.
Error: 5104, Severity: 16, File ‘%.*ls’ already used.
Error: 5105, Severity: 16, A file activation error occurred. The physical file name ‘%.*ls’ may be incorrect. Diagnose and correct additional errors, and retry the operation.
Error: 5108, Severity: 10, Log file ‘%.*ls’ does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
Error: 5110, Severity: 16, The file “%.*ls” is on a network path that is not supported for system database files.
Error: 5111, Severity: 10, File activation failure. The physical file name “%.*ls” may be incorrect.

Error: 5112, Severity: 10, FCB::SetSize dbid %d fileid %d oldSize %d newSize %d. To prevent this informational message from appearing in the error log, use DBCC TRACEOFF to turn off the trace flag.
Error: 5113, Severity: 10, The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due
Error: 5114, Severity: 16, Log files, offline files, restoring files, and defunct files for database snapshots should not be specified. “%.*ls” is not an eligible file for a database snapshot.
Error: 5115, Severity: 16, Only SQL Server database files can be specified for database snapshots. ‘%.*ls’ is not a SQL Server database file.
Error: 5118, Severity: 16, The file “%ls” is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
Error: 5119, Severity: 16, Cannot make the file “%.*ls” a sparse file. Make sure the file system supports sparse files.
Error: 5120, Severity: 16, Unable to open the physical file “%.*ls”. Operating system error %d: “%ls”.
Error: 5121, Severity: 16, The path specified by “%.*ls” is not in a valid directory.
Error: 5123, Severity: 16, CREATE FILE encountered operating system error %ls while attempting to open or create the physical file ‘%.*ls’.

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.

 

SQL Server Errors or Failures Error: 1472 to Error: 1505

SQLServerF1

 

Error: 1472, Severity: 16,
The database mirroring connection terminated. Communications error sending message for database “%.*ls”.

Error: 1473, Severity: 16,
This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed.

Error: 1474, Severity: 16,
Database mirroring connection error %d ‘%.*ls’ for ‘%.*ls’.

Error: 1475, Severity: 16,
Database “%.*ls” might contain bulk logged changes that have not been backed up. Take a log backup on the principal database or primary database. Then restore this backup either on the mirror database to enable database mirroring or on every secondary dat

Error: 1476, Severity: 16,
Database mirroring timeout value %d exceeds the maximum value 32767.

Error: 1477, Severity: 16,
The database mirroring safety level must be FULL to manually failover database “%.*ls”. Set safety level to FULL and retry.

Error: 1478, Severity: 16,
The mirror database, “%.*ls”, has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database

Error: 1479, Severity: 16,
The mirroring connection to “%.*ls” has timed out for database “%.*ls” after %d seconds without a response. Check the service and network connections.

Error: 1480, Severity: 10,
The %S_MSG database “%.*ls” is changing roles from “%ls” to “%ls” because the mirroring session or availability group failed over due to %S_MSG. This is an informational message only. No user action is required.

Error: 1481, Severity: 10,
Database mirroring could not repair physical page %S_PGID in database “%.*ls”. The mirroring partner could not be contacted or did not provide a copy of the page. Possible reasons include a lack of network connectivity or that the copy of the page kept by

Error: 1482, Severity: 10,
Database mirroring failed to get snapshot synchrinization lock.

Error: 1485, Severity: 10,
Database mirroring has been enabled on this instance of SQL Server.

Error: 1486, Severity: 10,
Database Mirroring Transport is disabled in the endpoint configuration.

Error: 1487, Severity: 10,
Database mirroring is starting %d parallel redo thread(s) with database ‘%.*ls’ as the mirror copy. This is an informational message only. No user action is required.

Error: 1488, Severity: 16,
Database “%.*ls” database is in single user mode which is incompatible with participating in database mirroring or in an availability group. Set database to multi-user mode, and retry the operation.

Error: 1489, Severity: 10,
Database Mirroring is disabled on this server due to error %d. Check the errorlog and configuration for more information.

Error: 1490, Severity: 16,
The remote copy of database “%.*ls” has not been restored to a log backup that includes all filestream data files.

Error: 1499, Severity: 16,
Database mirroring error: status %u, severity %u, state %u, string %.*ls.

Error: 1501, Severity: 20,
Sort failure. Contact Technical Support.

Error: 1505, Severity: 16,
The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘%.*ls’ and the index name ‘%.*ls’. The duplicate key value is %ls.

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.

 
1 2