Export (0) Print
Expand All

2.2.4 Common Status Codes

The status values returned for each command are specified in the Status element (section 2.2.3.162) section corresponding to each command. Links to the Status element sections are listed in the following table.

Command

Status element section

Autodiscover (section 2.2.2.1)

Section 2.2.3.162.1

FolderCreate (section 2.2.2.2)

Section 2.2.3.162.2

FolderDelete (section 2.2.2.3)

Section 2.2.3.162.3

FolderSync (section 2.2.2.4)

Section 2.2.3.162.4

FolderUpdate (section 2.2.2.5)

Section 2.2.3.162.5

GetItemEstimate (section 2.2.2.7)

Section 2.2.3.162.6

ItemOperations (section 2.2.2.8)

Section 2.2.3.162.7

MeetingResponse (section 2.2.2.9)

Section 2.2.3.162.8

MoveItems (section 2.2.2.10)

Section 2.2.3.162.9

Ping (section 2.2.2.11)

Section 2.2.3.162.10

Provision (section 2.2.2.12)

[MS-ASPROV] section 2.2.2.53

ResolveRecipients (section 2.2.2.13)

Section 2.2.3.162.11

Search (section 2.2.2.14)

Section 2.2.3.162.12

SendMail (section 2.2.2.15)

Section 2.2.3.162.13

Settings (section 2.2.2.16)

Section 2.2.3.162.14

SmartForward (section 2.2.2.17)

Section 2.2.3.162.15

SmartReply (section 2.2.2.18)

Section 2.2.3.162.15

Sync (section 2.2.2.19)

Section 2.2.3.162.16

ValidateCert (section 2.2.2.20)

Section 2.2.3.162.17

Many of the status values listed in the Status element sections have a scope assigned to them. The following table defines the scope values.

Value

Meaning

Global

The status pertains to the overall client request.

Item

The status pertains to a particular item within the overall client request.

Policy

The status pertains to a particular policy within the Provision command.

In addition to the status values specified for individual commands in the Status element sections of this document, the following table lists the Status element values that are common to all commands. The protocol versions that support each value are specified in the "Protocol versions" column of the table. When protocol version 2.5, 12.0, or 12.1 is used, an HTTP status code 4xx or 5xx instead of a Status element value 1xx is returned in the response. The specific HTTP status codes corresponding to some Status element values are specified in the table.

Note: The client indicates the protocol version being used by setting either the MS-ASProtocolVersion header, as specified in [MS-ASHTTP] section 2.2.1.1.2.4, or the Protocol version field, as specified in [MS-ASHTTP] section 2.2.1.1.1.1, in the request.

Value

Element name

Meaning

Protocol Versions

101

InvalidContent

The body of the HTTP request sent by the client is invalid.

Ensure the HTTP request is using the specified Content-Type and length, and that the request is not missing (when an empty body is not allowed).

Examples:

Ping command (section 2.2.2.11) with a text/plain body, or SendMail command (section 2.2.2.15) with version 12.1 and a WBXML body.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 400 response is returned instead of this status value.

102

InvalidWBXML

The request contains WBXML but it could not be decoded into XML.

Supported by: 14.0, 14.1

103

InvalidXML

The XML provided in the request does not follow the protocol requirements.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 400 response is returned instead of this status value.

104

InvalidDateTime

The request contains a timestamp that could not be parsed into a valid date and time.

Supported by: 14.0, 14.1

105

InvalidCombinationOfIDs

The request contains a combination of parameters that is invalid.

Supported by: 14.0, 14.1

106

InvalidIDs

The request contains one or more IDs that could not be parsed into valid values.

That is different from specifying an ID in the proper format that does not resolve to an existing item.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 400 response, or an HTTP 500 response for the SendMail command, is returned instead of this status value.

107

InvalidMIME

The request contains MIME that could not be parsed.

Supported by: 14.0, 14.1

108

DeviceIdMissingOrInvalid

The device ID is either missing or has an invalid format.

Supported by: 14.0, 14.1

109

DeviceTypeMissingOrInvalid

The device type is either missing or has an invalid format.

Supported by: 14.0, 14.1

110

ServerError

The server encountered an unknown error, the device SHOULD NOT retry later.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 500 response is returned instead of this status value.

111

ServerErrorRetryLater

The server encountered an unknown error, the device SHOULD retry later.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 503 response is returned instead of this status value.

112

ActiveDirectoryAccessDenied

The server does not have access to read/write to an object in the directory service.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 403 response is returned instead of this status value.

113

MailboxQuotaExceeded

