SQL Server Errors or Failures from Error: 41414 to Error: 45005

SQLServerF1

Error: 41414, Severity: 16, In this availability group, at least one secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.

Error: 41415, Severity: 16, Availability replica does not have a healthy role.

Error: 41416, Severity: 16, The role of this availability replica is unhealthy. The replica does not have either the primary or secondary role.

Error: 41417, Severity: 16, Availability replica is disconnected.
Error: 41418, Severity: 16, This secondary replica is not connected to the primary replica. The connected state is DISCONNECTED.
Error: 41419, Severity: 16, Data synchronization state of some availability database is not healthy.
Error: 41420, Severity: 16, At least one availability database on this availability replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state. If this is a synchronous-
Error: 41421, Severity: 16, Availability database is suspended.
Error: 41422, Severity: 16, Either a database administrator or the system has suspended data synchronization on this availability database.
Error: 41423, Severity: 16, Secondary database is not joined.
Error: 41424, Severity: 16, This secondary database is not joined to the availability group. The configuration of this secondary database is incomplete. For information about how to join a secondary database to an availability group, see SQL Server Books Online.
Error: 41425, Severity: 16, Data synchronization state of availability database is not healthy.
Error: 41426, Severity: 16, The data synchronization state of this availability database is unhealthy. On an asynchronous-commit availability replica, every availability database should be in the SYNCHRONIZING state. On a synchronous-commit replica, every availability database shoul
Error: 41427, Severity: 16, Availability replica is not joined.
Error: 41428, Severity: 16, This secondary replica is not joined to the availability group. For an availability replica to be successfully joined to the availability group, the join state must be Joined Standalone Instance (1) or Joined Failover Cluster (2). For information about ho
Error: 45001, Severity: 16, %ls operation failed. Specified federation name does not exist.
Error: 45002, Severity: 16, %ls operation failed. Specified federation distribution name %.*ls is not valid.
Error: 45003, Severity: 16, %ls operation failed. Specified data type is not supported as a federation distribution.
Error: 45004, Severity: 16, %ls operation failed. Specified value is not valid for federation distribution %.*ls and federation %.*ls.
Error: 45005, Severity: 16, Filter value cannot be set or was already set for this session.

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: 41191 to Error: 41211

SQLServerF1

Error: 41191, Severity: 16, The local availability replica of availability group ‘%.*ls’ cannot become the primary replica. The last-known primary availability replica is of a higher version than the local availability replica. Upgrade the local instance of SQL Server to the same

Error: 41192, Severity: 17, Creating and scheduling a worker task for AlwaysOn Availability Groups failed due to lack of resources (SQL OS error %d). Processing of new actions might be delayed or stalled until the resource limits are resolved. Reduce the memory or thread count on
Error: 41193, Severity: 10, Cannot join database ‘%.*ls’ to availability group ‘%.*ls’. The database is in the process of being removed from the availability group. When the remove-database operation completes, the database will no longer be joined to the availability group. Then

Error: 41194, Severity: 16, An error occurred while waiting for the local availability replica for availability group ‘%.*ls’ to complet post-online work. The operation encountered SQL OS error %d and has been terminated. Verify that the Windows Server Failover Clustering (WSFC) c
Error: 41195, Severity: 16, Availability group ‘%.*ls’ failed to process the WSFC lease-renewal command. The local availability replica lease is no longer valid to process the lease renewal command. Availability replica lease expired. This is an informational message only. No user a
Error: 41196, Severity: 16, Failed to create availability group ‘%.*ls’, because a Windows Server Failover Cluster (WSFC) group with the specified name already exists. An attempt to rollback the operation failed. Check the SQL Server error log for more details. To manually clean
Error: 41197, Severity: 15, The FAILOVER_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying a failover mode for the replica.
Error: 41198, Severity: 15, The AVAILABILITY_MODE option has not been specified for the replica ‘%.*ls’. Reenter the command, specifying an availability mode for the replica.

