CcmSetup failed with error code 0x80080005

This post covers about the error CcmSetup failed with error code 0x80080005. In a remote site while re-installing SCCM client agent, the IT guy told me that client agent installation is failing. He reviewed the smsts.log file and found that CcmSetup failed with error code 0x80080005.

He then uninstalled the SCCM client agent and restarted the computer. When he pushed the client agent to the computer back, he noticed the same error.

CcmSetup failed with error code 0x80080005In such cases, until you review the complete smsts.log file, you cannot troubleshoot this issue further. Finally I got hold of smsts.log file and I saw multiple errors logged in smsts.log file. If you go through the log file, I am sure you will identify the cause of this error.

Updated security on object C:\WINDOWS\ccmsetup
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup
Params to send '5.0.8239.1502 Deployment Error: ' ccmsetup
Downloading file C:\Users\Prajwal\Downloads\Windows\ccmsetup.exe
Download complete
CreateInstance of CLSID_BackgroundCopyManager failed with 80080005. Unable to check BITS version ccmsetup
This operating system does not contain the correct version of BITS. BITS 2.5 or later is required
Failed to get client version for sending state messages. Error 0x8004100e
Params to send '5.0.8239.1502 Deployment This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.'
Deleted file C:\WINDOWS\ccmsetup\ccmsetup.exe.download
CcmSetup failed with error code 0x80080005

CcmSetup failed with error code 0x80080005

It’s very rare that you see ccmsetup error code 0x80080005 during the SCCM client agent installation. However the error 0x80080005 is a known error and let us see the reason behind this error.

This problem occurs because Microsoft Background Intelligent Transfer Service (BITS) version 2.5 or a later version must be installed before you can install the SCCM client.

As per Microsoft, BITS version 2.5 is required to enable throttled data transfers between the client computer and Configuration Manager site systems.

During client installation, BITS isn’t downloaded automatically. Most operating systems include BITS. However, if your operating system does not include BITS, you must install BITS before you install the client agent.

In this case, I checked the client computer and it already had BITS installed but the service wasn’t running. I am not sure if the Background Intelligent Transfer Service was intentionally stopped by user. When the BITS service was started, the client agent installation worked fine. The same solution also works when you see ccmsetup failed with error code 0x80200014.

Prajwal Desai

Hi, I am Prajwal Desai. For last few years I have been working on multiple technologies such as SCCM / Configuration Manager, Intune, Azure, Security etc. I created this site so that I can share valuable information with everyone.
Photo of author

2 thoughts on “CcmSetup failed with error code 0x80080005”

  1. Dear Prajwal Desai,

    Please find the below logs when installing the client , for the security concern i have removed the SCCM Server name into dashes(—-)

    Client
    IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to connect to machine policy namespace. 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to get client certificate for transportation. Error 0x87d00280 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed (0x87d00454) to send location request to ‘—–‘. StatusCode 200, StatusText ” ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to send location message to ‘HTTPS://—–‘. Status text ” ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    GetDPLocations failed with error 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to get DP locations as the expected version from MP ‘HTTPS://——‘. Error 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to find DP locations from MP ‘HTTPS://——‘ with error 0x87d00454, status code 200. Check next MP. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Have already tried all MPs. Couldn’t find DP locations. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to connect to machine policy namespace. 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    IsSslClientAuthEnabled – Determining provisioning mode state failed with 80070002. Defaulting to state of 63. ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to get client certificate for transportation. Error 0x87d00280 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    DownloadFileByWinHTTP failed with a non-recoverable failure, 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    DownloadFileByWinHTTP failed with error 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to send status 308. Error (87D00215) ccmsetup 4/19/2021 7:43:29 AM 8840 (0x2288)
    Failed to connect to policy namespace. Error 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 6272 (0x1880)
    Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 4/19/2021 7:43:29 AM 6272 (0x1880)
    CcmSetup failed with error code 0x87d00454 ccmsetup 4/19/2021 7:43:29 AM 6272 (0x1880)

    Server
    Unable to connect to remote machine “—–” using Kerberos with alternate account, error – 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:53:57 AM 30564 (0x7764)
    Unable to connect to WMI on remote machine “——“, error = 0x80041033. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764)
    Unable to connect to remote machine “MAHMED” using Kerberos with machine account, error – 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764)
    Unable to connect to WMI on remote machine “MAHMED”, error = 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152117, -2147023174 SMS_CLIENT_CONFIG_MANAGER 4/18/2021 9:55:04 AM 30564 (0x7764)

    Please note:
    Server & Client – firewall is Turn Off complete all ports are opened
    WMI & BITS is installed and working fine in Client & Server – restarted the services
    Reintall the ISS roles

    Reply

Leave a Comment