- Article
- 17 minutes to read
(Video) Intune Tutorial 37 - Troubleshooting Windows Device Enrolment Errors in Intune
See Also
Solution for Bad Gateway errors: Azure Application GatewayAzure AD Connect: Troubleshoot Azure AD connection - Microsoft EnterUse Intune to manage Microsoft Defender for Endpoint Security on devices not enrolled in Microsoft IntuneAzure Active Directory Connect Health operations - Microsoft sign-in(Video) How to Resolve Windows Device not Enrolling in Microsoft Intune | Windows 10 not Enrolling in Intune
This article lists common errors, status codes, descriptions, and possible solutions when accessing corporate resources. Use this information to troubleshoot access issues when using Microsoft Intune.
(Video) How to Set Up Microsoft Intune
If you need help, seeGet support for Microsoft Endpoint Manager.
(Video) S02E12 - OMA-Goodness w/ Jeff Gilbert - How to Configure CSP & OMA-URI in Microsoft Intune - (I.T)
Status codes for MDM managed Windows devices
| Statuscode | error message | Do |
|---|---|---|
| 10 (APP_CI_ENFORCEMENT_IN_PROGRESS) | Installation in progress | |
| 20 (APP_CI_ENFORCEMENT_IN_PROGRESS_WAITING_CONTENT) | Waiting for content | |
| 30 (APP_CI_ENFORCEMENT_ERROR_RETRIEVING_CONTENT) | Content Retrieval | Likely Cause: Job status 30 indicates that an application download by the user failed. Possible causes for this can be: The device lost internet connection during the download. The certificate issued to the device at the time of registration may have expired. mitigation: Launch the Corporate Apps app from the Control Panel on the device to confirm that the device certificate has not expired; In this case, you must register the device again. Make sure the device is connected to the internet and try to request the app again. |
| 40 (APP_CI_ENFORCEMENT_IN_PROGRESS_CONTENT_DOWNLOADED) | Full content download | |
| 50 (APP_CI_ENFORCEMENT_IN_PROGRESS_INSTALLING) | Installation in progress | |
| 60 (APPLICATION_CI_ENFORCEMENT_ERROR_INSTALLATION) | An installation error has occurred | Application installation failed after download. The code signing certificate used to sign the application is not present on the device. A framework dependency that the application depends on is not installed on the device. Ensure that the code signing certificate used to sign your app is present on the device, and confirm with your administrator that the code signing certificate is intended for all enterprise-enrolled Windows RT devices. In case the installation error is due to a missing framework dependency, the admin needs to re-publish the app by packaging the framework along with the app package. The downloaded application package is not a valid package, it may be corrupted or incompatible with the device operating system version. |
| 70 (APP_CI_ENFORCEMENT_SUCCEEDED) | Installation successful | |
| 80 (APP_CI_ENFORCEMENT_IN_PROGRESS) | Uninstall in progress | |
| 90 (APP_CI_ENFORCEMENT_ERROR) | An uninstall error has occurred | |
| 100 (APP_CI_ENFORCEMENT_SUCCEEDED) | Uninstall successful | |
| 110 (APPLICATION_CI_ENFORCEMENT_ERROR) | Content hash mismatch | |
| 120 (APPLICATION_CI_ENFORCEMENT_ERROR) | SLK/Sideload not activated | |
| 130 (APP_CI_ENFORCEMENT_ERROR) | MSADP license installation failed | |
| Unspecified (APP_CI_ENFORCEMENT_UNKNOWN) | n / a | The status is currently unknown. |
Access to corporate resources (common mistakes)
| Statuscode | Hexadecimal error code | error message |
|---|---|---|
| -2016281101 | 0x87D1FDF3 | MDM CRP request not found |
| -2016281102 | 0x87D1FDF2 | NDES URL not found |
| -2016281103 | 0x87D1FDF1 | MDM CRP certificate information not found |
| -2016281104 | 0x87D1FDF0 | MDM CI certificate information not found |
| -2016281105 | 0x87D1FDEF | Error evaluating rule |
| -2016281106 | 0x87D1FDEE | Does not apply because he lost in conflict resolution |
| -2016281107 | 0x87D1FDED | Unsupported configuration detection source |
| -2016281108 | 0x87D1FDEC | Reference configuration not found in CI |
| -2016281109 | 0x87D1FDEB | Data type conversion failed |
| -2016281110 | 0x87D1FDEA | Invalid CIM configuration parameter |
| -2016281111 | 0x87D1FDE9 | Does not apply to this device |
| -2016281112 | 0x87D1FDE8 | failed fix |
| -2016330905 | 0x87D13B67 | Application status is unknown |
| -2016330906 | 0x87D13B66 | The app is managed but the user deleted it |
| -2016330907 | 0x87D13B65 | The device redeems the voucher code |
| -2016330908 | 0x87D13B64 | Application installation failed |
| -2016330909 | 0x87D13B63 | The user declined the offer to update the app. |
| -2016330910 | 0x87D13B62 | The user declined the offer to install the app. |
| -2016330911 | 0x87D13B61 | The user installed the app before managed app installation could take place. |
| -2016330912 | 0x87D13B60 | The app is scheduled to be installed, but you'll need a redemption code to complete the transaction |
| -2016341109 | 0x87D1138B | The iOS device returned an error |
| -2016341110 | 0x87D1138A | The iOS device rejected the command due to an incorrect format |
| -2016341111 | 0x87D11389 | The iOS device returned from an unexpected sleep state |
| -2016341112 | 0x87D11388 | The iOS device is currently busy |
Errors returned from iOS/iPadOS devices
Company portal error
| Error text in the company portal | HTTP-Statuscode | Additional error information |
|---|---|---|
| Internal Server Problem It seems you were unable to contact us due to an internal error on our server. Please try again and then contact your IT admin if the problem persists. | error 500 | This error is likely caused by an issue in the Intune service. The issue should be resolved on the Intune service side and is not likely caused by issues on the client side. |
| Temporary not available It seems you couldn't contact us because our service is temporarily unavailable. Please try again and then contact your IT admin if the problem persists. | Error 503 | This is likely due to a transient issue with the Intune service, such as: B. that the service is under maintenance. The issue should be resolved on the Intune service side and is not likely caused by issues on the client side. |
| I can't connect to the server It seems you couldn't contact us. Please try again and then contact your IT admin if the problem persists. | Not associated with an HTTP status code | A secure connection to the server could not be established, probably due to an SSL problem with the certificates used. This issue can be caused by client configurations that don't meet Apple's requirements for App Transport Security (ATS). |
| Something went wrong The Company Portal client could not be loaded. Please try again and then contact your IT admin if the problem persists. | Error 400 | Any error with an HTTP status code in 400 that doesn't have a more specific error message will see this. This is a client-side error that occurs in the Company Portal app for iOS/iPadOS. |
| The server cannot be reached It seems you couldn't contact us. Please try again and then contact your IT admin if the problem persists. | error 500 | Any error with an HTTP status code in 500 that doesn't have a more specific error message will see this. This is a service-side error that occurs in the Intune service. |
service error
| Statuscode | Hexadecimal error code | error message |
|---|---|---|
| -2016299111 | 0x87D1B799 | Internal error |
| -2016299112 | 0x87D1B798 | Internal error |
| -2016300111 | 0x87D1B3B1 | 36001:(internal error) |
| -2016300112 | 0x87D1B3B0 | 36000:Mobile already configured |
| -2016301110 | 0x87D1AFCA | 35002:Multiple sources on a single payload |
| -2016301111 | 0x87D1AFC9 | 35001: Font installation failed |
| -2016301112 | 0x87D1AFC8 | 35000: Invalid font data |
| -2016302109 | 0x87D1ABE3 | 34003: Invalid Kerberos principal name |
| -2016302110 | 0x87D1ABE2 | 34002: Missing Kerberos principal name |
| -2016302111 | 0x87D1ABE1 | 34001:Invalid URL pattern match |
| -2016302112 | 0x87D1ABE0 | 34000: Invalid application identifier match pattern |
| -2016304112 | 0x87D1A410 | 32000: Too many applications |
| -2016305111 | 0x87D1A029 | 31001: Configuration cannot be applied |
| -2016305112 | 0x87D1A028 | 31000: Credentials cannot be applied |
| -2016306111 | 0x87D19C41 | 30001: Timeout |
| -2016306112 | 0x87D19C40 | 30000: Authentication failed |
| -2016307109 | 0x87D1985B | 29003: Incorrect certificate data |
| -2016307110 | 0x87D1985A | 29002: |
| -2016307111 | 0x87D19859 | 29001: |
| -2016307112 | 0x87D19858 | 29000:Unattended device |
| -2016308110 | 0x87D19472 | 28002: Unable to set wallpaper |
| -2016308111 | 0x87D19471 | 28001: bad background image |
| -2016308112 | 0x87D19470 | 28000: Unknown item |
| -2016310111 | 0x87D18CA1 | 26001: File-level encryption is not supported |
| -2016310112 | 0x87D18CA0 | 26000: Block-level encryption is not supported |
| -2016311110 | 0x87D188BA | 25002: cannot be deleted |
| -2016311111 | 0x87D188B9 | 25001: Unable to install |
| -2016311112 | 0x87D188B8 | 25000: bad profile |
| -2016312109 | 0x87D184D3 | 24003: Bad end profile |
| -2016312110 | 0x87D184D2 | 24002: Incorrect identity payload |
| -2016312111 | 0x87D184D1 | 24001: Attribute dictionary cannot be signed |
| -2016312112 | 0x87D184D0 | 24000: Cannot create attribute dictionary |
| -2016313110 | 0x87D180EA | 23002: Invalid server certificate |
| -2016313111 | 0x87D180E9 | 23001: Invalid response from server |
| -2016313112 | 0x87D180E8 | 23000: Bad identity |
| -2016314099 | 0x87D17D0D | 22013: Invalid PKIO operation response |
| -2016314100 | 0x87D17D0C | 22012: CA certificate cannot be saved |
| -2016314101 | 0x87D17D0B | 22011: Cannot generate CSR |
| -2016314102 | 0x87D17D0A | 22010: Temporary identity cannot be saved |
| -2016314103 | 0x87D17D09 | 22009: A temporary identity cannot be created |
| -2016314104 | 0x87D17D08 | 22008: Unable to create identity |
| -2016314105 | 0x87D17D07 | 22007: Invalid signed certificate |
| -2016314106 | 0x87D17D06 | 22006: Insufficient CACaps |
| -2016314107 | 0x87D17D05 | 22005:Network error |
| -2016314108 | 0x87D17D04 | 22004: Unsupported certificate configuration |
| -2016314109 | 0x87D17D03 | 22003: Invalid RAR response |
| -2016314110 | 0x87D17D02 | 22002: Invalid CAR response |
| -2016314111 | 0x87D17D01 | 22001: Unable to generate key pair |
| -2016314112 | 0x87D17D00 | 22000: Invalid password usage |
| -2016315105 | 0x87D1791F | 21007: Account cannot be verified |
| -2016315106 | 0x87D1791E | 21006: Certificate cannot be decrypted |
| -2016315107 | 0x87D1791D | 21005:Account not unique (email profile already exists on the device) |
| -2016315108 | 0x87D1791C | 21004: Unable to create account |
| -2016315109 | 0x87D1791B | 21003:No hostname |
| -2016315110 | 0x87D1791A | 21002: Server encryption policy cannot be met |
| -2016315111 | 0x87D17919 | 21001: The server policy cannot be complied with |
| -2016315112 | 0x87D17918 | 21000: Unable to get server policy |
| -2016316110 | 0x87D17532 | 20002: Non-unique account |
| -2016316111 | 0x87D17531 | 20001:No hostname |
| -2016316112 | 0x87D17530 | 20000: Unable to create account |
| -2016317110 | 0x87D1714A | 19002: Non-unique account |
| -2016317111 | 0x87D17149 | 19001:No hostname |
| -2016317112 | 0x87D17148 | 19000: Unable to create account |
| -2016318110 | 0x87D16D62 | 18002: Invalid credentials |
| -2016318111 | 0x87D16D61 | 18001: Host cannot be deleted |
| -2016318112 | 0x87D16D60 | 18000: Unknown error |
| -2016319110 | 0x87D1697A | 17002: Non-unique account |
| -2016319111 | 0x87D16979 | 17001:No hostname |
| -2016319112 | 0x87D16978 | 17000: Unable to create account |
| -2016320110 | 0x87D16592 | 16002: Non-unique account |
| -2016320111 | 0x87D16591 | 16001:No hostname |
| -2016320112 | 0x87D16590 | 16000: Unable to create subscription |
| -2016321109 | 0x87D161AB | 15003: Invalid certificate |
| -2016321110 | 0x87D161AA | 15002: Unable to lock down network settings |
| -2016321111 | 0x87D161A9 | 15001: VPN cannot be removed |
| -2016321112 | 0x87D161A8 | 15000: VPN cannot be installed |
| -2016322110 | 0x87D15DC2 | 14002: Cloud configuration already exists |
| -2016322111 | 0x87D15DC1 | 14001:Device blocked |
| -2016322112 | 0x87D15DC0 | 14000: Invalid field |
| -2016323107 | 0x87D159DD | 13005: Proxy cannot be configured |
| -2016323108 | 0x87D159DC | 13004: EAP cannot be configured |
| -2016323109 | 0x87D159DB | 13003: WLAN configuration cannot be created |
| -2016323110 | 0x87D159DA | 13002: Password required |
| -2016323111 | 0x87D159D9 | 13001:Username required |
| -2016323112 | 0x87D159D8 | 13000: Unable to install |
| -2016324070 | 0x87D1561A | 12042: unknown area code |
| -2016324071 | 0x87D15619 | 12041: Unknown language code |
| -2016324072 | 0x87D15618 | 12040: iTunes Store login required |
| -2016324073 | 0x87D15617 | 12039: (unused) |
| -2016324074 | 0x87D15616 | 12038: Unmanaged application |
| -2016324075 | 0x87D15615 | 12037:Invalid coupon code |
| -2016324076 | 0x87D15614 | 12036: The application cannot be deleted in the current state |
| -2016324077 | 0x87D15613 | 12035: The app cannot be purchased |
| -2016324078 | 0x87D15612 | 12034: URL is not HTTPS |
| -2016324079 | 0x87D15611 | 12033: Invalid manifest |
| -2016324080 | 0x87D15610 | 12032: Too many applications in the manifest |
| -2016324081 | 0x87D1560F | 12031: Application installation disabled |
| -2016324082 | 0x87D1560E | 12030: Invalid URL |
| -2016324083 | 0x87D1560D | 12029: Unmanaged application |
| -2016324084 | 0x87D1560C | 12028: Without waiting for salvation |
| -2016324085 | 0x87D1560B | 12027: No application |
| -2016324086 | 0x87D1560A | 12026:Application already queued |
| -2016324087 | 0x87D15609 | 12025: Application already installed |
| -2016324088 | 0x87D15608 | 12024: The application manifest could not be validated |
| -2016324089 | 0x87D15607 | 12023: The application ID could not be validated |
| -2016324090 | 0x87D15606 | 12022: Invalid topic |
| -2016324091 | 0x87D15605 | 12021: Invalid request type |
| -2016324092 | 0x87D15604 | 12020: Not authorized by the server |
| -2016324093 | 0x87D15603 | 12019: Custody secret cannot be copied |
| -2016324094 | 0x87D15602 | 12018: Escrow Key Vault data cannot be copied |
| -2016324095 | 0x87D15601 | 12017: Cannot create escrow key repository |
| -2016324096 | 0x87D15600 | 12016: missing identity |
| -2016324097 | 0x87D155FF | 12015: Unable to get embed token |
| -2016324098 | 0x87D155FE | 12014: Unmanaged provisioning profile |
| -2016324099 | 0x87D155FD | 12013: Unmanaged profile |
| -2016324100 | 0x87D155FC | 12012: MDM replacement conflict |
| -2016324101 | 0x87D155FB | 12011: Invalid MDM configuration |
| -2016324102 | 0x87D155FA | 12010: Internal Inkonsistenzfehler |
| -2016324103 | 0x87D155F9 | 12009:Invalid replacement profile |
| -2016324104 | 0x87D155F8 | 12008: Request with wrong format |
| -2016324105 | 0x87D155F7 | 12007: Unauthorized |
| -2016324106 | 0x87D155F6 | 12006: Redirect denied |
| -2016324107 | 0x87D155F5 | 12005: Certificate cannot be found |
| -2016324108 | 0x87D155F4 | 12004: Invalid push certificate |
| -2016324109 | 0x87D155F3 | 12003: Invalid query response |
| -2016324110 | 0x87D155F2 | 12002: Unable to register |
| -2016324111 | 0x87D155F1 | 12001: Multiple instances of MDM |
| -2016324112 | 0x87D155F0 | 12000: Invalid access rights |
| -2016325111 | 0x87D15209 | 11001:Custom APN already installed |
| -2016325112 | 0x87D15208 | 11000: APN cannot be installed |
| -2016326111 | 0x87D14E21 | 10001: Invalid signer |
| -2016326112 | 0x87D14E20 | 10000: Default settings cannot be installed |
| -2016327106 | 0x87D14A3E | 9006: The certificate is not an identity |
| -2016327107 | 0x87D14A3D | 9005: bad certificate |
| -2016327108 | 0x87D14A3C | 9004: Root certificate cannot be saved |
| -2016327109 | 0x87D14A3B | 9003:WAPI data cannot be saved |
| -2016327110 | 0x87D14A3A | 9002: Certificate cannot be saved |
| -2016327111 | 0x87D14A39 | 9001: Too many certificates in a payload |
| -2016327112 | 0x87D14A38 | 9000: Invalid password |
| -2016328112 | 0x87D14650 | 8000:Webclip cannot be installed |
| -2016329105 | 0x87D1426F | 7007: SMTP account is configured incorrectly |
| -2016329106 | 0x87D1426E | 7006: Incorrectly configured POP account |
| -2016329107 | 0x87D1426D | 7005: IMAP account configured incorrectly |
| -2016329108 | 0x87D1426C | 7004: The SMIME certificate is incorrect |
| -2016329109 | 0x87D1426B | 7003: SMIME certificate not found |
| -2016329110 | 0x87D1426A | 7002: An unknown error occurred during validation |
| -2016329111 | 0x87D14269 | 7001: Invalid credentials |
| -2016329112 | 0x87D14268 | 7000: Host cannot be deleted |
| -2016330110 | 0x87D13E82 | 6002: Cannot build query |
| -2016330111 | 0x87D13E81 | 6001:Empty string |
| -2016330112 | 0x87D13E80 | 6000: Keychain system error |
| -2016331097 | 0x87D13AA7 | 5015: Unable to set grace period |
| -2016331098 | 0x87D13AA6 | 5014: Unable to set passcode |
| -2016331099 | 0x87D13AA5 | 5013: Access code cannot be deleted |
| -2016331100 | 0x87D13AA4 | 5012: (unused) |
| -2016331101 | 5011: Wrong access code | |
| -2016331102 | 5010:Device blocked | |
| -2016331103 | 0x87D13AA4 | 5009: (unused) |
| -2016331104 | 0x87D13AA0 | 5008: Password too new |
| -2016331105 | 0x87D13A9F | 5007: Access code expired |
| -2016331106 | 0x87D13AA3 | 5006: Passcode requires alphabetic characters |
| -2016331107 | 0x87D13A9D | 5005: Access code requires number |
| -2016331108 | 0x87D13A9C | 5004: Passcode has ascending and descending characters |
| -2016331109 | 0x87D13A9B | 5003: Passcode contains repeated characters |
| -2016331110 | 0x87D13A9A | 5002: Not enough complex characters |
| -2016331111 | 0x87D13A99 | 5001: Too few unique characters |
| -2016331112 | 0x87D13A98 | 5000: Passcode too short |
| -2016332093 | 0x87D136C3 | 4019: Multiple app crash payloads |
| -2016332094 | 0x87D136C2 | 4018: Multiple payloads from APN or cell |
| -2016332095 | 0x87D136C1 | 4017: Multiple global HTTPProxy payloads |
| -2016332096 | 0x87D136C0 | 4016:(Internal error) |
| -2016332097 | 0x87D136BF | 4015: Replacement profile does not contain MDM payload |
| -2016332098 | 0x87D136BE | 4014: No device identity available |
| -2016332099 | 0x87D136BD | 4013:Update failed |
| -2016332100 | 0x87D136BC | 4012: The profile cannot be updated |
| -2016332101 | 0x87D136BB | 4011: The final profile is not a configuration profile |
| -2016332102 | 0x87D136BA | 4010: Updated profile does not have the same identifier |
| -2016332103 | 0x87D136B9 | 4009:Device blocked |
| -2016332104 | 0x87D136B8 | 4008: Mismatched certificates |
| -2016332105 | 0x87D136B7 | 4007: Unknown file format |
| -2016332106 | 0x87D136B6 | 4006: The deletion date of the profile is earlier |
| -2016332107 | 0x87D136B5 | 4005: The access code does not match |
| -2016332108 | 0x87D136B4 | 4004: Installation aborted by user |
| -2016332109 | 0x87D136B3 | 4003: Profile not queued for installation |
| -2016332110 | 0x87D136B2 | 4002: Duplicate UUID |
| -2016332111 | 0x87D136B1 | 4001: Installation failed |
| -2016332112 | 0x87D136B0 | 4000: Unable to parse profile |
| -2016333111 | 0x87D132C9 | 3001: Inconsistent sense of value comparison (internal error) |
| -2016333112 | 0x87D132C8 | 3000: Constraint Sense inconsistent (internal error) |
| -2016334108 | 0x87D12EE4 | 2004: Field value is not supported |
| -2016334109 | 0x87D12EE3 | 2003: Wrong data type in field |
| -2016334110 | 0x87D12EE2 | 2002: Mandatory field is missing |
| -2016334111 | 0x87D12EE1 | 2001: Unsupported payload version |
| -2016334112 | 0x87D12EE0 | 2000: Malformed payload |
| -2016335102 | 0x87D12B02 | 1010: Unsupported field value |
| -2016335103 | 0x87D12B01 | 1009:Error installing profile |
| -2016335104 | 0x87D12B00 | 1008: Ambiguous payload identifiers |
| -2016335105 | 0x87D12AFF | 1007: Non-unique UUID |
| -2016335106 | 0x87D12AFE | 1006: Cannot decrypt |
| -2016335107 | 0x87D12AFD | 1005:Empty profile |
| -2016335108 | 0x87D12AFC | 1004: Wrong signature |
| -2016335109 | 0x87D12AFB | 1003: Incorrect data type in field |
| -2016335110 | 0x87D12AFA | 1002: Mandatory field is missing |
| -2016335111 | 0x87D12AF9 | 1001: Unsupported profile version |
| -2016335112 | 0x87D12AF8 | 1000: faulty profile |
OMA Response Codes
| Statuscode | Hexadecimal error code | error message |
|---|---|---|
| -2016344008 | 0x87D10838 | (1404): Certificate access denied |
| -2016344009 | 0x87D10837 | (1403): Certificate not found |
| -2016344010 | 0x87D10836 | DCMO(1402): Operation failed |
| -2016344011 | 0x87D10835 | DCMO(1401): The user has chosen not to accept the operation when prompted |
| -2016344012 | 0x87D10834 | DCMO (1400): Client error |
| -2016344108 | 0x87D107D4 | DCMO (1204) - The device function is disabled and can be re-enabled by the user |
| -2016344109 | 0x87D107D3 | DCMO (1203) - The device feature is disabled and cannot be re-enabled by the user |
| -2016344110 | 0x87D107D2 | DCMO(1202): The activation process was successful, but the device function is currently offline |
| -2016344111 | 0xF3FB4D95 | DCMO(1201): The activation process was successful and the device function is currently connected |
| -2016344112 | 0x87D107D0 | DCMO(1200): The operation is successful |
| -2016345595 | 0x87D10205 | Syncml(517): The response to an atomic command was too large to fit in a single message. |
| -2016345596 | 0x87D10204 | Syncml(516): The command was inside the atomic element and the atomic failed. This command was not rolled back successfully. |
| -2016345598 | 0x87D10202 | Syncml(514): The SyncML command did not complete successfully because the operation was canceled before the command was processed. |
| -2016345599 | 0x87D10201 | Syncml(513): The recipient does not support or refuses to support the specified version of the SyncML synchronization protocol used in the SyncML Request message. |
| -2016345600 | 0x87D10200 | syncml(512): An application error occurred during the synchronization session. |
| -2016345601 | 0x87D101FF | Syncml(511): A fatal server error occurred while processing the request. |
| -2016345602 | 0x87D101FE | Syncml(510): An error occurred while processing the request. The error relates to an error in the receiver data store. |
| -2016345603 | 0x87D101FD | Syncml(509): Reserved for future use. |
| -2016345604 | 0x87D101FC | Syncml(508): An error has occurred that requires an update of the client's current synchronization status with the server. |
| -2016345605 | 0x87D101FB | Syncml(507): The bug caused all SyncML commands inside 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 the SyncML DTD used in the Request SyncML message. |
| -2016345608 | =0x87D101F8 | Syncml(504): The receiver acting as a gateway or proxy did not receive a timely response from the upstream receiver specified by the URI (e.g. HTTP, FTP, LDAP) or another auxiliary receiver (e.g. DNS) is specified ) I had to access when trying to complete the application. |
| -2016345609 | 0x87D101F7 | Syncml(503): The receiver is currently unable to process the request due to temporary overload or receiver maintenance. |
| -2016345610 | 0x87D101F6 | Syncml(502): The receiver, acting as a gateway or proxy, received an invalid response from the upstream receiver it accessed when 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 that prevented it from fulfilling the request |
| -2016345684 | 0x87D101AC | syncml(428): Move failed |
| -2016345685 | 0x87D101AB | Syncml(427): Parent cannot be deleted because it contains children. |
| -2016345686 | 0x87D101AA | Syncml(426): Partial element not accepted. |
| -2016345687 | 0x87D101A9 | Syncml(425): The requested command failed because the sender does not have the appropriate access control permissions (ACLs) for the recipient. |
| -2016345688 | 0x87D101A8 | Syncml(424): The fragmented object was received, but the size of the received object did not match the size declared in the first fragment. |
| -2016345689 | 0x87D101A7 | Syncml(423): The requested command failed because the item 'soft deleted' was previously 'permanently deleted' on the server. |
| -2016345690 | 0x87D101A6 | Syncml(422): The requested command failed on the server because the CGI script was malformed in the LocURI. |
| -2016345691 | 0x87D101A5 | Syncml(421): The requested command failed on the server because the specified search grammar was not known. |
| -2016345692 | 0x87D101A4 | Syncml(420): The receiver has run out of space for the remaining sync data. |
| -2016345693 | 0x87D101A3 | Syncml(419): The client request caused a conflict which was resolved by winning the server command. |
| -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 point and the requestor must try the request again later. |
| -2016345696 | 0x87D101A0 | Syncml(416): The request failed because the byte size specified in the request was too large. |
| -2016345697 | 0x87D1019F | Syncml(415): Unsupported media type or format. |
| -2016345698 | 0x87D1019E | Syncml(414): The requested command failed because the destination URI is too long for what the recipient can or wants to process. |
| -2016345699 | 0x87D1019D | Syncml(413): The receiver refuses to execute the requested command because the requested item is larger than the receiver can or wants to process. |
| -2016345700 | 0x87D1019C | Syncml(412): The requested command failed at the receiver because it was incomplete or malformed. |
| -2016345701 | 0x87D1019B | Syncml(411): The requested command must be accompanied by information about the size or length of the byte in the meta element type. |
| -2016345702 | 0x87D1019A | Syncml(410): The requested destination is no longer in the receiver and no redirect URI is known. |
| -2016345703 | 0x87D10199 | Syncml(409): The request failed due to an update conflict between the client and server data versions. |
| -2016345704 | 0x87D10198 | Syncml(408): An expected message was not received within the required time. |
| -2016345705 | 0x87D10197 | Syncml(407): The requested command failed because the author needs to provide proper authentication. |
| -2016345706 | 0x87D10196 | Syncml(406): The requested command failed because an optional function 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 required. |
| -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 executed due to incorrect syntax in the command. |
| -2016345807 | 0x87D10131 | Syncml(305): The requested destination 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 under a different URI. |
| -2016345810 | 0x87D1012E | Syncml(302): The requested target has been 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 multiple requested alternate targets. |
| -2016345896 | 0x87D100D8 | Syncml(216): A command was inside the atomic element and atomic failed. This command was rolled back successfully. |
| -2016345897 | 0x87D100D7 | Syncml(215): A command was not executed due to user interaction and the user chose not to accept the choice. |
| -2016345898 | 0x87D100D6 | Syncml(214): Operation aborted. The SyncML command completed successfully, but no more commands are being processed within the session. |
| -2016345899 | 0x87D100D5 | Syncml(213): Fragmented element accepted and buffered |
| -2016345900 | 0x87D100D4 | Syncml(212): Authentication accepted. No further authentication is required for the rest of the synchronization session. This response code can only be used in response to a request where credentials have been provided. |
| -2016345901 | 0x87D100D3 | syncml(211): Element not removed. The requested item was not found. It may have been previously deleted. |
| -2016345902 | 0x87D100D2 | Syncml(210): Löschen ohne Archivierung. Die Antwort gibt an, dass die angeforderten Daten erfolgreich gelöscht, aber vor dem Löschen nicht archiviert wurden, da diese OPTIONALE Funktion von der Implementierung nicht unterstützt wurde. |
| -2016345903 | 0x87D100D1 | Resolved conflict with duplicate. The response indicates that the request caused an update conflict; This was addressed by duplicating client data created in the server's database. The response includes the target URI of the duplicate in the status element. Also in the case of two-way synchronization an Add command is returned with the definition of duplicate data. |
| -2016345904 | 0x87D100D0 | Fixed conflict with client win command. The response indicates that an update conflict has occurred; which was solved by winning the client command. |
| -2016345905 | 0x87D100CF | Conflict resolved by merging. The response indicates that the request caused a conflict; This was addressed by merging the client and server instances of the data. The response includes the source and destination URLs in the status element. Additionally, a Replace command is returned with the merged data. |
| -2016345906 | 0x87D100CE | The response indicates that only part of the command was executed. If the rest of the command can later be completed, another appropriate completion request status code should be generated upon completion. |
| -2016345907 | 0x87D100CD | The source MUST update its content. The requester is told that their content MUST be synchronized for a current version. |
| -2016345908 | 0x87D100CC | The request completed successfully, but no data is returned. The response code is also returned as a response to Get when the target has no content. |
| -2016345909 | 0x87D100CB | Unauthorized Response. The request is answered by an entity other than the target. The response should only be returned if the request would have resulted in a 200 response code from the authorized destination. |
| -2016345910 | 0x87D100CA | Accepted for processing. The request to remotely run an application or notify a user or application was successful. |
| -2016345911 | 0x87D100C9 | The requested item has been added. |
| -2016345912 | 0x87D100C8 | The SyncML command completed successfully. |
| -2016346011 | 0x87D10065 | The specified SyncML command is running but not yet complete. |
Next Steps
Contact Microsoft Support forGet support for Microsoft Endpoint Manager.
(Video) What's new in Microsoft Intune (2211 2212)