Ccmsetup failed with error code 0x87d0029e

Successfully downloaded client files via BITS. ccmsetup 10/23/2016 3:40:26 PM 4612 (0x1204)

Validated file ‘C:Windowsccmsetupvcredist_x86.exe’ hash ‘BBC26ACA42CD311A0E1EA1356852F061D863AF047F1891AC9952AB7E7CB8E04F’ ccmsetup 10/23/2016 3:40:26 PM 4612 (0x1204)

Validated file ‘C:Windowsccmsetupvcredist_x64.exe’ hash ‘E8F443960B2F4A588902C3ED1603B07E29366B35D6CD1F06BC2544345D270D72’ ccmsetup 10/23/2016 3:40:26 PM 4612 (0x1204)

Validated file ‘C:Windowsccmsetupvc50727_x64.exe’ hash ‘0551A61C85B718E1FA015B0C3E3F4C4EEA0637055536C00E7969286B4FA663E0’ ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Validated file ‘C:WindowsccmsetupMicrosoftPolicyPlatformSetup.msi’ hash ‘998052F221F508A9E5E3BF73C0AB3124E1F45EA469DB770190CAC79D9144387D’ ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Validated file ‘C:WindowsccmsetupWindowsFirewallConfigurationProvider.msi’ hash ‘3BF0651FD4A01170925CEF694468D4EF6F64D76FD3413DEBD14CB8DE019AA10E’ ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

File ‘C:WindowsccmsetupSilverlight.exe’ with hash ‘9C75C5154E91F044BD8646F25A2390E63C9E442BE6EA5E2672FBA92C637D505C’ from manifest doesn’t match with the file hash ‘BD7EC2CD5D5E31D39A183854C587681F49D1FC0DE47EF79AB0EA6D509DE64938’ ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Params to send ‘5.0.8412.1004 Deployment Silverlight.exe’ ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

A Fallback Status Point has not been specified and no client was installed. Message with STATEID=’325′ will not be sent. ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Failed to send status 325. Error (87D00215) ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Failed to connect to policy namespace. Error 0x8004100e ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

Deleted file C:Windowsccmsetupccmsetup.xml ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

CcmSetup failed with error code 0x87d0029e ccmsetup 10/23/2016 3:40:27 PM 4612 (0x1204)

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:windowsccmsetuplogs. 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:windowsccmlogs. 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.

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.

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.

Hi,
I have installed a new SCCM 2012 server into a site with an existing 2007 SCCM server.

After jumping through hoops managed to get Management Point working.

I am trying to manually install SCCM client on a windows 8.1 machine, but I now have issue in my ccmsetup

