SCCM Troubleshooting Intune Error Codes Table | ConfigMgr

SCCM Troubleshooting error codes details would be beneficial for an Intune ConfigMgr Administrator. All credit to this error code goes to Nasiri El Marini !! SCCM Troubleshooting Intune Error Codes Table | ConfigMgr!

We all are familiar with the tool trace32.exe. However, it won’t work with CM 2012 properly log files. More details are below ConfigMgr SCCM Troubleshooting Intune Error Codes. You can check the following post to check the latest error codes – Translate SCCM Error Codes to Error Messages.

[New Updated PostSCCM Logs and Quick Tips to Read Logs]

Excellent  posts from ConfigMgr MVPs (Rob Marshall and Jörgen Nilsson).  These posts explain some of the advantageous features of CMTrace.exe like  Highlight, Filtering, Update Interval, and Refresh Interval and Merging. ConfigMgr SCCM Troubleshooting Intune Error Codes are helpful to understand real-world issues.

Patch My PC
SCCM Troubleshooting Intune Error Codes Table | ConfigMgr 1

Through the following blog post, we can find some hidden features of SCCM / SMS log reader tools called trace32.exe, cmtrace.exe.

ConfigMgrDog post explains about additional features available, like the error lookup (CTL + L) – The Error Lookup tool will return descriptions of cryptic error codes from and Merge selected files feature !!!

In the following blog post, Tao Yang explains about ConfigMgr 2012 log parser CMTRACE.EXE. Read his blog to know more about the experience which he had with trace32.exe for SCCM CB log files.

SCCM Troubleshooting – Error Codes for SCCM | Intune

You can try to have a search for error codes from the following table.

