Error and status codes in Microsoft Intune - Azure - Intune

Status codes for MDM managed Windows devices

Status code Error message What to do 30 (APP_CI_ENFORCEMENT_ERROR_RETRIEVING_CONTENT) Retrieving content Probable Cause: Job status 30 indicates that a user download of an app failed.

Likely causes for this may be:

The device lost Internet connectivity while the download was in progress.

The certificate issued to the device at the time of enrollment may have expired.

Mitigation:

Launch the Company Apps app from Control Panel on the device to confirm that the device certificate hasn't expired; if it has then you will need to re-enroll the device.

Confirm that the device is connected to the Internet and try to request the app again. 40 (APP_CI_ENFORCEMENT_IN_PROGRESS_CONTENT_DOWNLOADED) Content download complete 50 (APP_CI_ENFORCEMENT_IN_PROGRESS_INSTALLING) Installation in progress 60 (APP_CI_ENFORCEMENT_ERROR_INSTALLING) Installation Error occurred The app installation failed after download.

The code signing certificate with which app was signed is not present on the device.

A framework dependency on which the application depends is not found installed on the device.

Ensure that the code signing certificate with which your app was signed is present on the device and confirm with the admin that such a certificate was targeted for all enterprise enrolled Windows RT devices.

In case the installation failure is due to a missing framework dependency, the admin will have to re-publish the application again packaging the framework along with the application package.

The application package downloaded isn't a valid package, may have been corrupted, or may not be compatible with the OS version on the device. 70 (APP_CI_ENFORCEMENT_SUCCEEDED) Installation Success 80 (APP_CI_ENFORCEMENT_IN_PROGRESS) Uninstall in progress 90 (APP_CI_ENFORCEMENT_ERROR) Uninstall Error occurred 100 (APP_CI_ENFORCEMENT_SUCCEEDED) Uninstall Success 110 (APP_CI_ENFORCEMENT_ERROR) Content hash mismatch 120 (APP_CI_ENFORCEMENT_ERROR) SLK / side loading not enabled 130 (APP_CI_ENFORCEMENT_ERROR) MSADP license install failed No status (APP_CI_ENFORCEMENT_UNKNOWN) The status is currently unknown.

Company resource access (common errors)

Status code Hexadecimal error code Error message -2016330911 0x87D13B61 The user has installed the app before managed app installation could take place -2016330912 0x87D13B60 The app is scheduled for installation, but needs a redemption code to complete the transaction -2016341109 0x87D1138B iOS device has returned an error -2016341110 0x87D1138A iOS device has rejected the command due to incorrect format -2016341111 0x87D11389 iOS device has returned an unexpected Idle status -2016341112 0x87D11388 iOS device is currently busy

Errors returned by iOS/iPadOS devices

Company Portal errors

Error text in Company Portal HTTP status code Additional error information Internal server issue
Looks like you couldn't reach us due to an internal error on our server. Retry and then contact your IT admin if the issue continues. 500 error This error is likely caused by a problem on in the Intune service. The issue should be resolved on the Intune service side and is likely not due to issues on the customer side. Temporarily unavailable
Looks like you couldn't reach us because our service is temporarily unavailable. Retry and then contact your IT admin if the issue continues. 503 error This is likely due to a temporary Intune service issue, such as the service being under maintenance. The issue should be resolved on the Intune service side and is likely not due to issues on the customer side. Can't connect to server
Looks like you couldn't reach us. Retry and then contact your IT admin if the issue continues. Not associated with an HTTP status code A secure connection to the server could not be made, likely due to an SSL issue with the certs being used. This issue may be due to customer configurations not being compliant with Apple's requirements for App Transport Security (ATS). Something went wrong
The Company Portal client couldn't load. Retry and then contact your IT admin if the issue continues. 400 error Any error with an HTTP status code in the 400s that does not have a more specific error message will see this one. This is a client side error happening in the Company Portal app for iOS/iPadOS. Can't reach server
Looks like you couldn't reach us. Retry and then contact your IT admin if the issue continues. 500 error Any error with an HTTP status code in the 500s that does not have a more specific error message will see this one. This is a service side error happening in the Intune service.

Service errors