Error: 41199, Severity: 16, The specified command is invalid because the AlwaysOn Availability Groups feature is not supported by this edition of SQL Server. For information about features supported by the editions of SQL Server, see SQL Server Books Online.
Error: 41201, Severity: 16, The SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE and SEMANTICSIMILARITYDETAILSTABLE functions do not support remote data sources.
Error: 41202, Severity: 16, The source table ‘%.*ls’ specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function doesn’t have a full-text index that uses the STATISTICAL_SEMANTICS option. A full-text index using the STATISTICAL_SEMANT
Error: 41203, Severity: 16, The column ‘%.*ls’ specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function is not full-text indexed with the STATISTICAL_SEMANTICS option. The column must be full-text indexed using the STATISTICAL_SEMA
Error: 41204, Severity: 16, The source_key parameter is required in the SEMANTICSIMILARITYTABLE function.
Error: 41205, Severity: 10, Error %d occurred during semantic index population for table or indexed view ‘%.*ls’ (table or indexed view ID %d, database ID %d, document ID %d)
Error: 41206, Severity: 10, An ALTER FULLTEXT INDEX statement cannot remove the ‘STATISTICAL_SEMANTICS’ option from the last column in the index that has the option set when a “WITH NO POPULATION” clause is specified. Remove the “WITH NO POPULATION” clause.
Error: 41207, Severity: 10, A locale ID that is not supported was specified for a column with ‘STATISTICAL_SEMANTICS’. Please verify that the locale ID is correct and that the corresponding language statistics has been installed.
Error: 41208, Severity: 10, Warning: The population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’) encountered a document with full-text key value ‘%ls’ that specifies a language not supported for semantic indexing. Some columns of the row will not
Error: 41209, Severity: 10, A semantic language statistics database is not registered. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated.
Error: 41210, Severity: 10, The semantic language statistics database is not accessible or not valid. Full-text indexes using ‘STATISTICAL_SEMANTICS’ cannot be created or populated.
Error: 41211, Severity: 16, A semantic language statistics database is already registered.

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: 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 Error: 3413 to Error: 3448

SQLServerF1

 

Error: 3413, Severity: 21, Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to identify the cause and correct any associated problems.,
Error: 3414, Severity: 10, An error occurred during recovery, preventing the database ‘%ls’ (%d:%d) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

Msg 3415, Level 16, State 2, Line 2Error: 3415, Severity: 16, State: 2Database ‘%.*ls’ cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to modify some of the files. Make the database or files writeable, and rerun recovery.
This error occurs if you try to attach an database whose .mdf, .ndf or .ldf files resides in a folder to which the SQL Server service account does not have permission to. So, grant full control to SQL Server service account on the folder and files where database files are present.