Adaptiva
Signed Integer Error CodeUnsigned Integer Error CodeHexadecimal Error Code Description/Meaning
000x00000000Success
-142949672950xFFFFFFFFScript execution failed with error code -1
10100x0000000AThe unit test error string
1310725121310725120x07D00200The client is successfully assigned with Group Policy Site Assignment
1310733141310733140x07D00522No more data
1310735891310735890x07D00635The scan was skipped because history was valid
-201627800222786892940x87D20A0EShutdown received while compressing
-201627800322786892930x87D20A0DUnexpected error while compressing
-201627800422786892920x87D20A0CAlready compressed
-201627800522786892910x87D20A0BFailed to create file header while compressing
-201627800622786892900x87D20A0AFailed to create file while compressing
-201627800722786892890x87D20A09Failed to create folder while compressing
-201627800822786892880x87D20A08Invalid compressed header in the file
-201627800922786892870x87D20A07Invalid compressed file
-201627801022786892860x87D20A06Failed to compress header
-201627801122786892850x87D20A05The file is no more there to compress
-201627801222786892840x87D20A04Invalid destination for compression
-201627801322786892830x87D20A03Invalid source for compression
-201627801422786892820x87D20A02Compression destination not found
-201627801522786892810x87D20A01Compression source not found
-201627826722786890290x87D20905SEDO lock request timed out
-201627826822786890280x87D20904SEDO lock not found
-201627826922786890270x87D20903Invalid object path for SEDO
-201627827022786890260x87D20902SEDO request ID not found
-201627827122786890250x87D20901SEDO needs lock ID or Rel path
-201627851822786887780x87D2080ACertificate not found
-201627851922786887770x87D20809Invalid data in the certificate
-201627852022786887760x87D20808Failed to find certificate
-201627852122786887750x87D20807Failed to decrypt the certificate
-201627852222786887740x87D20806Failed to delete certificate store
-201627852322786887730x87D20805Failed to write in the certificate store
-201627852422786887720x87D20804Failed to open the certificate store
-201627852522786887710x87D20803Error reading peer’s encoded certificate
-201627852622786887700x87D20802Error reading certificate
-201627852722786887690x87D20801Service Host Name property is either missing or invalid
-201627877622786885200x87D20708The specified item to update is not found in Site Control File
-201627877722786885190x87D20707Invalid FQDN found in Site Control File
-201627877822786885180x87D20706Legacy type item in Site Control File
-201627877922786885170x87D20705Site not found in Site Control File
-201627878022786885160x87D20704Bad data in Site Control File
-201627878122786885150x87D20703Item type not known in Site Control File
-201627878222786885140x87D20702Item not found in Site Control File
-201627878322786885130x87D20701Unknown property in Site Control File
-201627900622786882900x87D20622SRS data source has been modified or deleted
-201627900722786882890x87D20621SRS root folder is not present
-201627900822786882880x87D20620SRS is not installed or not properly configured
-201627901922786882770x87D20615SRS web service is not running
-201627927822786880180x87D20512The machine is not assigned to this site
-201627927922786880170x87D20511The machine is not an SMS client
-201627928022786880160x87D20510Machine not found foreign key constraint
-201627952922786877670x87D20417Auto Deployment Rule download failed
-201627953022786877660x87D20416No rule filters specified for the Auto Deployment Rule
-201627953122786877650x87D20415Auto Deployment Rule results exceeded the maximum number of updates
-201627953222786877640x87D20414Cannot Configure WU/MU as an upstream server on Peer Primary
-201627953322786877630x87D20413Active SUP not selected
-201627953722786877590x87D2040FWSUS Server component failure
-201627953822786877580x87D2040EWSUS Server Database connection failure
-201627953922786877570x87D2040DFailed to set Parent WSUS Configuration on the child sites
-201627954022786877560x87D2040CWSUS server not ready
-201627979722786874990x87D2030BDevice Setting Item not found Foreign Key Constraint
-201628005422786872420x87D2020ASDM Type not found Foreign Key Constraint
-201628005522786872410x87D20209Related SDM Package not found Foreign Key Constraint
-201628005622786872400x87D20208SDM Package was not found Foreign Key Constraint
-201628005722786872390x87D20207SDM Type not found Foreign Key Constraint
-201628005822786872380x87D20206EULA is not found Foreign Key Constraint
-201628005922786872370x87D20205Update Source was not found Foreign Key Constraint
-201628006022786872360x87D20204CI Type not found Foreign Key Constraint
-201628006122786872350x87D20203The category was not found Foreign Key Constraint
-201628006222786872340x87D20202Configuration Item not found Foreign Key Constraint
-201628006322786872330x87D20201Operation on Old Configuration Item when a newer instance exits in the Database
-201628031922786869770x87D20101Collection not found foreign key constraint
-201628052822786867680x87D20030Error while creating inbox
-201628054422786867520x87D20020Thread is signaled to be stopped
-201628055722786867390x87D20013Registry write error
-201628055822786867380x87D20012Registry read error
-201628055922786867370x87D20011Registry connection error
-201628056822786867280x87D20008SQL send batch error
-201628056922786867270x87D20007SQL queue row error
-201628057022786867260x87D20006SQL table binding error
-201628057122786867250x87D20005SQL deadlock error
-201628057222786867240x87D20004SQL error while registering type
-201628057322786867230x87D20003SQL Error
-201628057422786867220x87D20002SQL connection error
-201628057522786867210x87D20001Invalid data
-201628110722786861890x87D1FDEDUnsupported setting discovery source
-201628110822786861880x87D1FDECReferenced setting not found in CI
-201628110922786861870x87D1FDEBData type conversion failed
-201628111022786861860x87D1FDEAInvalid parameter to CIM setting
-201628111122786861850x87D1FDE9Not applicable for this device
-201628111222786861840x87D1FDE8Remediation failed
-201634110922786261870x87D1138BiOS device has returned an error
-201634111022786261860x87D1138AiOS device has rejected the command due to incorrect format
-201634111122786261850x87D11389iOS device has returned an unexpected Idle status
-201634111222786261840x87D11388iOS device is currently busy
-201634400822786232880x87D10838(1404): Certificate access denied
-201634400922786232870x87D10837(1403): Certificate not found
-201634401022786232860x87D10836DCMO(1402): The Operation failed
-201634401122786232850x87D10835DCMO(1401): User chose not to accept the operation when prompted
-201634401222786232840x87D10834DCMO(1400): Client error
-201634410822786231880x87D107D4DCMO(1204): Device Capability is disabled, and the User is allowed to re-enable it
-201634410922786231870x87D107D3DCMO(1203): Device Capability is disabled, and the User is not allowed to re-enable it
-201634411022786231860x87D107D2DCMO(1202): Enable operation is performed successfully, but the Device Capability is currently detached
-201634411122786231850x87D107D1DCMO(1201): Enable operation is performed successfully, and the Device Capability is currently attached
-201634411222786231840x87D107D0DCMO(1200): Operation is performed successfully
-201634419722786230990x87D1077BOperation not implemented on the client
-201634419822786230980x87D1077AThe package is an invalid upgrade
-201634419922786230970x87D10779The target location of the package is not accessible
-201634420022786230960x87D10778The installer is busy doing some other operation
-201634420122786230950x87D10777This indicates that network failure aborted the operation
-201634420222786230940x87D10776The package has no right to perform the operation
-201634420322786230930x87D10775Install/Uninstall Unknown error
-201634420422786230920x87D10774The mandatory file is in use and prevents the operation
-201634420522786230910x87D10773The package cannot be installed due to missing dependency
-201634420622786230900x87D10772The package cannot be installed due to a security error
-201634420722786230890x87D10771Package validation failed.
-201634420822786230880x87D10770Installation of the package is not supported
-201634420922786230870x87D1076FInsufficient free memory in the drive to perform the operation
-201634421022786230860x87D1076EFile is corrupted
-201634421122786230850x87D1076DUser canceled the operation
-201634421222786230840x87D1076CThe application was successfully installed
-201634451222786227840x87D10640An invalid OMA download descriptor received
-201634459322786227030x87D105EFA maximum number of HTTP redirections has been reached.
-201634459422786227020x87D105EENon-download specific error
-201634459522786227010x87D105EDInternal error occurred. Most probably a programming error.
-201634459622786227000x87D105ECAn error occurred in the transaction
-201634459722786226990x87D105EBGeneral storage error
-201634459822786226980x87D105EANot enough disk space for the content
-201634459922786226970x87D105E9Moving content file failed
-201634460022786226960x87D105E8Invalid download drive
-201634460122786226950x87D105E7File not found an error
-201634460222786226940x87D105E6File write failed
-201634460322786226930x87D105E5Media where the download is being persisted removed
-201634460422786226920x87D105E4Download Manager cannot handle this URL
-201634460522786226910x87D105E3Error in the destination filename
-201634460622786226900x87D105E2Destination file cannot be opened/created
-201634460722786226890x87D105E1Unhandled HTTP error code
-201634460822786226880x87D105E0404: object not found
-201634460922786226870x87D105DF412: partial content cannot be downloaded
-201634461022786226860x87D105DEPaused content is expired
-201634461122786226850x87D105DDResuming progressive download failed
-201634471122786225850x87D10579Connection failed. No network coverage
-201634471322786225830x87D10577Unknown error related to protocol
-201634481022786224860x87D10516The requested operation is invalid for this protocol
-201634481122786224850x87D10515The requested protocol is not known
-201634481322786224830x87D10513Unknown error related to remote content
-201634490722786223890x87D104B5Content needed to resent, but this failed
-201634490822786223880x87D104B4Remote server required authentication but credentials supplied if any were not accepted
-201634490922786223870x87D104B3Remote content was not found at the server
-201634491022786223860x87D104B2The operation requested on remote content is not permitted
-201634491122786223850x87D104B1Access to remote content denied
-201634491322786223830x87D104AFUnknown proxy related error
-201634500722786222890x87D10451Proxy authentication required or proxy refused the supplied credentials if any
-201634500822786222880x87D10450Connection to the proxy timed out
-201634500922786222870x87D1044FInvalid proxy hostname
-201634501022786222860x87D1044EThe proxy server closed the connection prematurely
-201634501122786222850x87D1044DConnection to the proxy server was refused
-201634506122786222350x87D1041BDetection rules not present
-201634506322786222330x87D10419Unknown network error
-201634510322786221930x87D103F1Remote server unavailable
-201634510422786221920x87D103F0Network authentication failed
-201634510522786221910x87D103EFTemporary network failure
-201634510622786221900x87D103EEThe encrypted channel could not be established
-201634510722786221890x87D103EDThe operation was canceled before it was finished
-201634510822786221880x87D103ECConnection to the remote server timed out
-201634510922786221870x87D103EBInvalid hostname
-201634511022786221860x87D103EAThe remote server closed the connection prematurely
-201634511122786221850x87D103E9The remote server refused the connection
-201634511222786221840x87D103E8Error Unknown
-201634559522786217010x87D10205SyncML: The response to an atomic command was too large to fit in a single message.
-201634559622786217000x87D10204SyncML: Command was inside Atomic element, and Atomic failed. This command was not rolled back successfully.
-201634559822786216980x87D10202SyncML: The SyncML command was not completed successfully since the operation was already canceled before processing the command.
-201634559922786216970x87D10201SyncML: The recipient does not support or refuses to support the specified version of the SyncML Synchronization Protocol used in the request SyncML Message.
-201634560022786216960x87D10200SyncML: An application error occurred during the synchronization session.
-201634560122786216950x87D101FFSyncML: A severe error occurred in the server while processing the request.
-201634560222786216940x87D101FESyncML: An error occurred while processing the request. The error is related to a failure in the recipient data store.
-201634560322786216930x87D101FDSyncML: Reserved for future use.
-201634560422786216920x87D101FCSyncML: An error that necessitates a refresh of the current synchronization state of the client with the server.
-201634560522786216910x87D101FBSyncML: The error caused all SyncML commands within an Atomic element type to fail.
-201634560622786216900x87D101FASyncML: An application error occurred while processing the request.
-201634560722786216890x87D101F9SyncML: The recipient does not support or refuses to support the specified version of SyncML DTD used in the request SyncML Message.
-201634560822786216880x87D101F8SyncML: 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.
-201634560922786216870x87D101F7SyncML: The recipient is currently unable to handle the request due to a temporary overloading or maintenance.
-201634561022786216860x87D101F6SyncML: The recipient, while acting as a gateway or proxy, received an invalid response from the upstream recipient it accessed to fulfill the request.
-201634561122786216850x87D101F5SyncML: The recipient does not support the command required to fulfill the request.
-201634561222786216840x87D101F4SyncML: The recipient encountered an unexpected condition that prevented it from fulfilling the request
-201634568422786216120x87D101ACSyncML: Move failed
-201634568522786216110x87D101ABSyncML: Parent cannot be deleted since it contains children.
-201634568622786216100x87D101AASyncML: Partial item not accepted.
-201634568722786216090x87D101A9SyncML: The requested command failed because the sender does not have adequate access control permissions (ACL) on the recipient.
-201634568822786216080x87D101A8SyncML: The chunked object was received, but the size of the received object did not match the size declared within the first chunk.
-201634568922786216070x87D101A7SyncML: The requested command failed because the “Soft Deleted” item was previously “Hard Deleted” on the server.
-201634569022786216060x87D101A6SyncML: The requested command failed on the server because the CGI scripting in the LocURI was incorrectly formed.
-201634569122786216050x87D101A5SyncML: The requested command failed on the server because the specified search grammar was not known.
-201634569222786216040x87D101A4SyncML: The recipient has no more storage space for the remaining synchronization data.
-201634569322786216030x87D101A3SyncML: The client request created a conflict which was resolved by the server command winning.
-201634569422786216020x87D101A2SyncML: The requested Put or Add command failed because the target already exists.
-201634569522786216010x87D101A1SyncML: The request failed at this time, and the originator should retry the request later.
-201634569622786216000x87D101A0SyncML: The request failed because the specified byte size in the request was too big.
-201634569722786215990x87D1019FSyncML: Unsupported media type or format.
-201634569822786215980x87D1019ESyncML: The requested command failed because the target URI is too long for what the recipient is able or willing to process.
-201634569922786215970x87D1019DSyncML: The recipient refuses to perform the requested command because the requested item is larger than the recipient is able or willing to process.
-201634570022786215960x87D1019CSyncML: The requested command failed on the recipient because it was incomplete or incorrectly formed.
-201634570122786215950x87D1019BSyncML: The requested command must be accompanied by byte size or length information in the Meta element type.
-201634570222786215940x87D1019ASyncML: The requested target is no longer on the recipient, and no forwarding URI is known.
-201634570322786215930x87D10199SyncML: The requested failed because of an update conflict between the client and server versions of the data.
-201634570422786215920x87D10198SyncML: An expected message was not received within the required period of time.
-201634570522786215910x87D10197SyncML: The requested command failed because the originator must provide proper authentication.
-201634570622786215900x87D10196SyncML: The requested command failed because an optional feature in the request was not supported.
-201634570722786215890x87D10195SyncML: The requested command is not allowed on the target.
-201634570822786215880x87D10194SyncML: The requested target was not found.
-201634570922786215870x87D10193SyncML: The requested command failed, but the recipient understood the requested command.
-201634571022786215860x87D10192SyncML: The requested command failed because proper payment is needed.
-201634571122786215850x87D10191SyncML: The requested command failed because the requestor must provide proper authentication.
-201634571222786215840x87D10190SyncML: The requested command could not be performed because of malformed syntax in the command.
-201634580722786214890x87D10131SyncML: The requested target must be accessed through the specified proxy URI.
-201634580822786214880x87D10130SyncML: The requested SyncML command was not executed on the target.
-201634580922786214870x87D1012FSyncML: The requested target can be found at another URI.
-201634581022786214860x87D1012ESyncML: The requested target has temporarily moved to a different URI.
-201634581122786214850x87D1012DSyncML: The requested target has a new URI.
-201634581222786214840x87D1012CSyncML: The requested target is one of several multiple alternatives requested target.
-201634601122786212850x87D10065SyncML: The specified SyncML command is being carried out but has not yet been completed.
-201640345222785638440x87D02004The software distribution policy was not found.
-201640345422785638420x87D02002The software distribution policy for this program was not found.
-201640689422785604020x87D01292The virtual application is in use
-201640689522785604010x87D01291The virtual environment is not applicable
-201640689622785604000x87D01290An error occurred when querying the App-V WMI provider
-201640689722785603990x87D0128FThe App-V time command returned failure
-201640689822785603980x87D0128EI could not uninstall the App-V deployment type because of conflict. The published components in this DT are still published by other DTs. This DT will always be detected as long as other DTs are still installed.
-201640690022785603960x87D0128CI could not find a streaming distribution point for the App-V package
-201640690122785603950x87D0128BThe App-V application is not installed
-201640690222785603940x87D0128AThe App-V client has reported a launch error
-201640690622785603900x87D01286The App-V package has already installed a higher version by another deployment type, so we cannot install a lower version of the package
-201640690722785603890x87D01285A dependent App-V package is not installed
-201640691122785603850x87D01281A supported App-V client is not installed
-201640691222785603840x87D01280The virtual application is currently in use
-201640695922785603370x87D01251The application deployment type handler could not be initialized. The deployment type might not be supported on this system.
-201640696022785603360x87D01250The computer restart cannot be initiated because a software installation job is in progress.
-201640702422785602720x87D01210Failed to get content locations.
-201640703622785602600x87D01204No distribution points were found for the requested content.
-201640703722785602590x87D01203The client cache is currently in use by a running program or by a download in progress.
-201640703822785602580x87D01202The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content.
-201640703922785602570x87D01201The content download cannot be performed because there is not enough available space in the cache or the disk is full.
-201640704022785602560x87D01200No content request was found with the given handle.
-201640728622785600100x87D0110AA fatal error occurred while preparing to execute the program, for example, when creating the program execution environment making a network connection impersonating the user determining the file association information or when attempting to launch the program. This program execution will not be retried.
-201640728722785600090x87D01109Failed to verify that the given file is a valid installation package.
-201640728822785600080x87D01108Failed to access all the provided program locations. This program will not retry.
-201640728922785600070x87D01107Failed to access all the provided program locations. This program may retry if the maximum retry count has not been reached.
-201640729022785600060x87D01106Failed to verify the executable file is valid or to construct the associated command line.
-201640729122785600050x87D01105An error was encountered while getting the process information for the launched program, and the program execution will not be monitored.
-201640729222785600040x87D01104The command line for this program is invalid.
-201640729322785600030x87D01103A nonfatal error occurred while preparing to execute the program, for example, when creating the program execution environment making a network connection impersonating the user determining the file association information or when attempting to launch the program. This program execution will be retried if the retry count has not been exceeded.
-201640729422785600020x87D01102An error occurred while creating the execution context.
-201640729522785600010x87D01101A fatal error has been encountered while attempting to run the program. The program execution will not be retried.
-201640729622785600000x87D01100A non-fatal error has been encountered while attempting to run the program. The program execution will be retried if the retry count has not been exceeded.
-201640752822785597680x87D01018The program cannot run at this time because the client is on the internet.
-201640752922785597670x87D01017The content hash string or hash version is empty or incorrect in the software distribution policy, or the hash verification failed.
-201640753122785597650x87D01015Failed to notify the caller that software distribution is paused because the paused state or paused cookie does not match.
-201640753222785597640x87D01014The program cannot run because it is targeted to a user that requires user input or is set to run in the user context.
-201640753322785597630x87D01013This program cannot run because it depends on another program that has not run successfully before.
-201640753422785597620x87D01012There is no program currently running.
-201640753522785597610x87D01011The execution request was not found.
-201640753622785597600x87D01010A system restart is in progress, or there is a pending execution for this program that requires a computer restart.
-201640754322785597530x87D01009Failed to get data from WMI.
-201640754422785597520x87D01008Failed to indicate the client cache is currently in use.
-201640754622785597500x87D01006The requested program is not currently pending.
-201640754722785597490x87D01005The policy for this program does not exist or is invalid.
-201640754822785597480x87D01004The program is disabled.
-201640755022785597460x87D01002Another execution for this program is already pending.
-201640755122785597450x87D01001Another software execution is in progress, or a restart is pending.
-201640958822785577080x87D0080CNo WDS session is available.
-201640958922785577070x87D0080BMCS Encountered WDS error.
-201640959022785577060x87D0080AInvalid MCS configuration.
-201640959122785577050x87D00809The package is not multicast enabled.
-201640959222785577040x87D00808The package is not multicast shared.
-201640959322785577030x87D00807The invalid path is specified for Package.
-201640959422785577020x87D00806MCS Server is Busy with many clients.
-201640959522785577010x87D00805MCS Encryption is empty
-201640959622785577000x87D00804Error performing MCS health check
-201640959722785576990x87D00803Error opening MCS session
-201640959822785576980x87D00802MCS protocol version mismatch
-201640959922785576970x87D00801General MCS Failure
-201640960022785576960x87D00800The content transfer manager job is in an unexpected state
-201640983522785574610x87D00715No updates specified in the requested job
-201640983622785574600x87D00714User-based install not allowed as system restart is pending
-201640983722785574590x87D00713Software updates detection results have not been received yet
-201640983822785574580x87D00712A system restart is required to complete the installation
-201640983922785574570x87D00711Software updates deployment not active yet, i.e., start time is in future
-201640984022785574560x87D00710Failed to compare process creation time
-201640984122785574550x87D0070FInvalid updates installer path
-201640984222785574540x87D0070EThe empty command line specified
-201640984322785574530x87D0070DThe software update failed when attempted
-201640984422785574520x87D0070CSoftware update execution timeout
-201640984522785574510x87D0070BFailed to create a process
-201640984622785574500x87D0070AInvalid command line
-201640984722785574490x87D00709Failed to resume the monitoring of the process
-201640984822785574480x87D00708Software Updates Install not required
-201640984922785574470x87D00707Job Id mismatch
-201640985022785574460x87D00706No active job exists
-201640985122785574450x87D00705Pause state required
-201640985222785574440x87D00704A hard reboot is pending
-201640985322785574430x87D00703Another software updates install job is in progress. Only one job is allowed at a time.
-201640985422785574420x87D00702Assignment policy not found
-201640985522785574410x87D00701Software updates download not allowed at this time
-201640985622785574400x87D00700Software updates installation not allowed at this time
-201640995922785573370x87D00699The scan is already in progress
-201640996022785573360x87D00698Software update being attempted is not actionable
-201640996122785573350x87D00697The software update is already installed but just requires a reboot to complete the installation
-201640996222785573340x87D00696The software update is already installed
-201640996322785573330x87D00695Incomplete scan results
-201640996422785573320x87D00694WSUS source already exists
-201640996522785573310x87D00693Windows Updates Agent version too low
-201640996622785573300x87D00692Group policy conflict
-201640996722785573290x87D00691Software update source not found
-201640996822785573280x87D00690The software update is not applicable
-201640999922785572970x87D00671Waiting for a third-party orchestration engine to initiate the installation
-201641000622785572900x87D0066ANone of the child software updates of a bundle are applicable
-201641000722785572890x87D00669Not able to get software updates content locations at this time
-201641000822785572880x87D00668Software update still detected as actionable after apply
-201641000922785572870x87D00667No current or future service window exists to install software updates
-201641001022785572860x87D00666Software updates cannot be installed outside the service window
-201641001122785572850x87D00665No updates to process in the job
-201641001222785572840x87D00664Updates handler job was canceled
-201641001322785572830x87D00663Failed to report installation status of software updates
-201641001422785572820x87D00662Failed to trigger the installation of software updates
-201641001522785572810x87D00661Error while detecting updates status after installation success
-201641001622785572800x87D00660Unable to monitor a software update’s execution
-201641002322785572730x87D00659An error occurred reading policy for software update
-201641002422785572720x87D00658Software updates processing was canceled
-201641002522785572710x87D00657Error while detecting software updates status after scan success
-201641002622785572700x87D00656Updates handler was unable to continue due to some generic internal error
-201641002722785572690x87D00655Failed to install one or more software updates
-201641002822785572680x87D00654Software update install failure occurred
-201641002922785572670x87D00653Software update download failure occurred
-201641003022785572660x87D00652Software update policy was not found
-201641003122785572650x87D00651Post-install scan failed
-201641003222785572640x87D00650Pre-install scan failed
-201641006022785572360x87D00634Legacy scanner not supported
-201641006122785572350x87D00633The offline scan is pending
-201641006222785572340x87D00632The online scan is pending
-201641006322785572330x87D00631Scan retry is pending
-201641006422785572320x87D00630Maximum retries exhausted
-201641007122785572250x87D00629Rescan of the updates is pending
-201641007222785572240x87D00628Invalid content location
-201641007322785572230x87D00627Process instance not found
-201641007422785572220x87D00626Invalid process instance information
-201641010422785571920x87D00608Invalid instance type
-201641010522785571910x87D00607Content not found
-201641010622785571900x87D00606Offline scan tool history not found
-201641010722785571890x87D00605The scan tool has been removed
-201641010822785571880x87D00604The ScanTool not found in the job queue
-201641010922785571870x87D00603The ScanTool Policy has been removed, so cannot complete scan operation
-201641011022785571860x87D00602Content location request timeout occurred
-201641011122785571850x87D00601Scanning for updates timed out
-201641011222785571840x87D00600Scan Tool Policy not found
-201641055822785567380x87D00442An enforcement action (install/uninstall) was attempted for a simulated deployment.
-201641055922785567370x87D00441The deployment metadata is not available on the client.
-201641056022785567360x87D00440Expected policy documents are incomplete or missing.
-201641059222785567040x87D00420The detection rules refer to an unsupported WMI namespace.
-201641062122785566750x87D00403The detection rules contain an unsupported datatype.
-201641062222785566740x87D00402The detection rules contain an invalid operator.
-201641062322785566730x87D00401An incorrect XML expression was found when evaluating the detection rules.
-201641062422785566720x87D00400An unexpected error occurred when evaluating the detection rules.
-201641083222785564640x87D00330This application deployment type does not support being enforced with a required deployment
-201641083822785564580x87D0032AThe uninstall command line is invalid
-201641083922785564570x87D00329Application requirement evaluation or detection failed
-201641084022785564560x87D00328Configuration item digest not found
-201641084122785564550x87D00327The script is not signed
-201641084222785564540x87D00326The application deployment metadata was not found in WMI
-201641084322785564530x87D00325The application was still detected after uninstalling was completed.
-201641084422785564520x87D00324The application was not detected after the installation was completed.
-201641084522785564510x87D00323No user is logged on.
-201641084622785564500x87D00322Rule conflict.
-201641084722785564490x87D00321The script execution has timed out.
-201641084822785564480x87D00320The script host has not been installed yet.
-201641084922785564470x87D0031FScript for discovery returned invalid data.
-201641085022785564460x87D0031EUnsupported configuration. The application is configured to Install for User but has been targeted to a mechanical device instead of the user.
-201641085122785564450x87D0031DUnsupported configuration. The application is targeted to a user but is configured to install when no user is logged in.
-201641085822785564380x87D00316CI Agent job was canceled.
-201641085922785564370x87D00315The CI version info data is not available.
-201641086022785564360x87D00314CI Version Info timed out.
-201641098322785563130x87D00299The client does not recognize this type of signature
-201641098422785563120x87D00298The client’s database record could not be validated
-201641098522785563110x87D00297Invalid key
-201641098622785563100x87D00296The client failed to process one or more CI documents
-201641098722785563090x87D00295Registration certificate is either missing or invalid
-201641098822785563080x87D00294Unable to verify Policy
-201641098922785563070x87D00293Client unable to Refresh Site server signing certificate
-201641099022785563060x87D00292Client unable to compute message signature for InBand Auth
-201641099122785563050x87D00291No task sequence policies assigned
-201641099222785563040x87D00290The job contains no items
-201641099922785562970x87D00289Failed to decompress CI documents
-201641100022785562960x87D00288Failed to decompress configuration item
-201641100122785562950x87D00287The signing certificate is missing
-201641100222785562940x87D00286Invalid SMS authority
-201641100322785562930x87D00285Search criteria verb is either missing or invalid
-201641100422785562920x87D00284Missing subject name
-201641100522785562910x87D00283Missing private key
-201641100622785562900x87D00282More than one certificate was found, but ‘select first cert’ was not set
-201641100722785562890x87D00281No certificate matching criteria specified
-201641100822785562880x87D00280Empty certificate store
-201641100922785562870x87D0027FSHA could not bind as NAP Agent might not be running
-201641101022785562860x87D0027EBad HTTP status code
-201641101122785562850x87D0027DCI documents download failed due to hash mismatch
-201641101222785562840x87D0027CCI documents download timed out
-201641101322785562830x87D0027BGeneral CI documents download failure
-201641101422785562820x87D0027AConfiguration item download failed due to hash mismatch
-201641101522785562810x87D00279Configuration item download timed out
-201641101622785562800x87D00278General configuration item download failure
-201641101722785562790x87D00277Insufficient resources to complete the operation
-201641101822785562780x87D00276A system restart is required
-201641101922785562770x87D00275Failed to acquire the lock
-201641102022785562760x87D00274No callback completion interface specified
-201641102122785562750x87D00273The component has already been requested to pause
-201641102222785562740x87D00272Component is disabled
-201641102322785562730x87D00271Component is paused
-201641102422785562720x87D00270The component is not paused
-201641102522785562710x87D0026FPause cookie did not match
-201641102622785562700x87D0026EPause duration too big
-201641102722785562690x87D0026DPause duration too small
-201641102822785562680x87D0026CStatus not found
-201641102922785562670x87D0026BAgent type not found
-201641103022785562660x87D0026AKey type not found
-201641103122785562650x87D00269Required management point not found
-201641103222785562640x87D00268Compilation failed
-201641103322785562630x87D00267Download failed
-201641103422785562620x87D00266Inconsistent data
-201641103522785562610x87D00265Invalid store state
-201641103622785562600x87D00264Invalid operation
-201641103722785562590x87D00263Invalid message received from DTS
-201641103822785562580x87D00262The type of DTS message received is unknown
-201641103922785562570x87D00261Failed to persist configuration item definition
-201641104022785562560x87D00260Job state is not valid for the action being requested
-201641104122785562550x87D0025FClient disconnected
-201641104222785562540x87D0025EEncountered a message which was not sufficiently trusted to forward to an endpoint for processing
-201641104322785562530x87D0025DEncountered invalid XML document which could not be validated by its corresponding XML schema(s)
-201641106022785562360x87D0024CEncountered invalid XML schema document
-201641106122785562350x87D0024BName already exists
-201641106222785562340x87D0024AThe job is already connected
-201641106322785562330x87D00249Property is not valid for the given configuration item type
-201641106422785562320x87D00248There was an error in network communication
-201641106522785562310x87D00247A component required to perform the operation was missing or not registered
-201641106622785562300x87D00246There was an error evaluating the health of the client
-201641106722785562290x87D00245The objector subsystem has already been initialized
-201641106822785562280x87D00244The object or subsystem has not been initialized
-201641106922785562270x87D00243Public key mismatch
-201641107022785562260x87D00242Stored procedure failed
-201641107122785562250x87D00241Failed to connect to database
-201641107222785562240x87D00240Insufficient disk space
-201641107922785562170x87D00239Client id not found
-201641108022785562160x87D00238Public key not found
-201641108122785562150x87D00237Reply mode incompatible
-201641108222785562140x87D00236Low memory
-201641108322785562130x87D00235Syntax error occurred while parsing
-201641108422785562120x87D00234An internal endpoint cannot receive a remote message
-201641108522785562110x87D00233Message not trusted
-201641108622785562100x87D00232Message not signed
-201641108722785562090x87D00231Transient error
-201641108822785562080x87D00230Error logging on as given credentials
-201641109522785562010x87D00229Failed to get credentials
-201641109622785562000x87D00228Invalid endpoint
-201641109722785561990x87D00227Functionality disabled
-201641109822785561980x87D00226Invalid protocol
-201641109922785561970x87D00225Invalid address type
-201641110022785561960x87D00224Invalid message
-201641110122785561950x87D00223Version mismatch
-201641110222785561940x87D00222Operation canceled
-201641110322785561930x87D00221Invalid user
-201641110422785561920x87D00220Invalid type
-201641111122785561850x87D00219Global service not set
-201641111222785561840x87D00218Invalid service settings
-201641111322785561830x87D00217Data is corrupt
-201641111422785561820x87D00216Invalid service parameter
-201641111522785561810x87D00215Item not found
-201641111622785561800x87D00214Invalid name length
-201641111722785561790x87D00213Timeout occurred
-201641111822785561780x87D00212Context is closed
-201641111922785561770x87D00211Invalid Address
-201641112022785561760x87D00210Invalid Translator
-201641112722785561690x87D00209Data type mismatch
-201641112822785561680x87D00208Invalid command
-201641112922785561670x87D00207Parsing error
-201641113022785561660x87D00206Invalid file
-201641113122785561650x87D00205Invalid path
-201641113222785561640x87D00204Data too large
-201641113322785561630x87D00203No data supplied
-201641113422785561620x87D00202Service is shutting down
-201641113522785561610x87D00201Incorrect name format
-201641113622785561600x87D00200Name not found
-214505881721499084790x8024FFFFThere was a reporter error not covered by another error code.
-214506290721499043890x8024F005The specified callback cookie is not found.
-214506290821499043880x8024F004The server rejected an event because the server was too busy.
-214506290921499043870x8024F003The XML in the event namespace descriptor could not be parsed.
-214506291021499043860x8024F002The XML in the event namespace descriptor could not be parsed.
-214506291121499043850x8024F001The event cache file was defective.
-214506291321499043830x8024EFFFThere was an expression evaluator error not covered by another WU_E_EE_* error code.
-214506700121499002950x8024E007An expression evaluator operation could not be completed because the cluster state of the computer could not be determined.
-214506700221499002940x8024E006An expression evaluator operation could not be completed because there was an invalid attribute.
-214506700321499002930x8024E005The expression evaluator could not be initialized.
-214506700421499002920x8024E004An expression evaluator operation could not be completed because the version of the serialized expression data is invalid.
-214506700521499002910x8024E003An expression evaluator operation could not be completed because an expression contains an incorrect number of metadata nodes.
-214506700621499002900x8024E002An expression evaluator operation could not be completed because an expression was invalid.
-214506700721499002890x8024E001An expression evaluator operation could not be completed because an expression was unrecognized.
-214506700921499002870x8024DFFFWindows Update Agent could not be updated because of an error not covered by another WU_E_SETUP_* error code.
-214507108221498962140x8024D016Windows Update Agent could not be updated because of an unknown error.
-214507108321498962130x8024D015Windows Update Agent is successfully updated, but a reboot is required to complete the setup.
-214507108421498962120x8024D014Windows Update Agent is successfully updated, but a reboot is required to complete the setup.
-214507108521498962110x8024D013Windows Update Agent could not be updated because the server does not contain updated information for this version.
-214507108621498962100x8024D012Windows Update Agent must be updated before a search can continue. An administrator is required to perform the operation.
-214507108721498962090x8024D011Windows Update Agent must be updated before a search can continue.
-214507108821498962080x8024D010Windows Update Agent could not be updated because the registry contains invalid information.
-214507108921498962070x8024D00FWindows Update Agent could not be updated because the setup handler failed during execution.
-214507109021498962060x8024D00EWindows Update Agent setup package requires a reboot to complete installation.
-214507109121498962050x8024D00DWindows Update Agent setup is already running.
-214507109221498962040x8024D00CWindows Update Agent could not be updated because a restart of the system is required.
-214507109321498962030x8024D00BWindows Update Agent could not be updated because the system is configured to block the update.
-214507109421498962020x8024D00AWindows Update Agent could not be updated because the current system configuration is not supported.
-214507109521498962010x8024D009An update to the Windows Update Agent was skipped due to a directive in the wuident.cab file.
-214507109621498962000x8024D008An update to the Windows Update Agent was skipped because previous attempts to update have failed.
-214507109721498961990x8024D007Windows Update Agent could not be updated because regsvr32.exe returned an error.
-214507109821498961980x8024D006Windows Update Agent could not be updated because a WUA file on the target system is newer than the corresponding source file.
-214507109921498961970x8024D005Windows Update Agent could not be updated because the versions specified in the INF do not match the actual source file versions.
-214507110021498961960x8024D004Windows Update Agent could not be updated because setup initialization was never completed successfully.
-214507110121498961950x8024D003Windows Update Agent could not be updated because of an internal error that caused set up initialization to be performed twice.
-214507110221498961940x8024D002Windows Update Agent could not be updated because the wuident.cab file contains invalid information.
-214507110321498961930x8024D001Windows Update Agent could not be updated because an INF file contains invalid information.
-214507110521498961910x8024CFFFA driver error not covered by another WU_E_DRV_* code.
-214507519321498921030x8024C007Information required for the synchronization of applicable printers is missing.
-214507519421498921020x8024C006Driver synchronization failed.
-214507519521498921010x8024C005The driver update is missing a required attribute.
-214507519621498921000x8024C004The driver update is missing metadata.
-214507519721498920990x8024C003The registry type read for the driver does not match the expected type.
-214507519821498920980x8024C002A property for the driver could not be found. It may not conform to the required specifications.
-214507519921498920970x8024C001A driver was skipped.
-214507929121498880050x8024B005Cannot cancel a non-scheduled install.
-214507929221498880040x8024B004The task was stopped and needs to be rerun to complete.
-214507929321498880030x8024B003The operation cannot be completed since the task is not yet started.
-214507929421498880020x8024B002The operation cannot be completed since the task status is currently disabled.
-214507929521498880010x8024B001The task is currently in progress.
-214507929721498879990x8024AFFFAn Automatic Updates error is not covered by another WU_E_AU * code.
-214508338621498839100x8024A006The default service registered with AU changed during the search.
-214508338721498839090x8024A005No unmanaged service is registered with AU.
-214508338821498839080x8024A004Automatic Updates was unable to process incoming requests because it was paused.
-214508338921498839070x8024A003The old version of the Automatic Updates client was disabled.
-214508339021498839060x8024A002The old version of the Automatic Updates client has stopped because the WSUS server has been upgraded.
-214508339221498839040x8024A000Automatic Updates was unable to service incoming requests.
-214508748321498798130x80249005A WMI error occurred when enumerating the instances for a particular class.
-214508748421498798120x80249004There was an inventory error not covered by another error code.
-214508748521498798110x80249003Failed to upload inventory results to the server.
-214508748621498798100x80249002Failed to get the requested inventory type from the server.
-214508748721498798090x80249001Parsing of the rule file failed.
-214508748921498798070x80248FFFA data store error is not covered by another WU_E_DS_* code.
-214509155521498757410x8024801DA data store operation did not complete because it was requested with an impersonated identity.
-214509155621498757400x8024801CThe data store requires a session reset; release the session and retry with a new session.
-214509155721498757390x8024801BThe schema of the current data store and the schema of a table in a backup XML document do not match.
-214509155821498757380x8024801AA request was declined because the operation is not allowed.
-214509155921498757370x80248019A request to remove the Windows Update service or to unregister it with Automatic Updates was declined because it is a built-in service, and/or Automatic Updates cannot fall back to another service.
-214509156021498757360x80248018A table was not closed because it is not associated with the session.
-214509156121498757350x80248017A table was not closed because it is not associated with the session.
-214509156221498757340x80248016A request to hide an update was declined because it is a mandatory update or because it was deployed with a deadline.
-214509156321498757330x80248015An operation did not complete because the registration of the service has expired.
-214509156421498757320x80248014An operation did not complete because the service is not in the data store.
-214509156521498757310x80248013The server sent the same update to the client with two different revision IDs.
-214509156721498757290x80248011I could not create a datastore object in another process.
-214509156821498757280x80248010The datastore is not allowed to be registered with COM in the current process.
-214509156921498757270x8024800FThe data store could not be initialized because it was locked by another process.
-214509157021498757260x8024800EThe row was not added because an existing row has the same primary key.
-214509157121498757250x8024800DThe category was not added because it contains no parent categories and is not a top-level category itself.
-214509157221498757240x8024800CThe data store section could not be locked within the allotted time.
-214509157321498757230x8024800BThe update was not deleted because it is still referenced by one or more services.
-214509157421498757220x8024800AThe update was not processed because its update handler could not be recognized.
-214509157521498757210x80248009The datastore is missing required information or references missing license terms file localized property or linked row.
-214509157621498757200x80248008The datastore is missing required information or has a NULL in a table column that requires a non-null value.
-214509157721498757190x80248007The information requested is not in the data store.
-214509157821498757180x80248006The current and expected versions of the datastore do not match.
-214509157921498757170x80248005A table could not be opened because the table is not in the data store.
-214509158021498757160x80248004The data store contains a table with unexpected columns.
-214509158121498757150x80248003The datastore is missing a table.
-214509158221498757140x80248002The current and expected states of the datastore do not match.
-214509158321498757130x80248001An operation failed because the datastore was in use.
-214509158421498757120x80248000An operation failed because Windows Update Agent is shutting down.
-214509158521498757110x80247FFFSearch using the scan package failed.
-214509567521498716210x80247005The service is not registered.
-214509567621498716200x80247004The size of the event payload submitted is invalid.
-214509567721498716190x80247003An invalid event payload was specified.
-214509567821498716180x80247002An operation could not be completed because the scan package requires a greater version of the Windows Update Agent.
-214509567921498716170x80247001An operation could not be completed because the scan package was invalid.
-214509568121498716150x80246FFFThere was a download manager error not covered by another WU_E_DM_* error code.
-214509976421498675320x8024600CA download failed because the current network limits downloads by update size for the update service.
-214509976521498675310x8024600BA download must be restarted because the updated content changed in a new revision.
-214509976621498675300x8024600AA download must be restarted because the location of the source of the download has changed.
-214509976721498675290x80246009A download manager operation failed because of an unspecified Background Intelligent Transfer Service (BITS) transfer error.
-214509976821498675280x80246008A download manager operation failed because the download manager could not connect the Background Intelligent Transfer Service (BITS).
-214509976921498675270x80246007The update has not been downloaded.
-214509977021498675260x80246006A download manager operation could not be completed because the version of Background Intelligent Transfer Service (BITS) is incompatible.
-214509977121498675250x80246005A download manager operation could not be completed because the network connection was unavailable.
-214509977221498675240x80246004An operation could not be completed because a download request is required from the download handler.
-214509977321498675230x80246003A download manager operation could not be completed because the file metadata requested an unrecognized hash algorithm.

