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.
| Description | Error Code | Error Code (hex) |
|---|---|---|
| Name not found | -2147746304 | 0x80040200 |
| Service is shutting down | -2147746306 | 0x80040201 |
| No data supplied | -2147746307 | 0x80040203 |
| Data too large | -2147746308 | 0x80040204 |
| Invalid path | -2147746309 | 0x80040205 |
| Invalid file | -2147746310 | 0x80040206 |
| Parsing error | -2147746311 | 0x80040207 |
| Invalid command | -2147746312 | 0x80040208 |
| Data type mismatch | -2147746313 | 0x80040209 |
| Invalid Translator | -2147746320 | 0x80040210 |
| Invalid Address | -21477463-21 | 0x80040211 |
| Context is closed | -2147746322 | 0x80040212 |
| Timeout occurred | -2147746323 | 0x80040213 |
| Invalid name length | -2147746324 | 0x80040214 |
| Item not found | -2147746325 | 0x80040215 |
| Invalid service parameter. The WMI file could be corrupt or there was a manual change to a site control file. | -2147746326 | 0x80040216 |
| Data is corrupt | -2147746327 | 0x80040217 |
| Invalid service settings | -2147746328 | 0x80040218 |
| Global service not set | -2147746329 | 0x80040219 |
| Invalid type | -2147746336 | 0x80040220 |
| Invalid user. An operation for a user that is not logged on is in process or the user account is invalid. | -2147746337 | 0x80040221 |
| Message not trusted | -2147746355 | 0x80040221 |
| Operation cancelled | -2147746338 | 0x80040222 |
| Version mismatch | -2147746339 | 0x80040223 |
| Invalid message | -2147746340 | 0x80040224 |
| Invalid address type | -2147746341 | 0x80040226 |
| Invalid protocol | -2147746342 | 0x80040226 |
| Functionality disabled | -2147746343 | 0x80040227 |
| Invalid endpoint | -2147746344 | 0x80040228 |
| Failed to get credentials | -2147746345 | 0x80040229 |
| Error logging on as given credentials | -2147746352 | 0x80040230 |
| Transient error that could indicate a network problem. | -2147746353 | 0x80040231 |
| Message not signed | -2147746354 | 0x80040232 |
| Internal endpoint cannot receive a remote message | -2147746356 | 0x80040234 |
| Syntax error occurred while parsing | -2147746357 | 0x80040235 |
| Low memory. | -2147746358 | 0x80040236 |
| Reply mode incompatible | -2147746359 | 0x80040237 |
| Public key not found | -2147746360 | 0x80040238 |
| Client ID not found | -2147746361 | 0x80040239 |
| Insufficient disk space | -2147746368 | 0x80040240 |
| Failed to connect to database | -2147746369 | 0x80040241 |
| Stored procedure failed | -2147746370 | 0x80040242 |
| Public key mismatch | -2147746371 | 0x80040243 |
| Client communication from the management point failed. | -2147746430 | 0x8004027E |
| A valid certificate was not found in the certificate store. | -2147746432 | 0x80040280 |
| No valid certificate could be found using the specified certificate selection. | -2147746433 | 0x80040281 |
| More than one valid certificate was located | -2147746434 | 0x80040282 |
| The selected certificate does not have a corresponding private key, which is required for successful communication. | -2147746435 | 0x80040283 |
| The selected certificate does not have a Subject Name defined. | -2147746436 | 0x80040284 |
| The certificate selection criteria syntax is invalid. | -2147746436 | 0x80040285 |
| The certificate does not successfully chain to a trusted root certification authority. | -2147746437 | 0x80040286 |
| Cannot locate the required Configuration Manager site server signing certificate for this site. | -2147746438 | 0x80040287 |
| Client trying to refresh management point and it is empty. | -2147746560 | 0x80040300 |
| Client is configured to only read Active Directory Domain Services and couldn't find the requested location (site assignment, management point) data. | -2147746561 | 0x80040301 |
| 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. | -2147746562 | 0x80040303 |
| Internal error | -2147746563 | 0x80040303 |
| Management point certification is corrupt from client's perspective, which could be due to network corruption or an attacker. | -2147746564 | 0x80040304 |
| Client certification is corrupt from site system's perspective, which could be due to network corruption or an attacker. | -2147746565 | 0x80040305 |
| Client failed to connect to management point to make a location services request (MPLIST or MPKEYINFORMATION). | -2147746566 | 0x80040306 |
| 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. | -2147746567 | 0x80040307 |
| Client is trying to refresh local management point and it's empty. Only called from NAP when trying to refresh proxy management point. | -2147746568 | 0x80040308 |
| The 'trust failed'. This happens when the client doesn't trust data from the management point. | -2147746569 | 0x80040309 |
| 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 | -2147746569 | 0x80040309 |
These error codes can be found in the SCCM client log files. Log file references can be found here => https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/log-files