locked
Service connection Point - Critical (1606) RRS feed

  • Question

  • Hi,

    I upgraded our DEV to 1606 last Friday, (used the powershell script to be in first ring) everything went smooth without any errors. Today I checked the Site status and saw that my Service Connection Point is critical, the Availability is Falied. (role is on the Site Server)

    When I check the status messages there a no Errors or warnings displayed. What other log files can I check to find the reason of the Critical state?

    I already removed the Connection Point role and re-installed it without any luck.  The dmpdownloader.log doesnt give me an error when I trigger a Check for updates from the Updates and Servicing node.


    Upgrade path - 1511 - 1602 - 1606
    • Edited by Tim NL Wednesday, July 27, 2016 7:56 PM added upgrade path
    Monday, July 25, 2016 7:33 AM

Answers

  • Part of the fast-ring update just released: https://support.microsoft.com/en-us/kb/3180992

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

    • Marked as answer by Tim NL Monday, August 8, 2016 9:25 PM
    Monday, August 8, 2016 8:17 PM

All replies

  • Same here after updating a new 1511 Site to 1606 this morning. Status of the Component "Service Connection Point" was "OK" before the 1606 Update and remains in "Critical" Status after the Update.

    Status Messages and the Log-Files are showing no Errors or at least I can't find any.

    Could we have our first 1606 Bug?


    Simon Dettling | msitproblog.com | @SimonDettling



    Monday, July 25, 2016 12:13 PM
  • I am seeing the same. Product Group is informed.

    Torsten Meringer | http://www.mssccmfaq.de

    Monday, July 25, 2016 12:32 PM
  • Product Group is informed.

    Torsten Meringer | http://www.mssccmfaq.de

    Thanks :)

    Simon Dettling | msitproblog.com | @SimonDettling

    Monday, July 25, 2016 12:36 PM
  • Thanks Torsten, I also filed a bug report because this stops us from upgrading the production environment.

    https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/2982777

    Wednesday, July 27, 2016 7:55 PM
  • I have some Errors in DMPDownloader.log and DMPUploader.log file. I added them to the connect case.

    There are some "too busy" messages in that Logs, therefore i assume the service itself is very busy at the moment due to many requests at the same time...


    • Edited by Michael-CM Wednesday, July 27, 2016 8:37 PM
    Wednesday, July 27, 2016 8:26 PM
  • I got some Information on Twitter, that the SCP being Critical is benign, unless using ConfigMgr in a Hybrid Environment.

    https://twitter.com/djammmer/status/758000469063012352

    Anyway, for me this clearly is a Bug. At least at 1511 the SCP was in a Green State before I went to 1606.


    Simon Dettling | msitproblog.com | @SimonDettling

    Thursday, July 28, 2016 5:17 AM
  • Anyway, for me this clearly is a Bug. At least at 1511 the SCP was in a Green State before I went to 1606.


    Simon Dettling | msitproblog.com | @SimonDettling

    Definitely a bug. Also SCP in 1602 was in a Green state and not critical. I cant stand the fact that there is a red critical status in my environment ;)

    Let's wait and see what the MS connect will report back to us.

    PS: I'm running a 1602 environment in production. The log files are al exact the same and there the SCP is in a green state. (So it has nothing to do with a too busy connection)

       

    • Edited by Tim NL Thursday, July 28, 2016 7:35 AM
    Thursday, July 28, 2016 6:49 AM
  • This has been confirmed as a benign issue for non-hybrid environments by the product group. It will require a fix, but there's no impact other than having a big red X at the moment.

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

    Friday, July 29, 2016 3:10 PM
  • MS Connect:

    Field Status changed from [Active] to [Resolved]
    Field Resolution changed from [None] to [Fixed]

    But I don't see any comment on what fixes the "issue".

    Thursday, August 4, 2016 12:59 PM
  • I think that there's a hotfix coming.

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

    Thursday, August 4, 2016 2:42 PM
  • I also add a comment to this connect case. Everytime the Status is changed on the connect cases they don't comment how and when it will be solved.
    Thursday, August 4, 2016 3:03 PM
  • Thursday, August 4, 2016 6:05 PM
  • Part of the fast-ring update just released: https://support.microsoft.com/en-us/kb/3180992

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

    • Marked as answer by Tim NL Monday, August 8, 2016 9:25 PM
    Monday, August 8, 2016 8:17 PM
  • Thanks for the info, Jason.
    Monday, August 8, 2016 9:01 PM
  • I've Installed the sccm 1606 Hotfix https://support.microsoft.com/en-us/kb/3180992, 

    still showing Critical error on Service Connection Point.

    Tuesday, August 9, 2016 4:43 AM
  • Same here.  Still showing critical after hotfix.

    Not sure if it's related but if you look at the database with the query:

    select * from Summarizer_SiteSystem

    The InstallationState column for the "SMS Dmp Connector" Role is set to "6".  Same in my case for the FSP on that same site server which is also showing critical.  

    All other roles that show green in the site status are either InstallationState of "0" or "3"

    Tuesday, August 9, 2016 5:43 PM
  • The PG are aware that the issue still exists even after installing KB3180992. As Jason explained above though there is no functional impact - just a false positive error on the SCP.


    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson

    Tuesday, August 9, 2016 5:59 PM
  • https://support.microsoft.com/en-us/kb/3180992

    After applying the Hotfix-

    • Change the Availability State registry value from 1 to 4 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\SMS Dmp Connector.
    • Restart the SMS Executive service on the site server.has worked for me.
    • Proposed as answer by t3cknic1an Friday, August 19, 2016 2:49 PM
    Tuesday, August 9, 2016 11:25 PM
  • The Availability State value was already set to 4 on my SCP site server.

    Restarted the SMS Executive service doesn't resolve the critical status.

    Wednesday, August 10, 2016 6:25 PM
  • This worked for me. Thanks!
    Friday, August 19, 2016 2:49 PM
  • I think this has got fixed in CM 1606 hotfix(KB3184153).
    Tuesday, August 23, 2016 6:49 AM
  • I think this has got fixed in CM 1606 hotfix(KB3184153).

    It was fixed in KB3180992, however it might not work for anyone, see previous answers.

    For me applying KB3180992 with the manual modifcations described in the KB (!) worked. However, a Reset of the Component was needed via the Console.


    Simon Dettling | msitproblog.com | @SimonDettling

    Tuesday, August 23, 2016 11:21 AM