Extract from his blog post – Original Post

Unlike trace32.exe, cmtrace.exe is actually built-in in SCCM; there is no need to download separate toolkits for it. Cm trace.32 can be found on the SCCM site server, under the “<SCCM Install Dir>\tools\” folder. Same as its predecessor trace32.exe, cmtrace.exe can be copied/redistributed to other locations/computers alone and used as a log parser.

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

5 thoughts on “SCCM Troubleshooting Intune Error Codes Table | ConfigMgr”

  1. -2016411129,2278556167,0x87D00207,Parsing error – for this error if you have a combo of 80041013 and 80041001 in CIDownloader.log, an uninstall of the CMClient (we did it with ccmclean.exe /q) and a reinstall should solve it. We think it is because of blocked policies due to the 80041013 – Provider Load failure. Never heard anything from Microsoft about this, just “You need to look in the CI*.logs” where we found the hint on what to do. Cheers

    Reply
  2. -2016411129,2278556167,0x87D00207,Parsing error – for this error if you have a combo of 80041013 and 80041001 in CIDownloader.log, an uninstall of the CMClient (we did it with ccmclean.exe /q) and a reinstall should solve it. We think it is because of blocked policies due to the 80041013 – Provider Load failure. Never heard anything from Microsoft about this, just “You need to look in the CI*.logs” where we found the hint on what to do. Cheers

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.