Consulting ServicesNeed help with your SCCM infrastructure ? Consult our fixed price consulting plans to see our rates or contact us for a custom quote. |
As an SCCM administrator, it’s important to learn the concept of troubleshooting a Configuration Manager client installation. By targeting the SCCM client installation error codes, you will have a better idea of what is happening during client installation. The error codes are not an exact science, they can defer depending on the situation. For a better understanding of ccmsetup error codes, read this great post from Jason Sandys.
Client installation troubleshooting is probably your first challenge after an SCCM Installation. A better SCCM client installation rate equals better overall management. You want your SCCM non-client count to be as low as possible.
These error codes appear in ccmsetup logs, located on the target machine – C:\windows\ccmsetup\logs. During the SCCM client installation process, monitor the ccmsetup.log using cmtrace.exe and locate each error code.
There are other logs, to which the SCCM client installation relates. If you don’t find enough information in the ccmsetup.log, scan all related log files in c:\windows\ccm\logs. Use the command line net helpmsg, for more information about your return error code.
SCCM Console
You can also add the Last Installation Error column in the SCCM console:
- Open the SCCM console and navigate to Assets and Compliance / Devices
- In the devices view, right-click on the header and select Last Installation Error
There are chances that the last error code returns an empty value for a device. Important to understand: an SCCM Client error code of “0” is a success.
SCCM Client Installation Error Codes
This post from Technet Forums (Thanks to Charlie Hawkins), has inspired us to prepare a list of all error codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.
Feel free to send us any new error codes, this list will be updated based on your comments.
| ID | Source | Description | Solution |
|---|---|---|---|
| 2 | The system cannot find the file specified This error occur when the WMI service is corrupt | Technet Resolution WMI Repair |
|
| 5 | Access denied | Make sure that the installation account is member of the Administrator Group | |
| 7 | Reboot Required | ||
| 8 | Setup Already Running | ||
| 9 | Prerequisite evaluation failure | ||
| 10 | Setup manifest hash validation failure | ||
| 52 | You were not connected because a duplicate name exists on the network | Check for duplicate name in DNS (IP) | |
| 52 | You were not connected because a duplicate name exists on the network | Check for duplicate name in DNS (IP) | |
| 53 | Unable to locate Cannot connect to admin$ Computer Browser not started | Add File & Print sharing to Exceptions in Firewall Turn file and print on KB920852 |
|
| 58 | The specified server cannot perform the requested operation | ||
| 64 | Windows | The specified network name is no longer available | |
| 67 | Network name cannot be found | Check if client has a DNS entry or invalid DNS | |
| 86 | Incorrect network configuration | ||
| 112 | Not enough disk space | Free some space on the computer | |
| 1003 | Cannot complete this function | ||
| 1053 | The service did not respond to the start or control request in a timely fashion | ||
| 1068 | The dependency service or group failed to start | ||
| 1130 | Windows | Not enough server storage is available to process this command | |
| 1203 | The network path was either typed incorrectly, does not exist, or the network provider is not currently available Please try retyping the path or contact your network administrator | ||
| 1208 | Windows | An extended error has occurred | |
| 1305 | The revision level is unknown | ||
| 1396 | Login Failure | The target account name is incorrect | Check for duplicate name in DNS (IP) NBTSTAT -a reverse lookup |
| 1450 | Windows | Insufficient system resources exist to complete the requested service | |
| 1603 | CCMExec could not be stopped | Reboot and install the client as administrator | |
| 1618 | MSI | This error is cause by a multiple client.msi installation at the same time | Stop all related MSI install process |
| 1789 | The trust relationship between this workstation and the primary domain failed | KB2771040 | |
| 12002 | Failed to send HTTP Request | Check firewall ports | |
| 8007045D | MSI | Setup was unable to create the WMI namespace CCM | Delete all SCCM folders and rebuilt wmi Repository |
| 800706BA | WMI | Unable to connect to WMI on remote machine | Prajwal Desai post |
| 80041001 | MSI | Setup was unable to create the WMI namespace CCM Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS | WMI Repair |
| 8004103B | WMI | Unable to create the WMI Namespace | Rebuild WMI Repository |
| 80070070 | Setup failed due to unexpected circumstances | Rebuild WMI Repository | |
| 87D0029E | WMI | CCMSetup Failed | Prajwal Desai post |
| 2147023174 | The RPC server is unavailable | Check out firewall or AntiVirus | |
| 2147024891 | Access is denied | ||
| 2147749889 | WMI | Generic failure | |
| 2147749890 | WMI | Not found | WMI Repair |
| 2147749904 | WMI | Invalid class | |
| 2147749908 | WMI | Initialization failure | |
| 2147942405 | Access is Denied | Missing Firewall rules MacAfee-HIPS |
|
| 2147944122 | The RPC server is unavailable | KB899965 Dcom is miss-configured for security |
|
| 2148007941 | Server Execution Failed | ||
| Technet Forums Sources |
Don’t forget to put emphasis on the prerequisites of the SCCM client, this will increase your success percentage during client installation. You can also check the list of client commands list, as additional help for troubleshooting your SCCM clients.
SCCM Client Installation Error CodesReporting
Knowing the client installation status from reports reduces the number of devices without SCCM client installed in your IT infrastructure. It also increases your effectiveness, when it’s time to tackle all unhealthy clients.
One of our custom SSRS reports is made especially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment state. This report will help you achieve the *near* 100% client installation, that your project manager loves to see.
33 Comments on “SCCM Client Installation Error Codes”
Pingback: SCCM error codes – systemcenterdiary
Really useful, thank you!
While installing updates we get the below error code
Failed to Add Update Source for WUAgent of type (2) and id ({E5538892-0326-43DA-939D-18EDBF3664C1}). Error = 0x87d00692.
Hi,
Thanks for this list; very useful! I have a question on your statement regarding the column in the console: “There are chances that the last error code returns an empty value for a device.”
This is the case for my environment: I have 40000 devices, some of which have client install failures, but for all devices the value in the column is blank. I believe I have traced this column in the console back to a view in the DB called v_CombinedDeviceResources and the column CP_LastInstallationError. In the DB, this field is NULL for all devices.
My question is what might cause this NULL value please? We do have devices with the client failing to install, so why would those devices not report this to the server/DB?
Many thanks!
J
Hi Team,
We received below error in wuagent log.
Failed to Add Update Source for WUAgent of type (2) and id ({6622B5DC-1C2D-4C47-A08C-5B6D8E18F38E}). Error = 0x80070583.
Got an exit code 3221549161, no idea what this one is unfortunately…zero results on google RIP
oops almost forgot, it may be worth noting that SCCM was having trouble activating Windows, caused by something I don’t have access to
CcmSetup failed with error code 0x87d00227
—> NetUseAdd failed: 53: dwParamError = 0
53 – When pushing SCCM client
In addition to adding File & Print sharing Exceptions in Firewall by turning File and Print on, check your DNS servers have the current or updated host records if you’re using DHCP to broadcast IPs to the CIs in your organization. Delete any stale records, reboot the CI, check you can UNC to \\hostname\Admin$ (C:\Windows) and push the client install.
—> NetUseAdd failed: 53: dwParamError = 0
53 – When pushing SCCM client
In addition to adding File & Print sharing Exceptions in Firewall by turning File and Print on, check your DNS servers have the current or updated host records if you’re using DHCP to broadcast IPs to the CIs in your organisation. Delete any stale records, reboot the CI, check you can UNC to \\hostname\Admin$ (C:\Windows) and push the client install.
Hi,
I was installing sccm client in MDM device which is in workgroup.while installing CcmSetup it failed with error code 0x87d00454
This is very helpful information ,
Thanks
hi community, in our report for a device we get the error code -939523070
who knows what it is. (we got unknown error for this) with error status id:11423?
Hello,
Can you please help with error code 0xC0000409(-1073740791)?
Very helpful! Not sure what exit code 193 means though. :/
WSUS service service failed to start, not valid II win32application local computer.
Hello There,
My Setup is failing with error code “CcmSetup failed with error code 0x80070009”
Please help me in solving this.
CcmSetup failed with error code 0x800700c1
Hi
Has anyone experienced error 2147749911 not on the list?
thanks
Hello,
I have a code 121 on Client Push !!!
Is there a complete list of those codes …
Thanks,
Dom
The documentation lists additional error codes:
https://docs.microsoft.com/en-us/sccm/core/clients/deploy/about-client-installation-properties#ccmsetupReturnCodes
Hello,
I have error 1385 which apparently is not on the list above… still checking the cause…
Thanks,
Dom
Windows Setup failed with hexadecimal exit code 0x80070241 (decimal 2147942977). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online.
I wonder where in the WMI Namespace this is recorded, I would like to make this a WQL-query based collection.
Thank you very nice,nice post. Very informative and useful, I made repost on my blog https://alexandrelizarov.wordpress.com/
Pingback: Troubleshooting Client instalation | Блог ИТ специалиста
Any chance of convincing you to do a similar writeup for the seemingly more vague error codes that come with SCCM OSD?
I have a lot of clients with Last Installation Error Code 120. This code isn’t mentioned in your list.
Can you help me with this code?
No update on this error ?!
Need some help with ErrorCode=”-2145386476 or error code 0x80200014.
<![LOG[]LOG]!>
This is incredibly useful. Thank you!
Thanks !
hi, my ccmsetup.exe is runing on server . but it should ccmec is should be running on server … and my client are cannot be pushed