The mailbox has reached its size quota.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 507 response is returned instead of this status value.

114

MailboxServerOffline

The mailbox server is offline.

Supported by: 14.0, 14.1

115

SendQuotaExceeded

The request would exceed the send quota.

Supported by: 14.0, 14.1

116

MessageRecipientUnresolved

One of the recipients could not be resolved to an email address.

Supported by: 14.0, 14.1

117

MessageReplyNotAllowed

The mailbox server will not allow a reply of this message.

Supported by: 14.0, 14.1

118

Message

PreviouslySent

The message was already sent in a previous request. The server determined this by remembering the ClientId (section 2.2.3.36) values of the last few sent messages. This request contains a ClientId that was already used in a recent message.

Supported by: 14.0, 14.1

119

MessageHasNoRecipient

The message being sent contains no recipient.

Supported by: 14.0, 14.1

120

MailSubmissionFailed

The server failed to submit the message for delivery.

Supported by: 14.0, 14.1

121

MessageReplyFailed

The server failed to create a reply message.

Supported by: 14.0, 14.1

122

AttachmentIsTooLarge

The attachment is too large to be processed by this request.

Supported by: 14.0, 14.1

123

UserHasNoMailbox

A mailbox could not be found for the user.

Supported by: 14.0, 14.1

124

UserCannotBeAnonymous

The request was sent without credentials. Anonymous requests are not allowed.

Supported by: 14.0, 14.1

125

UserPrincipalCouldNotBeFound

The user was not found in the directory service.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 403 response is returned instead of this status value.

126

UserDisabledForSync

The user object in the directory service indicates that this user is not allowed to use ActiveSync.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 403 response is returned instead of this status value.

127

UserOnNewMailboxCannotSync

The server is configured to prevent users from syncing.

Supported by: 14.0, 14.1

128

UserOnLegacyMailboxCannotSync

The server is configured to prevent users on legacy servers from syncing.

Supported by: 14.0, 14.1

129

DeviceIsBlockedForThisUser

The user is configured to allow only some devices to sync. This device is not the allowed device.

Supported by: 14.0, 14.1

130

AccessDenied

The user is not allowed to perform that request.

Supported by: 14.0, 14.1

131

AccountDisabled

The user's account is disabled.

Supported by: 14.0, 14.1

132

SyncStateNotFound

The server’s data file that contains the state of the client was unexpectedly missing. It might have disappeared while the request was in progress. The next request will likely answer a sync key error and the device will be forced to do full sync.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 403 response for the Provision command, or an HTTP 500 response is returned instead of this status value.

133

SyncStateLocked

The server’s data file that contains the state of the client is locked, possibly because the mailbox is being moved or was recently moved.

Supported by: 14.0, 14.1

134

SyncStateCorrupt

The server’s data file that contains the state of the client appears to be corrupt.

Supported by: 14.0, 14.1

135

SyncStateAlreadyExists

The server’s data file that contains the state of the client already exists. This can happen with two initial syncs are executed concurrently.

Supported by: 14.0, 14.1

136

SyncStateVersionInvalid

The version of the server’s data file that contains the state of the client is invalid.

Supported by: 14.0, 14.1

137

CommandNotSupported

The command is not supported by this server.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 501 response is returned instead of this status value.

138

VersionNotSupported

The command is not supported in the protocol version specified.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 400 response, or an HTTP 505 response for version 1.0 devices, is returned instead of this status value.

139

DeviceNotFullyProvisionable

The device uses a protocol version that cannot send all the policy settings the admin enabled. For more details, see [MS-ASPROV] section 3.1.5.2.

Supported by: 14.0, 14.1

140

RemoteWipeRequested

A remote wipe was requested. The device SHOULD provision to get the request and then do another provision to acknowledge it. For more details, see [MS-ASPROV] section 3.1.5.1.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 403 response for no policy key header, or an HTTP 449 response is returned instead of this status value.

141

LegacyDeviceOnStrictPolicy

A policy is in place but the device is not provisionable. For more details, see [MS-ASPROV] section 3.1.5.2.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 449 response is returned instead of this status value.

142

DeviceNotProvisioned

There is a policy in place; the device needs to provision as specified in [MS-ASPROV] section 3.1.5.1.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 449 response is returned instead of this status value.

143

PolicyRefresh

The policy is configured to be refreshed every few hours. The device needs to re-provision as specified in [MS-ASPROV] section 3.1.5.1.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 449 response is returned instead of this status value.

144

InvalidPolicyKey

The device's policy key is invalid. The policy has probably changed on the server. The device needs to re-provision as specified in [MS-ASPROV] section 3.1.5.1.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 449 response is returned instead of this status value.

