Windows MDM - SyncML error codes
Windows MDM utilizes the SyncML protocol to communicate with target devices. Below are the OMA error codes associated with SyncML.
Error Code | Hexadecimal Error Code | Syncml Error Code | Error message |
-2016345595 | 0x87D10205 | 517 | The response to an atomic command was too large to fit in a single message. |
-2016345596 | 0x87D10204 | 516 | Command was inside Atomic element and Atomic failed. This command was not rolled back successfully. |
-2016345598 | 0x87D10202 | 514 | The SyncML command was not completed successfully, since the operation was already canceled before processing the command. |
-2016345599 | 0x87D10201 | 513 | The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol used in the request SyncML Message. |
-2016345600 | 0x87D10200 | 512 | An application error occurred during the synchronization session. |
-2016345601 | 0x87D101FF | 511 | A severe error occurred in the server while processing the request. |
-2016345602 | 0x87D101FE | 510 | An error occurred while processing the request. The error is related to a failure in the recipient data store. |
-2016345603 | 0x87D101FD | 509 | Reserved for future use. |
-2016345604 | 0x87D101FC | 508 | An error occurred that necessitates a refresh of the current synchronization state of the client with the server. |
-2016345605 | 0x87D101FB | 507 | The error caused all SyncML commands within an Atomic element type to fail. |
-2016345606 | 0x87D101FA | 506 | An application error occurred while processing the request. |
-2016345607 | 0x87D101F9 | 505 | The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML Message. |
-2016345608 | =0x87D101F8 | 504 | The recipient, while acting as a gateway or proxy, did not receive a timely response from the upstream recipient specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary recipient (e.g. DNS) it needed to access in attempting to complete the request. |
-2016345609 | 0x87D101F7 | 503 | The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the recipient. |
-2016345610 | 0x87D101F6 | 502 | The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient it accessed in attempting to fulfill the request. |
-2016345611 | 0x87D101F5 | 501 | The recipient does not support the command required to fulfill the request. |
-2016345612 | 0x87D101F4 | 500 | The recipient encountered an unexpected condition which prevented it from fulfilling the request |
-2016345684 | 0x87D101AC | 428 | Move failed |
-2016345685 | 0x87D101AB | 427 | Parent cannot be deleted since it contains children. |
-2016345686 | 0x87D101AA | 426 | Partial item not accepted. |
-2016345687 | 0x87D101A9 | 425 | The requested command failed because the sender does not have adequate access control permissions (ACL) on the recipient. |
-2016345688 | 0x87D101A8 | 424 | The chunked object was received, but the size of the received object did not match the size declared within the first chunk. |
-2016345689 | 0x87D101A7 | 423 | The requested command failed because the "Soft Deleted" item was previously "Hard Deleted" on the server. |
-2016345690 | 0x87D101A6 | 422 | The requested command failed on the server because the CGI scripting in the LocURI was incorrectly formed. |
-2016345691 | 0x87D101A5 | 421 | The requested command failed on the server because the specified search grammar was not known. |
-2016345692 | 0x87D101A4 | 420 | The recipient has no more storage space for the remaining synchronization data. |
-2016345693 | 0x87D101A3 | 419 | The client request created a conflict which was resolved by the server command winning. |
-2016345694 | 0x87D101A2 | 418 | The requested Put or Add command failed because the target already exists. |
-2016345695 | 0x87D101A1 | 417 | The request failed at this time and the originator should retry the request later. |
-2016345696 | 0x87D101A0 | 416 | The request failed because the specified byte size in the request was too big. |
-2016345697 | 0x87D1019F | 415 | Unsupported media type or format. |
-2016345698 | 0x87D1019E | 414 | The requested command failed because the target URI is too long for what the recipient is able or willing to process. |
-2016345699 | 0x87D1019D | 413 | The recipient is refusing to perform the requested command because the requested item is larger than the recipient is able or willing to process. |
-2016345700 | 0x87D1019C | 412 | The requested command failed on the recipient because it was incomplete or incorrectly formed. |
-2016345701 | 0x87D1019B | 411 | The requested command must be accompanied by byte size or length information in the Meta element type. |
-2016345702 | 0x87D1019A | 410 | The requested target is no longer on the recipient and no forwarding URI is known. |
-2016345703 | 0x87D10199 | 409 | The requested failed because of an update conflict between the client and server versions of the data. |
-2016345704 | 0x87D10198 | 408 | An expected message was not received within the required period of time. |
-2016345705 | 0x87D10197 | 407 | The requested command failed because the originator must provide proper authentication. |
-2016345706 | 0x87D10196 | 406 | The requested command failed because an optional feature in the request was not supported. |
-2016345707 | 0x87D10195 | 405 | The requested command is not allowed on the target. |
-2016345708 | 0x87D10194 | 404 | The requested target was not found. |
-2016345709 | 0x87D10193 | 403 | The requested command failed, but the recipient understood the requested command. |
-2016345710 | 0x87D10192 | 402 | The requested command failed because proper payment is needed. |
-2016345711 | 0x87D10191 | 401 | The requested command failed because the requestor must provide proper authentication. |
-2016345712 | 0x87D10190 | 400 | The requested command could not be performed because of malformed syntax in the command. |
-2016345807 | 0x87D10131 | 305 | The requested target must be accessed through the specified proxy URI. |
-2016345808 | 0x87D10130 | 304 | The requested SyncML command was not executed on the target. |
-2016345809 | 0x87D1012F | 303 | The requested target can be found at another URI. |
-2016345810 | 0x87D1012E | 302 | The requested target has temporarily moved to a different URI. |
-2016345811 | 0x87D1012D | 301 | The requested target has a new URI. |
-2016345812 | 0x87D1012C | 300 | The requested target is one of a number of multiple alternatives requested target. |
-2016345896 | 0x87D100D8 | 216 | A command was inside Atomic element and Atomic failed. This command was rolled back successfully. |
-2016345897 | 0x87D100D7 | 215 | A command was not executed, as a result of user interaction and user chose not to accept the choice. |
-2016345898 | 0x87D100D6 | 214 | Operation canceled. The SyncML command completed successfully, but no more commands will be processed within the session. |
-2016345899 | 0x87D100D5 | 213 | Chunked item accepted and buffered |
-2016345900 | 0x87D100D4 | 212 | Authentication accepted. No further authentication is needed for the remainder of the synchronization session. This response code can only be used in response to a request in which the credentials were provided. |
-2016345901 | 0x87D100D3 | 211 | Item not deleted. The requested item was not found. It could have been previously deleted. |
-2016345902 | 0x87D100D2 | 210 | Delete without archive. The response indicates that the requested data was successfully deleted, but that it was not archived prior to deletion because this OPTIONAL feature was not supported by the implementation. |
-2016345903 | 0x87D100D1 | Conflict resolved with duplicate. The response indicates that the request created an update conflict; which was resolved with a duplication of the client's data being created in the server database. The response includes both the target URI of the duplicate in the Item of the Status. In addition, in the case of a two-way synchronization, an Add command is returned with the duplicate data definition. | |
-2016345904 | 0x87D100D0 | Conflict resolved with client's command "winning". The response indicates that there was an update conflict; which was resolved by the client command winning. | |
-2016345905 | 0x87D100CF | Conflict resolved with merge. The response indicates that the request created a conflict; which was resolved with a merge of the client and server instances of the data. The response includes both the Target and Source URLs in the Item of the Status. In addition, a Replace command is returned with the merged data. | |
-2016345906 | 0x87D100CE | The response indicates that only part of the command was completed. If the remainder of the command can be completed later, then when completed another appropriate completion request status code SHOULD be created. | |
-2016345907 | 0x87D100CD | The source SHOULD update their content. The originator of the request is being told that their content SHOULD be synchronized to get an up-to-date version. | |
-2016345908 | 0x87D100CC | The request was successfully completed but no data is being returned. The response code is also returned in response to a Get when the target has no content. | |
-2016345909 | 0x87D100CB | Non-authoritative response. The request is being responded to by an entity other than the one targeted. The response is only to be returned when the request would have been resulted in a 200 response code from the authoritative target. | |
-2016345910 | 0x87D100CA | Accepted for processing. The request to either run a remote execution of an application or to alert a user or application was successfully performed. | |
-2016345911 | 0x87D100C9 | The requested item was added. | |
-2016345912 | 0x87D100C8 | The SyncML command completed successfully. | |
-2016346011 | 0x87D10065 | The specified SyncML command is being carried out, but has not yet completed. |
