none
Pull DP issues after Upgrade from SCCM 2012 to 1710

    Question

  • Hello All,

    After upgrading from SCCM 2012 to SCCM-1710, one of our Pull DP's has issues. Packages do not replicate anymore and SCCM client is in an infinite loop of self repair. I recall during the upgrade (2 weeks ago), this Pull DP was offline for some reason.

    smsdpprov.log logs the following error :

    RegQueryValueExW failed for Software\Microsoft\SMS\DP, Site Code
    RegReadString failed; 0x80070002

    Upon checking HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP, it lists only 3 items viz.ContentLibraryPath, ContentLibUsableDrives, UsablePackageShareDrives. (compared to other healthy Pull DP's, which have over 50)

    Since this is a remote Pull DP with low bandwidth, it would be perfect if there is method available without having to re-replicate over 100 GB of data.

    SCCM Version : 1710 + KB4057517

    OS Version of Pull DP : 2012-R2

    Kindly advise. Thanks


    • Edited by sccm72 Monday, February 19, 2018 2:51 AM
    Sunday, February 18, 2018 5:57 PM

Answers

  • > "since its mandatory for pulldp"

    This is not correct.

    Have you promoted the latest client version to production?

    What happens if you remove the client agent completely as suggested?


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by sccm72 Thursday, February 22, 2018 6:28 AM
    Monday, February 19, 2018 9:26 PM

All replies

  • Migration or upgrade? Your title says one thing and your text says another -- they are two very different things.

    Have you tried simply uninstalling the client agent?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, February 19, 2018 1:28 AM
  • Its an upgrade - have edited it. Sorry for that.

    Regards the SCCM Client :

    Yes, I've tried 'ccmsetup /uninstall' and then installing again. It installs fine but then loops forever in self repair.Next cleaned all known elements of the SCCM client after  'ccmsetup /uninstall' using https://blogs.technet.microsoft.com/michaelgriswold/2013/01/02/manual-removal-of-the-sccm-client/ but same issue of infinite self-repair. The installation though is somewhat successful as I can see the client installed in the console and reporting its inventory fine.

    Monday, February 19, 2018 3:05 AM
  • It seems the client self-repair loop has stopped after a restart.

    But the smsdpprov.log errors continue.

    Monday, February 19, 2018 6:51 AM
  • What else is in smsdpprov.log? Just that error message?

    Also, why reinstall the client at all initially?

    Did you review distmgr.log to validate that the DP itself was upgraded during the upgrade or if there are other messages related to it?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, February 19, 2018 3:07 PM
  • Hello Jason, Thanks for helping out.

    Here is the outline of of events :

    Before the upgrade, the PullDP was healthy.

    During the upgrade it was offline.

    A week after the upgrade I could see packages replicating fine to it.
    A few days after that package replication began to fail.

    We observed the SCCM Client was missing on the console.

    When trying to install the client on the Pull DP, (since its mandatory for pulldp), we observed it was fine a about 30 minutes or so, then would initiate a repair:
    ccmrepair.log:
    Could not get registration for product "ConfigMgr Distribution Point". Repair required. WMI returned (80041002)    CcmRepair
    Initiating repair


    Meanwhile, in smsdpprov.log, the following messages repeated every 40 minutes.

    [11DC][Sat 02/17/2018 23:45:09]:Installing/upgrading PullDP
    [11DC][Sat 02/17/2018 23:45:09]:Started process D:\SMS_DP$\sms\bin\vcredist_x64.exe /q /norestart /l D:\SMS_DP$\sms\logs\vcredist.log
    [11DC][Sat 02/17/2018 23:45:09]:Waiting for the completion of: D:\SMS_DP$\sms\bin\vcredist_x64.exe /q /norestart /l D:\SMS_DP$\sms\logs\vcredist.log
    [11DC][Sat 02/17/2018 23:45:10]:Run completed for: D:\SMS_DP$\sms\bin\vcredist_x64.exe /q /norestart /l D:\SMS_DP$\sms\logs\vcredist.log
    [11DC][Sat 02/17/2018 23:45:10]:File (D:\SMS_DP$\sms\bin\ccmsetup.exe) is not trusted
    [11DC][Sat 02/17/2018 23:45:10]:InstallPullDP() failed. error = 80004005 Unspecified error
    [11DC][Sat 02/17/2018 23:45:10]:RegQueryValueExW failed for Software\Microsoft\SMS\DP, Site Code
    [11DC][Sat 02/17/2018 23:45:10]:RegReadString failed; 0x80070002
    [11DC][Sat 02/17/2018 23:45:10]:Failed to validate IIS and ShareFolder configurations. Return code: 0x80070002



    Observed that D:\SMS_DP$\sms\bin\ccmsetup.exe did not exist.
    Copied from another healthy Pull DP
    Errors changed to the following


    [2344][Sun 02/18/2018 16:50:48]:Installing/upgrading PullDP
    [2344][Sun 02/18/2018 16:50:48]:Started process D:\SMS_DP$\sms\bin\vcredist_x64.exe /q /norestart /l D:\SMS_DP$\sms\logs\vcredist.log
    [2344][Sun 02/18/2018 16:50:48]:Waiting for the completion of: D:\SMS_DP$\sms\bin\vcredist_x64.exe /q /norestart /l D:\SMS_DP$\sms\logs\vcredist.log
    [2344][Sun 02/18/2018 16:51:13]:Run completed for: D:\SMS_DP$\sms\bin\vcredist_x64.exe /q /norestart /l D:\SMS_DP$\sms\logs\vcredist.log
    [2344][Sun 02/18/2018 16:51:14]:Started process D:\SMS_DP$\sms\bin\ccmsetup.exe /autoupgrade /upgradetolatest /postinstallmsi:"D:\SMS_DP$\sms\bin\pulldp.msi;D:\SMS_DP$\sms\logs\pulldp_install.log"
    [2344][Sun 02/18/2018 16:51:14]:RegQueryValueExW failed for Software\Microsoft\SMS\DP, Site Code
    [2344][Sun 02/18/2018 16:51:14]:RegReadString failed; 0x80070002
    [2344][Sun 02/18/2018 16:51:14]:Failed to validate IIS and ShareFolder configurations. Return code: 0x80070002

    And now I see only the following repeating every 40 minutes. No other entries

    [FCC][Mon 02/19/2018 23:22:14]:RegQueryValueExW failed for Software\Microsoft\SMS\DP, Site Code
    [FCC][Mon 02/19/2018 23:22:14]:RegReadString failed; 0x80070002
    [FCC][Mon 02/19/2018 23:22:14]:Failed to validate IIS and ShareFolder configurations. Return code: 0x80070002


    Also, it seems the SCCM Client has stopped repairing itself and is healthy now.


    The DP version in console is fine - 5.00.8577.1000 like all others (Console->Admin->DPs)
    The Site Status for this Pull DP is in Green in the console
    Package replication errors exist

    Monday, February 19, 2018 9:13 PM
  • > "since its mandatory for pulldp"

    This is not correct.

    Have you promoted the latest client version to production?

    What happens if you remove the client agent completely as suggested?


    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by sccm72 Thursday, February 22, 2018 6:28 AM
    Monday, February 19, 2018 9:26 PM
  • Hello jason,

    We just ended up reimaging the server eventually due to lack of time.

    Thanks very much for your help throughout this case.

    Thursday, February 22, 2018 6:28 AM