145

ExternallyManagedDevicesNotAllowed

The device claimed to be externally managed, but the server doesn't allow externally managed devices to sync. For more details, see [MS-ASPROV] section 3.1.5.2.

Supported by: 14.0, 14.1

146

NoRecurrenceInCalendar

The request tried to forward an occurrence of a meeting that has no recurrence.

Supported by: 14.0, 14.1

147

UnexpectedItemClass

The request tried to operate on a type of items unknown to the server.

Supported by: 14.0, 14.1

When protocol version 2.5, 12.0, or 12.1 is used, an HTTP 400 response or an HTTP 501 response is returned instead of this status value.

148

RemoteServerHasNoSSL

The request needs to be proxied to another server but that server doesn't have Secure Sockets Layer (SSL) enabled. This server is configured to only proxy requests to servers with SSL enabled.

Supported by: 14.0, 14.1

149

InvalidStoredRequest

The server had stored the previous request from that device. When the device sent an empty request, the server tried to re-execute that previous request but it was found to be impossible. The device needs to send the full request again.

Supported by: 14.0, 14.1

150

ItemNotFound

The ItemId (section 2.2.3.90) value specified in the SmartReply command (section 2.2.2.18) or SmartForward command (section 2.2.2.17) request could not be found in the mailbox.

Supported by: 14.0, 14.1

151

TooManyFolders

The mailbox contains too many folders. By default, the mailbox cannot contain more than 1000 folders.

Supported by: 14.0, 14.1

152

NoFoldersFound

The mailbox contains no folders.

Supported by: 14.0, 14.1

153

ItemsLostAfterMove

After moving items to the destination folder, some of those items could not be found.

Supported by: 14.0, 14.1

154

FailureInMoveOperation

The mailbox server returned an unknown error while moving items.

Supported by: 14.0, 14.1

155

MoveCommandDisallowedForNonPersistentMoveAction

An ItemOperations command request (section 2.2.2.9) to move a conversation is missing the MoveAlways element (section 2.2.3.112).

Supported by: 14.0, 14.1

156

MoveCommandInvalidDestinationFolder

The destination folder for the move is invalid.

Supported by: 14.0, 14.1

160

AvailabilityTooManyRecipients

The command has reached the maximum number of recipients that it can request availability for.

Supported by: 14.0, 14.1

161

AvailabilityDLLimitReached

The size of the distribution list is larger than the availability service is configured to process.

Supported by: 14.0, 14.1

162

AvailabilityTransientFailure

Availability service request failed with a transient error.

Supported by: 14.0, 14.1

163

AvailabilityFailure

Availability service request failed with an error.

Supported by: 14.0, 14.1

164

BodyPartPreferenceTypeNotSupported

The BodyPartPreference node (as specified in [MS-ASAIRS] section 2.2.2.7) has an unsupported Type element (as specified in [MS-ASAIRS] section 2.2.2.22.4) value.

Supported by: 14.1

165

DeviceInformationRequired

The required DeviceInformation element (as specified in [MS-ASPROV] section 2.2.2.52) is missing in the Provision request.

Supported by: 14.1

166

InvalidAccountId

The AccountId (section 2.2.3.3) value is not valid.

Supported by: 14.1

167

AccountSendDisabled

The AccountId value specified in the request does not support sending email.

Supported by: 14.1

168

IRM_FeatureDisabled

The Information Rights Management feature is disabled.

Supported by: 14.1

169

IRM_TransientError

Information Rights Management encountered an error.

Supported by: 14.1

170

IRM_PermanentError

Information Rights Management encountered an error.

Supported by: 14.1

171

IRM_InvalidTemplateID

The Template ID value is not valid.

Supported by: 14.1

172

IRM_OperationNotPermitted

Information Rights Management does not support the specified operation.

Supported by: 14.1

173

NoPicture

The user does not have a contact photo.

Supported by: 14.1

174

PictureTooLarge

The contact photo exceeds the size limit set by the MaxSize element (section 2.2.3.100).

Supported by: 14.1

175

PictureLimitReached

The number of contact photos returned exceeds the size limit set by the MaxPictures element (section 2.2.3.99).

Supported by: 14.1

176

BodyPart_ConversationTooLarge

The conversation is too large to compute the body parts. Try requesting the body of the item again, without body parts.

Supported by: 14.1

177

MaximumDevicesReached

The user's account has too many device partnerships. Delete partnerships on the server before proceeding.

Supported by: 14.1

Show:
© 2014 Microsoft