locked
Error while installing SCCM Client RRS feed

  • Question

  • Hello Fellas,

    I was trying to installing SCCM Client. I was using a script for deploying client, and work properly

    Then I use same script for other devices (different Subnet from first machine). ccmsetup service is running after I ran the script, but after some minutes, the service stopped improperly.

    I have one log only (at C:\windows\ccmsetup\Logs\ccmsetup.log)

    The log shown yellow line highlighted.

    File 'C:\Windows\ccmsetup\Silverlight.exe' with hash 'XXX' from manifest doesn't match with the file hash 'YYY'

    I was search this message. They said it was something happened in DP.

    Should I re-install DP role for this issue?

    If yes, can I rollback (in case re-install DP failed)? because it ran at production environment.

    Thursday, July 14, 2016 11:03 AM

Answers

  • It has been already addressed by Janson,

    Pretty clear now from the log file exactly what failed:

    File 'C:\Windows\ccmsetup\vc50727_x64.exe' with hash '0551A61C85B718E1FA015B0C3E3F4C4EEA0637055536C00E7969286B4FA663E0' from manifest doesn't match with the file hash '301300E768BB0401BE340E05DDFEE67989959B807D9DAC5140D4AFA57794BFA6'

    This could happen for a lot of reasons so there's no way to know why though. You should examine your client directory on your site server and grab the file off of another site. I think this file comes from site setup download process so you could redownload those files and grab just the one specified. You could also try updating the DPs.

    @CraigMatthews Now you see exactly why we needed more info.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Please try to update the configMgr client package using update distribution point and try to run again.


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    • Marked as answer by Aljazair Tuesday, July 19, 2016 11:04 AM
    Thursday, July 14, 2016 11:23 AM

All replies

  • This is the full log http://pastebin.com/t8Ei70yF
    Thursday, July 14, 2016 11:12 AM
  • It has been already addressed by Janson,

    Pretty clear now from the log file exactly what failed:

    File 'C:\Windows\ccmsetup\vc50727_x64.exe' with hash '0551A61C85B718E1FA015B0C3E3F4C4EEA0637055536C00E7969286B4FA663E0' from manifest doesn't match with the file hash '301300E768BB0401BE340E05DDFEE67989959B807D9DAC5140D4AFA57794BFA6'

    This could happen for a lot of reasons so there's no way to know why though. You should examine your client directory on your site server and grab the file off of another site. I think this file comes from site setup download process so you could redownload those files and grab just the one specified. You could also try updating the DPs.

    @CraigMatthews Now you see exactly why we needed more info.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Please try to update the configMgr client package using update distribution point and try to run again.


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    • Marked as answer by Aljazair Tuesday, July 19, 2016 11:04 AM
    Thursday, July 14, 2016 11:23 AM
  • Hello,

    No you don't need to reinstall the DP again, It's clear, you would have to install the correct version of vc50727_x64.exe which seems corrupted. 


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Thursday, July 14, 2016 2:47 PM
  • + Sharad sing email,

    its has all executable hash mismatch


    Kannan.CS | http://kannancs.wix.com/blog | Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

    Thursday, July 14, 2016 2:56 PM
  • Thanks All, the issue is my installer sources (silverlight.exe) was corrupted. So I just re-copy sources from SCCM Server (C:\Program Files\Microsoft Configuration Manager\Client) and re-install the agent.
    Tuesday, July 19, 2016 11:07 AM