SqlConfigurableRetryFactory.BaselineTransientErrors Property
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
This list may change at any time as the underlying implementation changes, and will not be considered a breaking API change. Applications should not depend on this list containing any particular error codes.
public:
static property System::Collections::ObjectModel::ReadOnlyCollection<int> ^ BaselineTransientErrors { System::Collections::ObjectModel::ReadOnlyCollection<int> ^ get(); };public static System.Collections.ObjectModel.ReadOnlyCollection<int> BaselineTransientErrors { get; }static member BaselineTransientErrors : System.Collections.ObjectModel.ReadOnlyCollection<int>Public Shared ReadOnly Property BaselineTransientErrors As ReadOnlyCollection(Of Integer)Property Value
Remarks
The following table shows the baseline/default transient error list used by the built-in retry providers.
Callers should treat this list as a starting point to copy and extend for their own retry logic, rather than as a stable contract that will remain unchanged.
| Error Number | Description |
|---|---|
| 233 | A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) |
| 997 | A connection was successfully established with the server, but then an error occurred during the login process. (provider: Named Pipes Provider, error: 0 - Overlapped I/O operation is in progress) |
| 1204 | The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions. |
| 1205 | Transaction (Process ID) was deadlocked on resources with another process and has been chosen as the deadlock victim. Rerun the transaction. |
| 1222 | Lock request time out period exceeded. |
| 4060 | Cannot open database "%.*ls" requested by the login. The login failed. |
| 4221 | Login to read-secondary failed due to long wait on 'HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING'. The replica is not available for login because row versions are missing for transactions that were in-flight when the replica was recycled. The issue can be resolved by rolling back or committing the active transactions on the primary replica. Occurrences of this condition can be minimized by avoiding long write transactions on the primary. |
| 10060 | An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060) |
| 10928 | Resource ID: %d. The %s limit for the database is %d and has been reached. For more information, see https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server. |
| 10929 | Resource ID: %d. The %s 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 requests greater than %d for this database. For more information, see https://learn.microsoft.com/azure/azure-sql/database/resource-limits-logical-server. Otherwise, please try again later. |
| 40143 | The service has encountered an error processing your request. Please try again. |
| 40197 | The service has encountered an error processing your request. Please try again. Error code %d. |
| 40501 | The service is currently busy. Retry the request after 10 seconds. Incident ID: %ls. Code: %d. |
| 40540 | The service has encountered an error processing your request. Please try again. |
| 40613 | Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'. |
| 42108 | Cannot connect to the SQL pool since it is paused. Please resume the SQL pool and try again. |
| 42109 | The SQL pool is warming up. Please try again. |
| 49918 | Cannot process request. Not enough resources to process request. |
| 49919 | Cannot process create or update request. Too many create or update operations in progress for subscription "%ld". |
| 49920 | Cannot process request. Too many operations in progress for subscription "%ld". |