none
Failed to refresh Resync state message. Error = 0x87d00310 RRS feed

  • Question

  • Hello I'm receiving the error message when trying to deploy Windows updates from SCCM to one of my server. The error message I receive is.

    Failed to refresh Resync state message. Error = 0x87d00310.

    I've setup the WSUS server on my SCCM server. I've setup the boundary groups to point to my SCCM Sever which has has WSUS on the server. 

    All the Windows update have been Synched into the SCCM server. I've created software update group and placed certain windows updates into those groups for deployment.

    I've deployed the software update groups to the computer collection I have created. 

    After deployment here is the log I received on the client computer.

    Failed to refresh sync message. Error = 0x87d00310. 5/21/2019 2:07:00 AM 5540 (0x15A4)
    Message received to refresh all update status, processing... 6/9/2019 6:27:00 PM 816 (0x0330)
    Failed to refresh Resync state message. Error = 0x87d00310. 6/9/2019 6:27:00 PM 816 (0x0330)
    Failed to refresh sync message. Error = 0x87d00310. 6/9/2019 6:27:00 PM 816 (0x0330)
    Message received to refresh all update status, processing... 6/30/2019 10:18:00 AM 4076 (0x0FEC)
    Failed to refresh Resync state message. Error = 0x87d00310. 6/30/2019 10:18:00 AM 4076 (0x0FEC)
    Failed to refresh sync message. Error = 0x87d00310. 6/30/2019 10:18:00 AM 4076 (0x0FEC)
    Message received to refresh all update status, processing... 7/20/2019 12:49:00 AM 5540 (0x15A4)
    Failed to refresh Resync state message. Error = 0x87d00310. 7/20/2019 12:49:00 AM 5540 (0x15A4)
    Failed to refresh sync message. Error = 0x87d00310. 7/20/2019 12:49:00 AM 5540 (0x15A4)
    Message received to refresh all update status, processing... 8/9/2019 8:59:00 AM 5540 (0x15A4)
    Failed to refresh Resync state message. Error = 0x87d00310. 8/9/2019 8:59:00 AM 5540 (0x15A4)
    Failed to refresh sync message. Error = 0x87d00310. 8/9/2019 8:59:00 AM 5540 (0x15A4)
    Message received to refresh all update status, processing... 8/28/2019 6:20:00 PM 5540 (0x15A4)
    Failed to refresh Resync state message. Error = 0x87d00310. 8/28/2019 6:20:00 PM 5540 (0x15A4)
    Failed to refresh sync message. Error = 0x87d00310. 8/28/2019 6:20:00 PM 5540 (0x15A4)
    Message received to refresh all update status, processing... 9/18/2019 4:18:00 PM 5540 (0x15A4)
    Failed to refresh Resync state message. Error = 0x87d00310. 9/18/2019 4:18:00 PM 5540 (0x15A4)
    Failed to refresh sync message. Error = 0x87d00310. 9/18/2019 4:18:00 PM 5540 (0x15A4)
    Message received to refresh all update status, processing... 9/20/2019 7:00:00 AM 5252 (0x1484)
    Failed to refresh Resync state message. Error = 0x87d00310. 9/20/2019 7:00:00 AM 5252 (0x1484)
    Failed to refresh sync message. Error = 0x87d00310. 9/20/2019 7:00:00 AM 5252 (0x1484)

    Friday, September 20, 2019 4:42 PM

All replies

  • After deployment here is the log I received on the client computer.

    Which log exactly?


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

    Friday, September 20, 2019 5:50 PM
  • Hi,

    We are recieving the same error code in the updatesstore.log, the handler and deployment log doesn't seem to flag any errors. Plus, the client seems to communicate and show in the console OK.

    The servers in question though are in the DMZ and Workgroup servers, but like I say, they look to be communicating OK?

    The rules for both the SCCM and SCCM_WSUS servers are put in the firewall, and I have modified the hosts file?

    Any ideas?

    Cheers

    Friday, September 27, 2019 11:23 AM
  • hey look to be communicating OK

    How are you determining this?

    What does WUAHandler.log say?

    How about ccmmessaging.log?


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

    Friday, September 27, 2019 1:12 PM
  • Hi,

    by communicating OK, I mean no errors seem to be flagging in the CCMMessaging, LocationServices, ClientIDManagerStartup, UpdatesDeployment logs

    No errors look to be showing in the WUAHandling log either, they just say SetCategoriesForStateReportingExclusion called with...….

    The one thing I have noticed that the registry hasn't updated with the WSUS location under policies\Windows\Windows Update?

    Its like the WSUS (on a different server) is being blocked? I can't ping everything and have asked the network team to make sure all the ports are open?

    I've double checked the boundary groups and the WSUS server is also added?

    Friday, September 27, 2019 1:26 PM
  • Also, bearing in mind they are workgroup 'standalone' servers, would the local accounts be a problem?

    Its tsrange that it can upload it's inventory data though, yet have issues with updates?

    Friday, September 27, 2019 1:33 PM
  • Only looking for errors is not sufficient.

    Based on what you've just said though, you've not associated your SUP with a boundary group so that it will get assigned to the client(s). As of 1802 (I think), you need to assign SUPs to clients just like DPs (using boundaries and boundary groups). I don't know anything about your environment so can't say for sure, but this can usually be be by simply associating the SUP with the default site boundary group.


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

    Friday, September 27, 2019 1:33 PM
  • yeah, at first I thought the boundary groups. But when I added it (well, the SUP, WSUS, everything!), there has been no change?.

    I'll have another look in case I've missed something....

    Friday, September 27, 2019 1:39 PM
  • Hi, 

    OK, I've sorted my issue. the boundaries were all OK, but what I did notice was that the client connection type only allowed intranet only connections. I changed that to Intranet and Internet, left it 30 minutes and it sprung to life!

    Happy Days

    Cheers

    • Proposed as answer by Wookie5375 Friday, September 27, 2019 2:47 PM
    Friday, September 27, 2019 2:47 PM