SCCM Error Codes – Descriptions and Quick Fixes
| Decimal Code | Hex Code | Description | Fix |
|---|---|---|---|
| 2 | 0x00000002 | The system cannot find the file specified [prajwaldesai.com], [byskov.com]. This typically indicates a required file or package is missing. | - Obtain a fresh copy of the missing installation files (e.g. re-download client setup files from the site server) [prajwaldesai.com]. - Ensure all required content is present in the expected locations before retrying installation. |
| 5 | 0x00000005 | Access is denied [prajwaldesai.com]. The installation process lacks the permissions needed to complete an action. | - Run the SCCM installer with administrative privileges on the client (ensure the SCCM service account has local admin rights) [prajwaldesai.com], [mynexttech.com]. - If pushing from the server, verify the client push account has admin access on the target machine. |
| 52 | 0x00000034 | A duplicate name exists on the network [prajwaldesai.com]. (The computer’s name conflicts with another on the network, often a DNS issue.) | - Remove or rename any duplicate hostnames in DNS that match the client’s name [prajwaldesai.com], [mynexttech.com]. - Ensure the computer’s name is unique in the domain before retrying deployment. |
| 53 | 0x00000035 | The network path was not found (failed to connect to admin$) [prajwaldesai.com]. This can happen if the admin share is inaccessible (e.g. firewall or service not running). | - Enable File and Printer Sharing through the Windows Firewall exceptions on the client [prajwaldesai.com]. - Verify the Server service (for admin$ share) is running and the device is reachable on the network. |
| 64 | 0x00000040 | The specified network name is no longer available [prajwaldesai.com]. (Network connection to the resource was lost during the operation.) | - Check network connectivity to the target resource (share or server) [prajwaldesai.com]. - Ensure the resource (e.g. a file share or DP) is still online and accessible, and that no network drop occurred. |
| 67 | 0x00000043 | The network name cannot be found [prajwaldesai.com]. (Name resolution failure or required services are not running on client.) | - Verify the client’s hostname can be resolved via DNS [prajwaldesai.com] (update DNS records if needed). - Ensure necessary services like Remote Registry and File/Printer Sharing are enabled on the client [prajwaldesai.com]. |
| 112 | 0x00000070 | Not enough disk space [prajwaldesai.com]. The target machine does not have sufficient free space for the operation. | - Free up disk space on the target machine (SCCM client needs ~100–500 MB for installation) [prajwaldesai.com]. - Clear temporary files or expand the disk volume before retrying the deployment. |
| 1053 | 0x0000041D | The service did not respond to the start or control request in a timely fashion [prajwaldesai.com]. (A Windows service needed by SCCM timed out starting.) | - Restart the service related to the SCCM client (e.g. ccmexec or ccmsetup) on the client machine [mynexttech.com]. - Check that all dependent services are running and increase the service timeout if persistent. |
| 1203 | 0x000004B3 | The network path was typed incorrectly or does not exist (network provider not available) [prajwaldesai.com]. In practice, this means the client couldn’t find the network location. | - Verify the network path in the deployment is correct and reachable by the client [prajwaldesai.com]. - Make sure the client’s network configuration (DNS, firewall) allows access to that path [mynexttech.com]. |
| 1396 | 0x00000574 | Logon Failure: The target account name is incorrect [prajwaldesai.com]. Often caused by a mismatch between machine account and AD (e.g. duplicate SPN or old computer object). | - Check Active Directory/DNS for a duplicate or stale computer account for the client; remove any duplicates [prajwaldesai.com]. - If the machine’s domain trust is broken, reset the computer account or rejoin it to the domain [mynexttech.com]. |
| 1603 | 0x00000643 | 1603 is a general Windows Installer fatal error (installation failed) [mynexttech.com]. In SCCM client setup logs, it often appears when the CCMExec service couldn’t be stopped [prajwaldesai.com]. | - Reboot the target machine, then retry the installation (this ensures no SCCM processes are stuck) [mynexttech.com]. - Check MSI logs (ccmsetup.log or client.msi.log) for specific errors, and address any MSI-related issue (e.g., remove previous client remnants) before reinstalling. |
| 1789 | 0x000006FD | The trust relationship between this workstation and the primary domain failed (machine account trust broken) [mynexttech.com]. | - Rejoin the computer to the domain to re-establish trust [mynexttech.com]. - Ensure the system’s clock is in sync with the domain and that the domain controller is reachable. |
| 12002 | 0x00002EE2 | The request timed out while accessing an HTTP resource (WININET error 12002) – for example, an HTTP upload or download timed out [mynexttech.com]. In SCCM, this might occur during content download via BITS. | - Check network connectivity for HTTP/HTTPS: ensure the client can reach the SCCM distribution point and that firewall ports (80/443) are open [mynexttech.com]. - If using a proxy or slow link, adjust BITS settings or retry when network conditions improve. |
| 2147942413 | 0x8007000D | A file needed by Windows Update is corrupted or missing [sccmgeekbl…dpress.com]. This error commonly causes Windows updates (or upgrade task sequences) to fail. | - Repair the Windows Update components: run System File Checker (SFC) and DISM to fix corrupted system files [learn.microsoft.com]. - Reset Windows Update (clear SoftwareDistribution cache) and then re-download the update [learn.microsoft.com]. |
| 2147500037 | 0x80004005 | Unspecified error (E_FAIL) – a generic failure with no specific message [learn.microsoft.com]. In SCCM logs, 0x80004005 appears when an operation fails without a detailed error (it can indicate anything from network issues to access denied, depending on context). | - General troubleshooting: check SCCM logs (e.g. SMSTS.log, AppEnforce.log) to find the underlying error message since 0x80004005 itself is generic [nextofwindows.com]. - Verify there are no obvious issues like firewall blocks, misconfigured client settings, or permission problems that could cause a generic failure [nextofwindows.com], [nextofwindows.com]. |
| 2147943517 | 0x8007045D | An I/O device error occurred (e.g. disk I/O failure). In SCCM context, this often shows up when the client’s WMI repository is inaccessible or can’t be written (WMI namespace creation failed) [mynexttech.com]. | - Rebuild the WMI repository on the client: remove or rename the existing repository (or the CCM namespace) and let it regenerate [mynexttech.com].- Check the disk health on the client (bad sectors or disk errors can cause 0x8007045D) and ensure the SYSTEM account can write to WMI. |
| 2147944122 | 0x800706BA | The RPC server is unavailable [prajwaldesai.com]. The client could not connect via RPC (for example, WMI calls to a remote machine failed). | - Make sure the Windows Firewall isn’t blocking RPC – open ports like TCP 135 and enable the “Remote Administration” exception [prajwaldesai.com]. - Verify the WMI service is running on the target and not corrupted (reinstall/repair WMI if RPC calls still fail) [mynexttech.com]. |
| 2147749947 | 0x8004103B | WMI generic failure: WMI namespace creation failed [prajwaldesai.com] (often due to insufficient resources on the client, e.g. low disk space for WMI). | - Free up disk space on the client (clear temp files, etc.) and reboot the machine [prajwaldesai.com]. - If WMI is broken, recompile the WMI repository. After freeing resources, retry the SCCM operation that failed. |
| 2278556181 | 0x87D00215 | Failed to get DP locations from the MP (no distribution point could be found) [techuisitive.com]. This often indicates the client is outside any boundary for content or the content is not distributed. | - Ensure the client’s network location is added to an SCCM Boundary and that it’s included in a Boundary Group with an associated Distribution Point [techuisitive.com]. - Distribute the content to the appropriate DP if not already done, then refresh policy on the client and retry. |
| 2278557191 | 0x87D00607 | The software distribution failed because content was not found by the client [learn.microsoft.com]. Common causes are misconfigured boundaries (client can’t find a source) or content removal. (In some cases, it can also indicate user permission issues or network errors.) | - Verify the application/package is distributed to the correct DP, and that the client’s boundary group is correctly configured for content location [learn.microsoft.com]. - Check that the client can communicate with the DP (no firewall blocking BITS/HTTP) [learn.microsoft.com], and review AppEnforce.log on the client for specific errors [learn.microsoft.com]. |
| 2278557284 | 0x87D00664 | Updates deployment was cancelled by SCCM because it exceeded its maximum runtime [sccmgeekbl…dpress.com]. (The update installer was stopped since it ran too long.) | - Re-deploy or run the update again on the client (the previous attempt was canceled) [sccmgeekbl…dpress.com]. - If the max run time is too low, adjust the Maximum Run Time setting for that update deployment in SCCM so it doesn’t timeout prematurely. |
| 2278556673 | 0x87D01201 | Not enough space in cache or disk for the application (Cache size too small) [sccmgeekbl…dpress.com]. The SCCM client’s cache or disk ran out of space during app install. | - Increase the SCCM client cache size in the Configuration Manager applet or deploy a policy to enlarge it, then retry the installation [sccmgeekbl…dpress.com]. - Free up disk space on the client if the entire disk is low on space. The deployment will resume once space is available. |
| 2278556318 | 0x87D0029E | CCMSetup failed – generic client install failure. This is a non-specific error indicating the client installation did not complete (often logged after other errors) [mynexttech.com]. | - Repair WMI on the client (WMI issues are a common cause for generic CCMSetup failures) and then run the client installation again [mynexttech.com]. - If not WMI, run CCMSetup with verbose logging and examine ccmsetup.log to find the preceding error (address that root cause). |
| 2278556199 | 0x87D00227 | Functionality disabled – client installation is blocked due to a metered network connection [prajwaldesai.com]. (By default, SCCM client won’t install over a metered link.) | - Re-run the client setup with the /AllowMetered switch to permit installation on a metered connection [prajwaldesai.com], [prajwaldesai.com].- Or, configure SCCM Client Settings to Allow client communication on metered networks and wait for the policy to apply, then retry the install [prajwaldesai.com]. |