Error: 3416, Severity: 16, The server contains read-only files that must be made writable before the server can be recollated.
Error: 3417, Severity: 21, Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.,
Error: 3418, Severity: 10, Recovery is unable to defer error %d. Errors can only be deferred in databases using the full recovery model and an active backup log chain.,
Error: 3419, Severity: 16, Recovery for database ‘%.*ls’ is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take the database back to a Restoring state and continue the restore sequence.,
Error: 3420, Severity: 21, Database snapshot ‘%ls’ has failed an IO operation and is marked suspect. It must be dropped and recreated.,
Error: 3421, Severity: 10, Recovery completed for database %ls (database ID %d) in %I64d second(s) (analysis %I64d ms, redo %I64d ms, undo %I64d ms.) This is an informational message only. No user action is required.,
Error: 3422, Severity: 10, Database %ls was shutdown due to error %d in routine ‘%hs’. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.,
Error: 3429, Severity: 10, Recovery could not determine the outcome of a cross-database transaction %S_XID, named ‘%.*ls’, in database ‘%.*ls’ (database ID %d:%d). The coordinating database (database ID %d:%d) was unavailable. The transaction was assumed to be committed. If the tra,
Error: 3431, Severity: 21, Could not recover database ‘%.*ls’ (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC) transactions were prepared, but MS DTC was unable to determine the resolution. To resolve, either fix MS,
Error: 3434, Severity: 20, Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and t,
Error: 3437, Severity: 21, An error occurred while recovering database ‘%.*ls’. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completion status of transaction %S_XID. Fix MS DTC, and run recovery again.,
Error: 3441, Severity: 21, During startup of warm standby database ‘%.*ls’ (database ID %d), its standby file (‘%ls’) was inaccessible to the RESTORE statement. The operating system error was ‘%ls’. Diagnose the operating system error, correct the problem, and retry startup.,
Error: 3443, Severity: 21, Database ‘%ls’ (database ID %d:%d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup.,
Error: 3445, Severity: 21, File ‘%ls’ is not a valid undo file for database ‘%.*ls (database ID %d). Verify the file path, and specify the correct file.,
Error: 3446, Severity: 16, Primary log file is not available for database ‘%ls’ (%d:%d). The log cannot be backed up.,
Error: 3447, Severity: 16, Could not activate or scan all of the log files for database ‘%.*ls’.,
Error: 3448, Severity: 21, Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database ‘%ls’ (%d:%d). Page information: LSN = %S_LSN, type = %ld. Log 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 Error: 3134 to Error: 3155

SQLServerF1

 

Error: 3134, Severity: 10, The differential base attribute for file ‘%ls’ of database ‘%ls’ has been reset because the file has been restored from a backup taken on a conflicting recovery path. The restore was allowed because the file was read-only and was consistent with the curre,
Error: 3135, Severity: 16, The backup set in file ‘%ls’ was created by %hs and cannot be used for this restore operation.,
Error: 3136, Severity: 16, This differential backup cannot be restored because the database has not been restored to the correct earlier state.,

Error: 3137, Severity: 16, Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there are missing files.,
Error: 3138, Severity: 16, The database cannot be reverted because FILESTREAM BLOBs are present.,
Error: 3139, Severity: 16, Restore to snapshot is not allowed with the master database.,
Error: 3140, Severity: 16, Could not adjust the space allocation for file ‘%ls’.,
Error: 3141, Severity: 16, The database to be restored was named ‘%ls’. Reissue the statement using the WITH REPLACE option to overwrite the ‘%ls’ database.,
Error: 3142, Severity: 16, File “%ls” cannot be restored over the existing “%ls”. Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location.,
Error: 3143, Severity: 16, The data set on device ‘%ls’ is not a SQL Server backup set.,

Error: 3144, Severity: 16, File ‘%.*ls’ was not backed up in file %d on device ‘%ls’. The file cannot be restored from this backup set.,
Error: 3145, Severity: 16, The STOPAT option is not supported for databases that use the SIMPLE recovery model.,
Error: 3147, Severity: 16, Backup and restore operations are not allowed on database tempdb.,
Error: 3148, Severity: 16, This RESTORE statement is invalid in the current context. The ‘Recover Data Only’ option is only defined for secondary filegroups when the database is in an online state. When the database is in an offline state filegroups cannot be specified.,
Error: 3149, Severity: 16, The file or filegroup “%ls” is not in a valid state for the “Recover Data Only” option to be used. Only secondary files in the OFFLINE or RECOVERY_PENDING state can be processed.,
Error: 3150, Severity: 10, The master database has been successfully restored. Shutting down SQL Server.,
Error: 3151, Severity: 21, Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to rebuild the master database, see SQL Server Books Online.,
Error: 3153, Severity: 16, The database is already fully recovered.,
Error: 3154, Severity: 16, The backup set holds a backup of a database other than the existing ‘%ls’ database.,
Error: 3155, Severity: 16, The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created.,

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: 969 to Error: 1004

SQLServerF1

 

Error: 969, Severity: 10,
Warning: The default or fixed value on XML element or attribute “%.*ls” in schema collection “%.*ls” is updated from “%.*ls” to “%.*ls” because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.

Error: 970, Severity: 10,
Warning: The XML instances in the XML column “%.*ls.%.*ls.%.*ls” may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary or selective XML index on these XML instances.

Error: 971, Severity: 10,
The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ instead of the currently attached resource database at ‘%.*ls’.

Error: 972, Severity: 17,
Could not use database ‘%d’ during procedure execution.

Error: 974, Severity: 10,
Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ failed as the database files do not exist.

Error: 975, Severity: 10,
System objects could not be updated in database ‘%.*ls’ because it is read-only.

Error: 976, Severity: 14,
The target database, ‘%.*ls’, is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other

Error: 977, Severity: 10,
Warning: Could not find associated index for the constraint ‘%.*ls’ on object_id ‘%d’ in database ‘%.*ls’.

Error: 978, Severity: 14,
The target database (‘%.*ls’) is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online.

Error: 979, Severity: 14,
The target database (‘%.*ls’) is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online.

Error: 980, Severity: 21,
SQL Server cannot load database ‘%.*ls’ because it contains a columnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL S

Error: 981, Severity: 10,
Database manager will be using %d target database version.

Error: 982, Severity: 14,
Unable to access the ‘%.*ls’ database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled r

Error: 983, Severity: 14,
Unable to access database ‘%.*ls’ because its replica role is RESOLVING which does not allow connections. Try the operation again later.

Error: 984, Severity: 21,
Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with error code %d.

Error: 985, Severity: 10,
Successfully installed the file ‘%ls’ into folder ‘%ls’.

Error: 1001, Severity: 16,
Line %d: Length or precision specification %d is invalid.

Error: 1002, Severity: 16,
Line %d: Specified scale %d is invalid.

Error: 1003, Severity: 15,
Line %d: %ls clause allowed only for %ls.

Error: 1004, Severity: 16,
Invalid column prefix ‘%.*ls’: No table name specified

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.