You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2016-database-engine-events-and-errors-31000-41399.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -559,7 +559,7 @@ ms.topic: include
559
559
| 35264 | 10 | No | Always On 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 information about how to resume an availability database, see SQL Server Books Online. |
560
560
| 35265 | 10 | No | Always On Availability Groups data movement for database '%.\*ls' has been resumed. This is an informational message only. No user action is required. |
561
561
| 35266 | 10 | No | Always On Availability Groups connection with %S_MSG database established for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
562
-
| 35267 | 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
562
+
|[35267](../mssqlserver-35267-database-engine-error.md)| 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
563
563
| 35268 | 16 | Yes | 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 database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups. |
564
564
| 35269 | 21 | Yes | 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 subsequent log backups. |
565
565
| 35270 | 10 | No | Received a corrupt FileStream transport message. The '%ls' message section is invalid. |
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2017-database-engine-events-and-errors-31000-41399.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -578,7 +578,7 @@ ms.topic: include
578
578
| 35264 | 10 | No | Always On 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 information about how to resume an availability database, see SQL Server Books Online. |
579
579
| 35265 | 10 | No | Always On Availability Groups data movement for database '%.\*ls' has been resumed. This is an informational message only. No user action is required. |
580
580
| 35266 | 10 | No | Always On Availability Groups connection with %S_MSG database established for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
581
-
| 35267 | 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
581
+
|[35267](../mssqlserver-35267-database-engine-error.md)| 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
582
582
| 35268 | 16 | Yes | 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 database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups. |
583
583
| 35269 | 21 | Yes | 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 subsequent log backups. |
584
584
| 35270 | 10 | No | Received a corrupt FileStream transport message. The '%ls' message section is invalid. |
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2019-database-engine-events-and-errors-31000-41399.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -646,7 +646,7 @@ ms.topic: include
646
646
| 35264 | 10 | No | Always On 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 information about how to resume an availability database, see SQL Server Books Online. |
647
647
| 35265 | 10 | No | Always On Availability Groups data movement for database '%.\*ls' has been resumed. This is an informational message only. No user action is required. |
648
648
| 35266 | 10 | No | Always On Availability Groups connection with %S_MSG database established for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
649
-
| 35267 | 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
649
+
|[35267](../mssqlserver-35267-database-engine-error.md)| 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
650
650
| 35268 | 16 | Yes | 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 database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups. |
651
651
| 35269 | 21 | Yes | 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 subsequent log backups. |
652
652
| 35270 | 10 | No | Received a corrupt FileStream transport message. The '%ls' message section is invalid. |
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-10000-10999.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -391,15 +391,15 @@ ms.topic: include
391
391
| 10925 | 16 | No | A %S_MSG value was specified more than one time in the pool affinity range list. |
392
392
| 10926 | 16 | No | The %S_MSG range that specifies %S_MSG %d includes at least one %S_MSG that is not available to the current instance. The maximum %S_MSG number that is available to this instance is %d. |
393
393
| 10927 | 16 | No | The operation could not be completed. The specified '%.\*ls' value, %u, causes the sum of minimums on all workload groups using resource pool '%.\*ls' to exceed 100 percent. Reduce the value or modify other workload groups so that the sum is less than or equal to 100. |
394
-
| 10928 | 16 | No | Resource ID : %d. The %ls limit for the database is %d and has been reached. See 'https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server' for assistance. |
395
-
| 10929 | 16 | No | Resource ID : %d. The %ls minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support %ls greater than %d for this database. See 'https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server' for assistance. Otherwise, please try again later. |
394
+
| 10928 | 16 | No | Resource ID : %d. The %ls limit for the database is %d and has been reached. See '[https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server](/azure/azure-sql/database/resource-limits-logical-server)' for assistance. |
395
+
| 10929 | 16 | No | Resource ID : %d. The %ls minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d. However, the server is currently too busy to support %ls greater than %d for this database. See '[https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server](/azure/azure-sql/database/resource-limits-logical-server)' for assistance. Otherwise, please try again later. |
396
396
| 10930 | 16 | No | The service is currently too busy. Please try again later. |
397
397
| 10931 | 16 | No | Cannot drop resource pool '%.\*ls' because it is bound to a database. Remove all bindings to this resource pool before dropping it. |
398
398
| 10932 | 16 | No | Resource governor configuration failed, because there is an active database in the resource pool being dropped. Take the database offline and try again. |
399
399
| 10933 | 16 | No | A %S_MSG with id %d does not exist on this system. Use sys.dm_os_schedulers to locate valid %S_MSGs for this system. |
400
400
| 10934 | 16 | No | Requested operation cannot be performed because the external resource pool '%.\*ls' does not exist. |
401
401
| 10935 | 16 | No | External resource pool does not allow more than one processor group. |
402
-
| 10936 | 16 | No | Resource ID : %d. The %ls limit for the elastic pool is %d and has been reached. See 'https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server' for assistance. |
402
+
| 10936 | 16 | No | Resource ID : %d. The %ls limit for the elastic pool is %d and has been reached. See '[https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server](/azure/azure-sql/database/resource-limits-logical-server)' for assistance. |
403
403
| 10937 | 16 | No | Default workload group does not allow to alter attribute '%.\*ls'. |
404
404
| 10961 | 16 | No | The request has been aborted because its CPU usage exceeds the maximum configured limit for the workload group. |
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-22000-22999.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ ms.topic: include
50
50
| 22122 | 16 | No | Change Tracking autocleanup failed on side table of "%s". If the failure persists, use sp_flush_CT_internal_table_on_demand to clean up expired records from its side table. |
51
51
| 22123 | 16 | No | Change Tracking autocleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process . |
52
52
| 22124 | 16 | No | Change Tracking manual cleanup is blocked on side table of "%s". If the failure persists, check if the table "%s" is blocked by any process . |
53
-
| 22125 | 16 | No | Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, check the following resource: https://learn.microsoft.com/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server|
53
+
| 22125 | 16 | No | Change tracking autocleanup is currently not able to maintain retention for database ID %d. Number of expired records: %d. If this warning persists, check the following resource: [https://learn.microsoft.com/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server](/sql/relational-databases/track-changes/cleanup-and-troubleshoot-change-tracking-sql-server)|
54
54
| 22201 | 16 | No | Internal error. Unable to acquire the latch holding buffers for DW Tiered Storage ColumnStore Scan. |
55
55
| 22202 | 16 | No | Internal error. Unable to run the remote cs garbage collector. Error Code 22202. |
56
56
| 22203 | 16 | No | Internal error. Unable to update the blobs table in the catalogDB. Error Code 22203. |
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-31000-41399.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -710,7 +710,7 @@ ms.topic: include
710
710
| 35264 | 10 | No | Always On 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 information about how to resume an availability database, see SQL Server Books Online. |
711
711
| 35265 | 10 | No | Always On Availability Groups data movement for database '%.\*ls' has been resumed. This is an informational message only. No user action is required. |
712
712
| 35266 | 10 | No | Always On Availability Groups connection with %S_MSG database established for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
713
-
| 35267 | 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
713
+
|[35267](../mssqlserver-35267-database-engine-error.md)| 10 | No | Always On Availability Groups connection with %S_MSG database terminated for %S_MSG database '%.\*ls' on the availability replica '%.\*ls' with Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}. This is an informational message only. No user action is required. |
714
714
| 35268 | 16 | Yes | 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 database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups. |
715
715
| 35269 | 21 | Yes | 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 subsequent log backups. |
716
716
| 35270 | 10 | No | Received a corrupt FileStream transport message. The '%ls' message section is invalid. |
@@ -1048,7 +1048,7 @@ ms.topic: include
1048
1048
| 37350 | 16 | No | LEDGER = ON cannot be specified with SYSTEM_VERSIONING = ON and APPEND_ONLY = ON. |
1049
1049
| 37351 | 16 | No | LEDGER = ON cannot be specified with PERIOD FOR SYSTEM_TIME and APPEND_ONLY = ON. |
1050
1050
| 37352 | 16 | No | APPEND_ONLY = ON cannot be specified with generated always end columns. |
1051
-
| 37353 | 16 | No | Server identity does not have Azure Active Directory Readers permission. Please follow the steps here : https://learn.microsoft.com/azure/azure-sql/database/authentication-aad-service-principal|
1051
+
| 37353 | 16 | No | Server identity does not have Azure Active Directory Readers permission. Please follow the steps here : [https://learn.microsoft.com/azure/azure-sql/database/authentication-aad-service-principal](/azure/azure-sql/database/authentication-aad-service-principal)|
1052
1052
| 37354 | 16 | No | LEDGER = ON cannot be specified with system versioning retention period. |
1053
1053
| 37355 | 16 | No | An existing History Table cannot be specified with LEDGER=ON. |
1054
1054
| 37356 | 16 | No | System Versioning cannot be altered for Ledger Tables. |
@@ -1252,7 +1252,7 @@ ms.topic: include
1252
1252
| 39018 | 16 | No | Parameter '%.\*ls' uses a data type that is not supported by the runtime for '%.\*s' script. Unsupported types are timestamp, datetime2, datetimeoffset, time, text, ntext, image, hierarchyid, xml, sql_variant and user-defined type. External script request id is %ls. |
1253
1253
| 39019 | 10 | No | An external script error occurred: %.\*ls%.\*ls |
1254
1254
| 39020 | 16 | No | Feature 'Advanced Analytics Extensions' is not installed. Please consult Books Online for more information on this feature. |
1255
-
| 39021 | 16 | No | Unable to launch runtime for '%.\*s' script for request id: %ls. Please check the configuration of the '%.\*s' runtime. See 'https://learn.microsoft.com/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022?view=sql-server-ver16' for setup instructions. |
1255
+
| 39021 | 16 | No | Unable to launch runtime for '%.\*s' script for request id: %ls. Please check the configuration of the '%.\*s' runtime. See '[https://learn.microsoft.com/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022](/sql/machine-learning/install/sql-machine-learning-services-windows-install-sql-2022)' for setup instructions. |
1256
1256
| 39022 | 10 | No | STDERR message(s) from external script: %.\*ls%.\*ls |
1257
1257
| 39023 | 16 | No | 'sp_execute_external_script' is disabled on this instance of SQL Server. Use sp_configure 'external scripts enabled' to enable it. |
1258
1258
| 39024 | 16 | No | Parallel execution of 'sp_execute_external_script' failed. Specify WITH RESULT SETS clause with output schema. |
Copy file name to clipboardExpand all lines: docs/relational-databases/errors-events/includes/sql-server-2022-database-engine-events-and-errors-41400-42999.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -306,8 +306,8 @@ ms.topic: include
306
306
| 42034 | 16 | No | Boot of federation host failed with error 0x%08X. |
307
307
| 42035 | 16 | No | %ls operation timed out. Request was sent to the service resulting in response timeout. The operation might start anyway. |
308
308
| 42036 | 16 | No | %ls operation has been cancelled. |
309
-
| 42101 | 10 | No | Reason: Unable to create or update firewall rules since Deny Public Network Access is set to Yes. Please set Deny Public Network Access to No and retry the operation (https://learn.microsoft.com/azure/azure-sql/database/connectivity-settings#deny-public-network-access).|
310
-
| 42102 | 10 | No | Reason: Unable to set Deny Public Network Access to Yes since there is no private endpoint enabled to access the server. Please set up private endpoints and retry the operation (https://learn.microsoft.com/azure/sql-database/sql-database-private-endpoint-overview#how-to-set-up-private-link-for-azure-sql-database).|
309
+
| 42101 | 10 | No | Reason: Unable to create or update firewall rules since Deny Public Network Access is set to Yes. Please set Deny Public Network Access to No and retry the operation ([https://learn.microsoft.com/azure/azure-sql/database/connectivity-settings#deny-public-network-access](/azure/azure-sql/database/connectivity-settings#deny-public-network-access)). |
310
+
| 42102 | 10 | No | Reason: Unable to set Deny Public Network Access to Yes since there is no private endpoint enabled to access the server. Please set up private endpoints and retry the operation ([https://learn.microsoft.com/azure/sql-database/sql-database-private-endpoint-overview#how-to-set-up-private-link-for-azure-sql-database](/azure/sql-database/sql-database-private-endpoint-overview#how-to-set-up-private-link-for-azure-sql-database)). |
311
311
| 42103 | 16 | No | The SQL Pool '%.\*ls' already exists. Please choose a new name. |
312
312
| 42104 | 16 | No | Could not create SQL Pool '%.\*ls'. Please try again later. |
313
313
| 42105 | 16 | No | The server role '%.\*ls' already exists. Please choose a new name. |
0 commit comments