An Azure relational database service.
Error 40613 means the Azure SQL database is currently unavailable. This is typically a transient condition caused by failover, reconfiguration, or a scale operation. Since it has lasted more than 12 hours, this is no longer a normal brief interruption.
Recommended actions:
- Check the database health in Azure portal.
- Open the SQL database resource.
- Review Resource Health for any platform issue affecting the database.
- Also check whether the database state is Online.
- Check for service incidents during the affected period.
- Review the Microsoft Azure Service Dashboard for outages around the time the failures started.
- Retry with backoff from applications.
-
40613is a retryable transient connectivity error. - Production applications should implement retry logic instead of surfacing the error directly.
-
- Use the session tracing ID if the issue persists.
- The error message explicitly says to provide the session tracing ID when contacting support.
- Because the outage has continued far beyond the expected brief window, capture the tracing ID
{AA587236-93BF-4371-9507-E74259E5269D}and open an Azure support request.
- If a Dedicated Admin Connection is being used, verify there is not already an active DAC session.
- In Azure SQL Database,
40613can also occur if another session is already connected through DAC. - Only one DAC session can connect to a single database or elastic pool at a time.
- In Azure SQL Database,
Relevant behavior for this case:
- Azure documents
40613as:Database '%.*ls' on server '%.*ls' is not currently available. Please retry the connection later... - Brief occurrences can happen during failover or scale operations.
- If the duration exceeds 60 seconds or there are repeated occurrences in a day, the documented guidance is to file an Azure support request.