Consulting Services

Need 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.

SCCM Client Installation Error Codes

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\logsUse 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 ComplianceDevices
  • In the devices view, right-click on the header and select Last Installation Error
SCCM Client Installation Error Codes

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.

IDSourceDescriptionSolution
2The system cannot find the file specified
This error occur when the WMI service is corrupt
Technet Resolution
WMI Repair
5Access deniedMake sure that the installation account is member of the Administrator Group
7Reboot Required
8Setup Already Running
9Prerequisite evaluation failure
10Setup manifest hash validation failure
52You were not connected because a duplicate name exists on the networkCheck for duplicate name in DNS (IP)
52You were not connected because a duplicate name exists on the networkCheck for duplicate name in DNS (IP)
53Unable to locate
Cannot connect to admin$
Computer Browser not started
Add File & Print sharing to Exceptions in Firewall
Turn file and print on
KB920852
58The specified server cannot perform the requested operation
64WindowsThe specified network name is no longer available
67Network name cannot be foundCheck if client has a DNS entry or invalid DNS
86Incorrect network configuration
112Not enough disk spaceFree some space on the computer
1003Cannot complete this function
1053The service did not respond to the start or control request in a timely fashion
1068The dependency service or group failed to start
1130WindowsNot enough server storage is available to process this command
1203The 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
1208WindowsAn extended error has occurred
1305The revision level is unknown
1396Login FailureThe target account name is incorrectCheck for duplicate name in DNS (IP)
NBTSTAT -a reverse lookup
1450WindowsInsufficient system resources exist to complete the requested service
1603CCMExec could not be stoppedReboot and install the client as administrator
1618MSIThis error is cause by a multiple client.msi installation at the same timeStop all related MSI install process
1789The trust relationship between this workstation and the primary domain failed
KB2771040
12002Failed to send HTTP RequestCheck firewall ports
8007045DMSISetup was unable to create the WMI namespace CCMDelete all SCCM folders and rebuilt wmi Repository
800706BAWMIUnable to connect to WMI on remote machinePrajwal Desai post
80041001MSISetup was unable to create the WMI namespace CCM
Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS
WMI Repair
8004103BWMIUnable to create the WMI NamespaceRebuild WMI Repository
80070070Setup failed due to unexpected circumstancesRebuild WMI Repository
87D0029EWMICCMSetup FailedPrajwal Desai post
2147023174The RPC server is unavailableCheck out firewall or AntiVirus
2147024891Access is denied
2147749889WMIGeneric failure
2147749890WMINot foundWMI Repair
2147749904WMIInvalid class
2147749908WMIInitialization failure
2147942405Access is DeniedMissing Firewall rules
MacAfee-HIPS
2147944122The RPC server is unavailableKB899965
Dcom is miss-configured for security
2148007941Server 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.

Comments (34)

Dominique

07.27.2017 AT 03:38 PM
Hello, I have error 1385 which apparently is not on the list above... still checking the cause... Thanks, Dom

Matt

06.22.2017 AT 03:50 PM
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.

Christopher Moriarty

05.09.2016 AT 09:52 PM
I wonder where in the WMI Namespace this is recorded, I would like to make this a WQL-query based collection.

Alexandr

05.04.2016 AT 02:02 PM
Thank you very nice,nice post. Very informative and useful, I made repost on my blog https://alexandrelizarov.wordpress.com/

gabester

05.02.2016 AT 07:05 AM
Any chance of convincing you to do a similar writeup for the seemingly more vague error codes that come with SCCM OSD?

Philhamburgo

04.29.2016 AT 03:37 AM
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?

Ayman

07.02.2019 AT 05:08 AM
No update on this error ?!

Kevin Pestrue

04.27.2016 AT 09:27 AM
Need some help with ErrorCode="-2145386476 or error code 0x80200014. <![LOG[]LOG]!>

Zac

04.27.2016 AT 08:48 AM
This is incredibly useful. Thank you!

Benoit Lecours

04.28.2016 AT 06:34 AM
Thanks !

sohaib

12.09.2016 AT 09:49 AM
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