List of SCCM Client error messages


Listed below are the SCCM Client error messages. This list was originally posted into Microsoft TechNet by Klaus Bilger. Click here to view the TechNet article.

DescriptionError CodeError Code (hex)
Name not found-21477463040x80040200
Service is shutting down-21477463060x80040201
No data supplied-21477463070x80040203
Data too large-21477463080x80040204
Invalid path-21477463090x80040205
Invalid file-21477463100x80040206
Parsing error-21477463110x80040207
Invalid command-21477463120x80040208
Data type mismatch-21477463130x80040209
Invalid Translator-21477463200x80040210
Invalid Address-21477463-210x80040211
Context is closed-21477463220x80040212
Timeout occurred-21477463230x80040213
Invalid name length-21477463240x80040214
Item not found-21477463250x80040215
Invalid service parameter. The WMI file could be corrupt or there was a manual change to a site control file.-21477463260x80040216
Data is corrupt-21477463270x80040217
Invalid service settings-21477463280x80040218
Global service not set-21477463290x80040219
Invalid type-21477463360x80040220
Invalid user. An operation for a user that is not logged on is in process or the user account is invalid.-21477463370x80040221
Message not trusted-21477463550x80040221
Operation cancelled-21477463380x80040222
Version mismatch-21477463390x80040223
Invalid message-21477463400x80040224
Invalid address type-21477463410x80040226
Invalid protocol-21477463420x80040226
Functionality disabled-21477463430x80040227
Invalid endpoint-21477463440x80040228
Failed to get credentials-21477463450x80040229
Error logging on as given credentials-21477463520x80040230
Transient error that could indicate a network problem.-21477463530x80040231
Message not signed-21477463540x80040232
Internal endpoint cannot receive a remote message-21477463560x80040234
Syntax error occurred while parsing-21477463570x80040235
Low memory.-21477463580x80040236
Reply mode incompatible-21477463590x80040237
Public key not found-21477463600x80040238
Client ID not found-21477463610x80040239
Insufficient disk space-21477463680x80040240
Failed to connect to database-21477463690x80040241
Stored procedure failed-21477463700x80040242
Public key mismatch-21477463710x80040243
Client communication from the management point failed.-21477464300x8004027E
A valid certificate was not found in the certificate store.-21477464320x80040280
No valid certificate could be found using the specified certificate selection.-21477464330x80040281
More than one valid certificate was located-21477464340x80040282
The selected certificate does not have a corresponding private key, which is required for successful communication.-21477464350x80040283
The selected certificate does not have a Subject Name defined.-21477464360x80040284
The certificate selection criteria syntax is invalid.-21477464360x80040285
The certificate does not successfully chain to a trusted root certification authority.-21477464370x80040286
Cannot locate the required Configuration Manager site server signing certificate for this site.-21477464380x80040287
Client trying to refresh management point and it is empty.-21477465600x80040300
Client is configured to only read Active Directory Domain Services and couldn't find the requested location (site assignment, management point) data.-21477465610x80040301
Client is trying to do something that requires being assigned to a site and it is not assigned. Only called from NAP when trying to refresh the management point.-21477465620x80040303
Internal error-21477465630x80040303
Management point certification is corrupt from client's perspective, which could be due to network corruption or an attacker.-21477465640x80040304
Client certification is corrupt from site system's perspective, which could be due to network corruption or an attacker.-21477465650x80040305
Client failed to connect to management point to make a location services request (MPLIST or MPKEYINFORMATION).-21477465660x80040306
Client is trying to refresh proxy management point and it's empty. May only be called from NAP when trying to refresh the proxy management point.-21477465670x80040307
Client is trying to refresh local management point and it's empty. Only called from NAP when trying to refresh proxy management point.-21477465680x80040308
The 'trust failed'. This happens when the client doesn't trust data from the management point.-21477465690x80040309
In most cases this indicates that the in band server authorization failed on a client, usually because the trusted root key does not match the management point certificate-21477465690x80040309

Related Articles

SCCM task sequence UI – Set computer name and more during an SCCM task sequence deployment

It is always a unique challenge of having to build an OSD experience that includes providing a great user experience during the deployment of a new operating system.

The attached application would allow you to present a front-end to an active end-user who is executing the SCCM task sequence……

Keywords: SCCM tasksequence UI, SCCM Task Sequence User interface, SCCM task sequence Set computer name.


Are you an SCCM administrator?

SCCM Task Sequence deployment orchestrator.

built on best practices, learnings & insights of industry experts.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.