locked
Service connection point issues after applying 1606 Hotfix (KB3184153) RRS feed

  • Question

  • Hi all,

    We have been encountering a strange issue with the Service Connection Point role since we installed the 1606 Hotfix on 18th August and suspect something may have gone wrong during the upgrade. Whenever we start the SMS_EXECUTIVE service, we see the following messages in the dmpdownloader.log (I've obfuscated the site name and server name, but have confirmed these are correct):

    SMS_EXECUTIVE started SMS_DMP_DOWNLOADER as thread ID 16984 (0x4258).	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	7480 (0x1D38)
    SMS_DMP_DOWNLOADER is starting...	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Connecting to MessageDownloader.	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Downloader logging level set to: 1	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Components\SMS_DMP_UPLOADER\:SQL Server Name from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <FQDN of Primary Site Server> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Components\SMS_DMP_UPLOADER\:Database Name from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <Site Code> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Identification:Server from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <FQDN of Primary Site Server> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Identification:Site Server from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <FQDN of Primary Site Server> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Identification:Server from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <FQDN of Primary Site Server> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\MPFDM\Inboxes\:State System (Incoming - high priority) from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value d:\program files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\high from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Identification:Site Server from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <FQDN of Primary Site Server> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Identification:Server from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value <FQDN of Primary Site Server> from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\MPFDM\Inboxes\:Hierarchy Manager (Forwarding messages) from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value d:\program files\Microsoft Configuration Manager\inboxes\hman.box\ForwardingMsg from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Components\SMS_DMP_UPLOADER\:OfflineMode from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value 0 from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Reading SOFTWARE\Microsoft\SMS\Identification:Installation Directory from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Returning value d:\program files\Microsoft Configuration Manager from provider Registry	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    Failed to call Initialize. error = [error code: -2147467261, error message: Invalid pointer].	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    SMS_DMP_DOWNLOADER is exiting...	SMS_DMP_DOWNLOADER	24/08/2016 11:00:21	16984 (0x4258)
    

    The Component Status screen shows the following error for SMS_DMP_DOWNLOADER:

    Type: Milestone
    Severity: Error
    Message ID: 1104
    Process ID: 6216
    Thread ID: 7916
    Description: SMS Executive detected that this component stopped unexpectedly.
    
    Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly.
    Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.

    We have tried removing and reinstalling the Service connection point role on the Primary Site Server and have also tried installing the role on a different server, but the same errors are logged once the SMS_DMP_DOWNLOADER service starts.

    This role was working previously (as we were able to download and install the 1606 update and the hotfix without problems). Has anyone else encountered problems similar to this and can you recommend any steps for troubleshooting?

    Many thanks,

    Robin

    Wednesday, August 24, 2016 1:14 PM

Answers

  • We have managed to resolve this on our Primary Site Server after comparing registry values with a virtual lab environment. It appears that our production system was missing the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR

    We also created two blank string values under this key named ProxyUserName and ProxyUserPassword (as these were present, but also blank, in our lab environment). 

    After recreating these values and restarting the SMS_EXECUTIVE service, the SMS_DMP_DOWNLOADER service started successfully and was able to connect to Microsoft and pull down package metadata.

    We've no idea how the registry key got deleted in the first place, but are glad to have found a fix. Hope this is useful to anyone in the same boat!

    Many thanks,

    Robin

    • Marked as answer by Robin Garrett Thursday, August 25, 2016 10:09 AM
    Thursday, August 25, 2016 10:09 AM

All replies

  • confirm. exactly the same problem.
    Wednesday, August 24, 2016 2:11 PM
  • We are seeing this with the SMS_StATE_MIGRATION_POINT after applying the hotfix for 1606. We decided to apply the hotfix to see if it would resolve the issue we are having with client push installs since we applied the 1606 update. Ever since applying the 1606 update it seems to have broke BiTs downloads. Hope the hotfix would help but it caused more issues.
    Wednesday, August 24, 2016 4:16 PM
  • We have managed to resolve this on our Primary Site Server after comparing registry values with a virtual lab environment. It appears that our production system was missing the following key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR

    We also created two blank string values under this key named ProxyUserName and ProxyUserPassword (as these were present, but also blank, in our lab environment). 

    After recreating these values and restarting the SMS_EXECUTIVE service, the SMS_DMP_DOWNLOADER service started successfully and was able to connect to Microsoft and pull down package metadata.

    We've no idea how the registry key got deleted in the first place, but are glad to have found a fix. Hope this is useful to anyone in the same boat!

    Many thanks,

    Robin

    • Marked as answer by Robin Garrett Thursday, August 25, 2016 10:09 AM
    Thursday, August 25, 2016 10:09 AM
  • Hi,

    I'm seeing the exact same Problem in my logs, however I have the Service Connector Point running on a seperate System.

    The aforementioned key and values are present on the Primary site Server, but not on the SCP Server. Does anyone know if they need to be present on both Systems? I'd install a test System to see for myself, but this time time is of the essence :-/

    Best Regards,

    Fred 

    Wednesday, September 14, 2016 1:36 PM
  • Hi Robin Garrett

    Thanks for your solution

    I created the registry keys that you described and restarting the SMS_EXECUTIVE service.

    The changes I have add is to remove the proxy settings from site system properties
    (
    Untick  "use proxy server…..")

    Then I reapply the proxy settings and the keys for ProxyUserPassword and ProxyUserName has been set in the registry.

    Now everything is working well

    many thank again.

    Monday, September 19, 2016 7:49 AM
  • Hello Robin,

    Thanks for your solution.
    We were having the same issue and your solution fixed it.

    Thanks

    Marc

    Monday, September 19, 2016 9:22 AM
  • I had exactly the same issue - thanks for the fix :)
    Tuesday, November 29, 2016 9:59 AM
  • Great find! That got the component going again.
    Friday, December 9, 2016 3:17 PM
  • Although creating the keys mentioned in the post will start the dpmconnector normally again, without error, be aware of the following:

    When your company uses a proxyserver and you have enabled your proxy server on your sitesystem role, the proxy account credentials will be entered in these keys:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR ProxyUserName

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR ProxyUserPassword

    The password key is encrypted and can (somehow) be left blanc. But be sure to fill in your domain\username in the proxyusername key. If you dont, at the next CMupgrade, you wont be able to download the manifest files.

    ERROR: Failed to download redist for 91406b1d-7c14-42d8-a68b-484be5c5e9b8 with command  /RedistUrl http://go.microsoft.com/fwlink/?LinkID=831290 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=831291 /RedistVersion 112015 /ProxyUri <a href="http://:<port>/">http://<proxyservername>:<port>/ /ProxyUserName  /ProxyUserPassword".

    and update and servicing state will stay at "downloading" forever.

    Sadly I found out the hard way ;-)

    Kr,

    Jan




    Monday, December 12, 2016 8:30 AM
  • Hi,

    In my situation I had to do an extra step.

    I had to reapply the proxy account password in the SCCM console under Administration > Overview > Security > Accounts before I could get the below registry values populated:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR ProxyUserName

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR ProxyUserPassword

    Thursday, December 15, 2016 4:27 AM
  • in my case, i have to add the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR key and the ProxyUserName and ProxyUserPassword strings.

    but... i have some errors trying to download some cab's file because in my network have a proxy, the SCCM Server have full access free to internet, but they discover the proxy and try to auth wiht blank user and password.

    I set the properties of the site System Role (Site System) and clear in the proxy tab "Use a proxy server when sunchronizing information from the internet".

    Now is working fine.
    Wednesday, January 25, 2017 1:40 PM
  • Had the same issue with downloading 1702, changing the Proxy account and setting it back to the old account afterwards did it. The ProxyUserName and ProxyUserPassword entries in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR were filled afterwards.
    Friday, April 14, 2017 11:55 AM