[/<![LOG[File 'C:Windowsccmsetupclient.msi' with hash 'A5732CE24F2B1545E9FBA458971E0A5504093E0F743CA9E8BD9C047582902878' from manifest doesn't match with the file hash 'D14D962286AF54C580F12D9B12DC4AD6ECE3E9873204AC82B11182C836D6066A']LOG]!><time="12:31:05.414-660" date="11-27-2014" component="ccmsetup" context="" type="2" thread="1368" file="util.cpp:2614">
<![LOG[A Fallback Status Point has not been specified.  Message with STATEID='325' will not be sent.]LOG]!><time="12:31:05.414-660" date="11-27-2014" component="ccmsetup" context="" type="1" thread="1368" file="ccmsetup.cpp:9763">
<![LOG[Deleted file C:Windowsccmsetupccmsetup.xml]LOG]!><time="12:31:05.414-660" date="11-27-2014" component="ccmsetup" context="" type="1" thread="1368" file="ccmsetup.cpp:9493">
<![LOG[CcmSetup failed with error code 0x87d0029e]LOG]!><time="12:31:05.414-660" date="11-27-2014" component="ccmsetup" context="" type="1" thread="1368" file="ccmsetup.cpp:10879">

Open in new window

Not sure why the hashes are different.

Any ideas?

in the CCMSETUP.LOG i get this…

Failed (0x87d0027e) to send location request to ‘PR1.na.corp.com’. StatusCode 403, StatusText ‘Forbidden’

Failed to get DP locations as the expected version from MP ‘PR1.na.corp.com’. Error 0x87d0027e

DownloadFileByWinHTTP failed with error 0x87d0027e

CcmSetup failed with error code 0x87d0027e

CCMSETUP bootstrap from Internet: 0 	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Current AD forest name is corp.com, domain name is na.corp.com	LocationServices	12/28/2018 7:17:14 AM	680 (0x02A8)
Domain joined client is in Intranet	LocationServices	12/28/2018 7:17:14 AM	680 (0x02A8)
Current AD site of machine is NA-USA-XX	LocationServices	12/28/2018 7:17:14 AM	680 (0x02A8)
DHCP entry points already initialized.	LocationServices	12/28/2018 7:17:14 AM	680 (0x02A8)
Begin checking Alternate Network Configuration	LocationServices	12/28/2018 7:17:14 AM	680 (0x02A8)
Finished checking Alternate Network Configuration	LocationServices	12/28/2018 7:17:14 AM	680 (0x02A8)
Sending message body '<ContentLocationRequest SchemaVersion="1.00"  BGRVersion="1">
<AssignedSite SiteCode="NA1"/>
<ClientPackage RequestForLatest="0" DeploymentFlags="4098"/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseAzure="1" DPTokenAuth="1" UseInternetDP="0">
<ADSite Name="NA-USA-XX"/>
<Forest Name="corp.com"/>
<Domain Name="na.corp.com"/>
<IPAddresses>
<IPAddress SubnetAddress="10.0.112.0" Address="10.0.112.100"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
'	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Sending location request to 'PR1.na.corp.com' with payload '<ContentLocationRequest SchemaVersion="1.00"  BGRVersion="1">
<AssignedSite SiteCode="NA1"/>
<ClientPackage RequestForLatest="0" DeploymentFlags="4098"/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseAzure="1" DPTokenAuth="1" UseInternetDP="0">
<ADSite Name="NA-USA-XX"/>
<Forest Name="corp.com"/>
<Domain Name="na.corp.com"/>
<IPAddresses>
<IPAddress SubnetAddress="10.0.112.0" Address="10.0.112.100"/>
</IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
'	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Client is not on internet	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Client is set to use webproxy if available.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
ccmsetup: Host=PR1.na.corp.com, Path=/ccm_system/request, Port=80, Protocol=http, CcmTokenAuth=0, Flags=0x14101, Options=0xe0	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Created connection on port 80	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Trying without proxy.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
[CCMHTTP] ERROR: URL=http://PR1.na.corp.com/ccm_system/request, Port=80, Options=224, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
[CCMHTTP] ERROR INFO: StatusCode=403 StatusText=Forbidden	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Raising event:
instance of CCM_CcmHttp_Status
{
ClientID = "GUID:C838FE5B-D6BB-45D9-A60F-17042A765771";
DateTime = "20181228121714.651000+000";
HostName = "PR1.na.corp.com";
HRESULT = "0x87d0027e";
ProcessID = 6864;
StatusCode = 403;
ThreadID = 680;
};
ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Failed to submit event to the Status Agent. Attempting to create pending event.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Raising pending event:
instance of CCM_CcmHttp_Status
{
ClientID = "GUID:C838FE5B-D6BB-45D9-A60F-17042A765771";
DateTime = "20181228121714.651000+000";
HostName = "PR1.na.corp.com";
HRESULT = "0x87d0027e";
ProcessID = 6864;
StatusCode = 403;
ThreadID = 680;
};
ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Successfully submitted pending event to WMI.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Failed (0x87d0027e) to send location request to 'PR1.na.corp.com'. StatusCode 403, StatusText 'Forbidden'	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Failed to send location message to 'PR1.na.corp.com'. Status text 'Forbidden'	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
GetDPLocations failed with error 0x87d0027e	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Failed to get DP locations as the expected version from MP 'PR1.na.corp.com'. Error 0x87d0027e	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Failed to find DP locations from MP 'PR1.na.corp.com' with error 0x87d0027e, status code 403. Check next MP.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Only one MP PR1.na.corp.com is specified. Use it.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Have already tried all MPs. Couldn't find DP locations.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Downloading 'HTTP://PR1.na.corp.com/CCM_Client/ccmsetup.cab' to 'C:windowsccmsetup\ccmsetup.cab'	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Client is not on internet	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Client is set to use webproxy if available.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
ccmsetup: Host=PR1.na.corp.com, Path=/CCM_Client/ccmsetup.cab, Port=80, Protocol=http, CcmTokenAuth=0, Flags=0x4101, Options=0xe0	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Created connection on port 80	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Trying without proxy.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
[CCMHTTP] ERROR: URL=HTTP://PR1.na.corp.com/CCM_Client/ccmsetup.cab, Port=80, Options=224, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
[CCMHTTP] ERROR INFO: StatusCode=403 StatusText=Forbidden	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Raising event:
instance of CCM_CcmHttp_Status
{
ClientID = "GUID:C838FE5B-D6BB-45D9-A60F-17042A765771";
DateTime = "20181228121714.728000+000";
HostName = "PR1.na.corp.com";
HRESULT = "0x87d0027e";
ProcessID = 6864;
StatusCode = 403;
ThreadID = 680;
};
ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Failed to submit event to the Status Agent. Attempting to create pending event.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Raising pending event:
instance of CCM_CcmHttp_Status
{
ClientID = "GUID:C838FE5B-D6BB-45D9-A60F-17042A765771";
DateTime = "20181228121714.728000+000";
HostName = "PR1.na.corp.com";
HRESULT = "0x87d0027e";
ProcessID = 6864;
StatusCode = 403;
ThreadID = 680;
};
ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Successfully submitted pending event to WMI.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
DownloadFileByWinHTTP failed with a non-recoverable failure, 0x87d0027e	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
DownloadFileByWinHTTP failed with error 0x87d0027e	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 2278556286	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
OS is not Win10RS3+, ENDOK.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
[5.00.8740.1004] Params to send '5.0.8740.1004 Deployment Error 0x87d0027e. Url HTTP://PR1.na.corp.com/CCM_Client/ccmsetup.cab'	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
<ClientDeploymentMessage ErrorCode="-2016411010"><Client Baseline="1" BaselineCookie="" Platform="2" Langs="LP1028LP1031LP1036LP1040LP1043LP1045LP1046LP1049LP2052LP2070LP3082"/><Packages><Package ID="{35830D25-C204-4A85-B428-B3519B15FAC2}"/><Package ID="{533A9EAF-0290-4736-B6D8-FFB9B33E0FB3}"/><Package ID="{596F6161-506D-48DC-B125-CA76B4E0E86C}"/><Package ID="{65C1167D-B9E5-4DE5-99A1-9F67AFB4FCD3}"/><Package ID="{85D95BE4-F3E2-4FCB-947D-938AB0899881}"/><Package ID="{89E379A6-3107-41BD-BD08-F78EBCBB905F}"/><Package ID="{92D0AB9A-BF19-4156-9B2F-3AF8DA5DD04F}"/><Package ID="{D8547A7F-3D93-4CCC-A30A-BF5EA32B7624}"/><Package ID="{D9532FBA-0FFE-4802-8287-D15A3B1CF7FF}"/><Package ID="{E49858F2-9320-424C-99D0-781973BA8F7B}"/><Package ID="{FAB888AB-2E9A-48C0-854D-04BCAE6C7F18}"/></Packages></ClientDeploymentMessage>	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Raised pending client deployment state message.	ccmsetup	12/28/2018 7:17:14 AM	680 (0x02A8)
Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 2278556286	ccmsetup	12/28/2018 7:17:14 AM	5312 (0x14C0)
OS is not Win10RS3+, ENDOK.	ccmsetup	12/28/2018 7:17:14 AM	5312 (0x14C0)
'Configuration Manager Client Retry Task' is scheduled to run at 12/28/2018 12:17:14 PM (local) 12/28/2018 05:17:14 PM (UTC) time with arguments '   "/mp:PR1.na.corp.com" RESETKEYINFORMATION="true" /RetryWinTask:4'.	ccmsetup	12/28/2018 7:17:14 AM	5312 (0x14C0)
Folder 'MicrosoftMicrosoftConfiguration Manager' not found. Task does not exist.	ccmsetup	12/28/2018 7:17:14 AM	5312 (0x14C0)
Successfully created task 'Configuration Manager Client Retry Task'	ccmsetup	12/28/2018 7:17:15 AM	5312 (0x14C0)
CcmSetup failed with error code 0x87d0027e	ccmsetup	12/28/2018 7:17:15 AM	5312 (0x14C0)

but if i look at the LocationServices.log and CcmMessaging.log i see ZERO issues….

any ideas?

Нашел я как то в локальной сети сервер, не управляемый SCCM. Не порядок, подумал я и запустил установку клиента SCCM на проблемный сервер с сервера управления. Установка потерпела крах. Процесс ccmsetup.exe запускался и тут же прекарщался. В логe ccmsetup.log первая ошибка была

Could not create WMI locator class (80040154)

Эта ужасная ошибка не давала покоя в течение дней, наверно, десяти, пока я не поборол её.

Вообще сама по себе она говорит, что есть проблемы с WMI, однако всяческие проверки показали, что WMI тут не причем. Оказывается код ошибки 0x80040154 говорит о том, что не зарегистрирован какой-то COM класс, но какой загадка. В поисках ответов нашел, что проблема скорее всего в том, что не работает функция CoCreateInstance или CoCreateInstanceEx, используемые для создания объектов. По этим функциям в поисковике раскопал несколько проблем, которые возникали у людей, в итоге пришёл к тому что необходимо в оснастке comexp.msc поглядеть на объекты COM. И наконец, я наткнулся на ошибку.

С такими показаниями решить проблему оказалось делом техники. Необходимо в свойствах объекта TcCtx. TransactionContext найти значение CLSID. Так как проблема возникала в COM+ Utilities (32 bit), то необходимо искать эти объекты в разделе реестра HKEY_CLASSES_ROOTWow6432NodeCLSID. Этих объектов там не было, поэтому я экспортировал ключи HKEY_CLASSES_ROOTWow6432NodeCLSID{5cb66670-d3d4-11cf-acab-00a024a55aef} и HKEY_CLASSES_ROOTWow6432NodeCLSID{7999FC25-D3C6-11CF-ACAB-00A024A55AEF} со здорового компьютера на этот проблемный. В результате первая ошибка в ccmsetup.log исчезла.

Однако, осталась ещё одна ошибка

Failed to get assigned site from AD. Error 0x87d00227

Такую ошибку решить не представляется никакой возможности, поэтому я перешёл к следующему этапу.

На этот раз я скопировал папку, из которой устанавливается клиент на проблемный сервер и запустил локально в итоге получил ошибки

CreateInstance of CLSID_BackgroundCopyManager failed with 80040154. Unable to check BITS version
This operating system does not contain the correct version of BITS. BITS 2.5 or later is required.

Я предпринял попытку восстановить BITS, однако, проблема оказалась не в этом. Пресловутая ошибка 0x80040154. В ходе посиков я раскопал, что объект BackgroundCopyManager входит в интерфейс IBackgroundCopyManager, CLSID которого {5CE34C0D-0DC9-4C1F-897C-DAA1B78CEE7C}, этого раздела не было в том же разделе реестра, в котором не было объекта TcCtx. TransactionContext. По отработаной схеме я экспортировал этот раздел со здоровой машины и импортировал на этот проблемный сервер.

В итоге, клиент SCCM благополучно установился.

PS

Добавлю, что в ходе последующих изысканий было выявлено, что не работают некоторые кнопки и ссылки в интерфейсе Windows и не запускается Internet Explorer 9 32-bit. Оказалось что надо перерегистрировать все dll в папке %windir%sysWOW64. Скорее всего, перерегистрация всех библиотек помогла бы и в решении пролемы с невозможностью установить клиента SCCM.