Status code Hexadecimal error code Error message -2016344108 0x87D107D4 DCMO(1204): Device Capability is disabled and User is allowed to re-enable it -2016344109 0x87D107D3 DCMO(1203): Device Capability is disabled and User is not allowed to re-enable it -2016344110 0x87D107D2 DCMO(1202): Enable operation is performed successfully but the Device Capability is currently detached -2016344111 0xF3FB4D95 DCMO(1201): Enable operation is performed successfully and the Device Capability is currently attached -2016344112 0x87D107D0 DCMO(1200): Operation is performed successfully -2016345595 0x87D10205 Syncml(517): The response to an atomic command was too large to fit in a single message. -2016345596 0x87D10204 Syncml(516): Command was inside Atomic element and Atomic failed. This command was not rolled back successfully. -2016345598 0x87D10202 Syncml(514): The SyncML command was not completed successfully, since the operation was already canceled before processing the command. -2016345599 0x87D10201 Syncml(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 Syncml(512): An application error occurred during the synchronization session. -2016345601 0x87D101FF Syncml(511): A severe error occurred in the server while processing the request. -2016345602 0x87D101FE Syncml(510): An error occurred while processing the request. The error is related to a failure in the recipient data store. -2016345603 0x87D101FD Syncml(509): Reserved for future use. -2016345604 0x87D101FC Syncml(508): An error occurred that necessitates a refresh of the current synchronization state of the client with the server. -2016345605 0x87D101FB Syncml(507): The error caused all SyncML commands within an Atomic element type to fail. -2016345606 0x87D101FA Syncml(506): An application error occurred while processing the request. -2016345607 0x87D101F9 Syncml(505): The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML Message. -2016345608 =0x87D101F8 Syncml(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 Syncml(503): The recipient is currently unable to handle the request due to a temporary overloading or maintenance of the recipient. -2016345610 0x87D101F6 Syncml(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 Syncml(501): The recipient does not support the command required to fulfill the request. -2016345612 0x87D101F4 Syncml(500): The recipient encountered an unexpected condition which prevented it from fulfilling the request -2016345684 0x87D101AC Syncml(428): Move failed -2016345685 0x87D101AB Syncml(427): Parent cannot be deleted since it contains children. -2016345686 0x87D101AA Syncml(426): Partial item not accepted. -2016345687 0x87D101A9 Syncml(425): The requested command failed because the sender does not have adequate access control permissions (ACL) on the recipient. -2016345688 0x87D101A8 Syncml(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 Syncml(423): The requested command failed because the "Soft Deleted" item was previously "Hard Deleted" on the server. -2016345690 0x87D101A6 Syncml(422): The requested command failed on the server because the CGI scripting in the LocURI was incorrectly formed. -2016345691 0x87D101A5 Syncml(421): The requested command failed on the server because the specified search grammar was not known. -2016345692 0x87D101A4 Syncml(420): The recipient has no more storage space for the remaining synchronization data. -2016345693 0x87D101A3 Syncml(419): The client request created a conflict which was resolved by the server command winning. -2016345694 0x87D101A2 Syncml(418): The requested Put or Add command failed because the target already exists. -2016345695 0x87D101A1 Syncml(417): The request failed at this time and the originator should retry the request later. -2016345696 0x87D101A0 Syncml(416): The request failed because the specified byte size in the request was too big. -2016345697 0x87D1019F Syncml(415): Unsupported media type or format. -2016345698 0x87D1019E Syncml(414): The requested command failed because the target URI is too long for what the recipient is able or willing to process. -2016345699 0x87D1019D Syncml(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 Syncml(412): The requested command failed on the recipient because it was incomplete or incorrectly formed. -2016345701 0x87D1019B Syncml(411): The requested command must be accompanied by byte size or length information in the Meta element type. -2016345702 0x87D1019A Syncml(410): The requested target is no longer on the recipient and no forwarding URI is known. -2016345703 0x87D10199 Syncml(409): The requested failed because of an update conflict between the client and server versions of the data. -2016345704 0x87D10198 Syncml(408): An expected message was not received within the required period of time. -2016345705 0x87D10197 Syncml(407): The requested command failed because the originator must provide proper authentication. -2016345706 0x87D10196 Syncml(406): The requested command failed because an optional feature in the request was not supported. -2016345707 0x87D10195 Syncml(405): The requested command is not allowed on the target. -2016345708 0x87D10194 Syncml(404): The requested target was not found. -2016345709 0x87D10193 Syncml(403): The requested command failed, but the recipient understood the requested command. -2016345710 0x87D10192 Syncml(402): The requested command failed because proper payment is needed. -2016345711 0x87D10191 Syncml(401): The requested command failed because the requestor must provide proper authentication. -2016345712 0x87D10190 Syncml(400): The requested command could not be performed because of malformed syntax in the command. -2016345807 0x87D10131 Syncml(305): The requested target must be accessed through the specified proxy URI. -2016345808 0x87D10130 Syncml(304):The requested SyncML command was not executed on the target. -2016345809 0x87D1012F Syncml(303): The requested target can be found at another URI. -2016345810 0x87D1012E Syncml(302): The requested target has temporarily moved to a different URI. -2016345811 0x87D1012D Syncml(301): The requested target has a new URI. -2016345812 0x87D1012C Syncml(300): The requested target is one of a number of multiple alternatives requested target. -2016345896 0x87D100D8 Syncml(216): A command was inside Atomic element and Atomic failed. This command was rolled back successfully. -2016345897 0x87D100D7 Syncml(215): A command was not executed, as a result of user interaction and user chose not to accept the choice. -2016345898 0x87D100D6 Syncml(214): Operation canceled. The SyncML command completed successfully, but no more commands will be processed within the session. -2016345899 0x87D100D5 Syncml(213): Chunked item accepted and buffered -2016345900 0x87D100D4 Syncml(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 Syncml(211): Item not deleted. The requested item was not found. It could have been previously deleted. -2016345902 0x87D100D2 Syncml(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.

Next steps

Contact Microsoft Support to get support in Microsoft Intune .