SALES: 1-800-867-1380

Status and Error Codes

Updated: November 6, 2013

The operations supported by the Azure SQL Database Management API return standard HTTP status codes, as defined in the HTTP/1.1 Status Code Definitions.

Database Management API operations may also return additional error information that is defined by the Azure SQL Database Management Service. This additional error information is returned in the response body. The code examples given in the technical reference for each operation demonstrate how to access the additional error information from the response stream of WebExceptions. The links below navigate to the technical reference for the supported operations.

The body of the error response follows the basic format shown here.

<?xml version="1.0" encoding="utf-8"?> 

The following table describes common errors that may be returned by the Azure SQL Database Management Service while attempting to execute a request. The value for severity-level and state-information will correspond directly to the Severity and State values that are returned for SQL Server error messages. For more information on how SQL Server populates these values, see Understanding Database Engine Errors.


Error code HTTP status code User Message


Bad Request (400)

<AdministratorLogin> is not a valid name because it contains invalid characters.


Bad Request (400)

Servers can have at most 128 firewall rules defined.


Bad Request (400)

Start IP address of firewall rule cannot exceed End IP address.


Bad Request (400)

The firewall rule name that starts with <rule name> is too long. Maximum length is 128.


Bad Request (400)

The firewall rule name cannot be empty.


Bad Request (400)

Password validation failed. The password does not meet policy requirements because it is too short.


Bad Request (400)

The password that you specified is too long. The password should have no more than 128 characters.


Bad Request (400)

Password validation failed. The password does not meet policy requirements because it is not complex enough.


Bad Request (400)

Invalid subscription id <subscription-id>. Subscription does not exist.


Bad Request (400)

Request does not conform to schema: <schema error>.


Internal Server Error (500)

The server encountered an unexpected exception.


Bad Request (400)

The specified location is invalid.


Service Unavailable (503)

The server is currently too busy. Please try again later.


Bad Request (400)

The specified x-ms-version header value is invalid.


Forbidden (403)

Failed to authorize access to the specified subscription.


Bad Request (400)

Servername <servername> cannot be empty or null. It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the name.


Bad Request (400)

Subscription ID cannot be empty.


Bad Request (400)

Subscription <subscription-id does not have server servername.


Service Unavailable (503)

Too many requests have been performed. Please retry later.


Bad Request (400)

Invalid content-type is specified. Only application/xml is supported.


Bad Request (400)

Subscription <subscription-id> does not exist or is not ready for the operation.


Bad Request (400)

Failed to create server because the subscription <subscription-id> is disabled.


Bad Request (400)

Cannot move or create server. Subscription <subscription-id> will exceed server quota.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2014 Microsoft