<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>UpdatesStore.log Archives - the Sysadmin Channel</title>
	<atom:link href="https://thesysadminchannel.com/tag/updatesstore-log/feed/" rel="self" type="application/rss+xml" />
	<link>https://thesysadminchannel.com/tag/updatesstore-log/</link>
	<description>Documenting My Life as a System Administrator</description>
	<lastBuildDate>Tue, 09 Apr 2019 04:27:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
<site xmlns="com-wordpress:feed-additions:1">144174110</site>	<item>
		<title>[Solved] SCCM Failed To Refresh Resync State Message Error 0x87d00310 in UpdatesStore.log</title>
		<link>https://thesysadminchannel.com/failed-to-refresh-resync-state-message-error-0x87d00310/</link>
					<comments>https://thesysadminchannel.com/failed-to-refresh-resync-state-message-error-0x87d00310/#respond</comments>
		
		<dc:creator><![CDATA[Paul Contreras]]></dc:creator>
		<pubDate>Tue, 10 Jul 2018 01:31:07 +0000</pubDate>
				<category><![CDATA[SCCM]]></category>
		<category><![CDATA[Error 0x87d00310]]></category>
		<category><![CDATA[failed to refresh resync state message]]></category>
		<category><![CDATA[Failed to refresh sync message]]></category>
		<category><![CDATA[SCCM Software Update errors]]></category>
		<category><![CDATA[troubleshoot SCCM SUP]]></category>
		<category><![CDATA[UpdatesStore.log]]></category>
		<guid isPermaLink="false">https://thesysadminchannel.com/?p=719</guid>

					<description><![CDATA[<p>In this article I&#8217;m going to go over the quick steps on how to fix the failed to refresh resync state message. Error = 0x87d00310 and Failed to refresh sync message. Error = 0x87d00310. you find in the UpdatesStore.log A&#8230; <a href="https://thesysadminchannel.com/failed-to-refresh-resync-state-message-error-0x87d00310/" class="more-link">Continue Reading <span class="meta-nav">&#8594;</span></a></p>
<p>The post <a href="https://thesysadminchannel.com/failed-to-refresh-resync-state-message-error-0x87d00310/">[Solved] SCCM Failed To Refresh Resync State Message Error 0x87d00310 in UpdatesStore.log</a> appeared first on <a href="https://thesysadminchannel.com">the Sysadmin Channel</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>In this article I&#8217;m going to go over the quick steps on how to fix the <strong>failed to refresh resync state message. Error = 0x87d00310</strong> and <strong>Failed to refresh sync message. Error = 0x87d00310.</strong> you find in the <strong>UpdatesStore.log</strong></p>
<p>A client recently <a href="https://thesysadminchannel.com/how-to-upgrade-to-sccm-1606-from-sccm-2012-r2/" target="_blank">upgraded an SCCM environment to 1606</a> and decided they wanted to move forward with Software Updates through SCCM. They followed my guides for <a href="https://youtu.be/3-2qhfvt8vo" rel="noopener" target="_blank">getting everything setup post installation</a> and everything was great until they added the separate WSUS server as a SUP site system role.  Normally, if they were to install the WSUS role on the same server as the SCCM server they wouldn&#8217;t have this problem, but since SCCM and WSUS are two separate servers this problem came into play.  Until this issue is resolved, all client computers won&#8217;t be able to scan in for the latest updates.  Needless to say this quickly became a top priority.</p>
<p><a href="https://thesysadminchannel.com/wp-content/uploads/2018/07/Failed-to-Refresh-Resync-State-Message.-Error-0x87d00310.png" target="_blank"><img fetchpriority="high" decoding="async" src="https://thesysadminchannel.com/wp-content/uploads/2018/07/Failed-to-Refresh-Resync-State-Message.-Error-0x87d00310-1024x534.png" alt="Failed to Refresh Resync State Message. Error = 0x87d00310" width="1024" height="534" class="aligncenter size-medium wp-image-723" srcset="https://thesysadminchannel.com/wp-content/uploads/2018/07/Failed-to-Refresh-Resync-State-Message.-Error-0x87d00310-1024x534.png 1024w, https://thesysadminchannel.com/wp-content/uploads/2018/07/Failed-to-Refresh-Resync-State-Message.-Error-0x87d00310-768x401.png 768w, https://thesysadminchannel.com/wp-content/uploads/2018/07/Failed-to-Refresh-Resync-State-Message.-Error-0x87d00310.png 1442w" sizes="(max-width: 1024px) 100vw, 1024px" /></a><br />
&nbsp;</p>
<h2>Failed To Refresh Resync State Message Error 0x87d00310 Fix</h2>
<p>After hours of troubleshooting I was finally able to figure out the root problem and it all had to do with boundary groups.  So lets get to the fix!!</p>
<ul>
<li>In the SCCM Administration Console go to <strong>Administration -> Boundaries -> Properties of the Boundary Groups</strong> you created.</li>
<li>Just make sure those are created and added properly.</li>
</ul>
<p><a href="https://thesysadminchannel.com/wp-content/uploads/2018/07/Check-Boundary-Groups-Properties.png" target="_blank"><img decoding="async" src="https://thesysadminchannel.com/wp-content/uploads/2018/07/Check-Boundary-Groups-Properties.png" alt="Check Boundary Groups Properties" width="929" height="458" class="aligncenter size-full wp-image-725" srcset="https://thesysadminchannel.com/wp-content/uploads/2018/07/Check-Boundary-Groups-Properties.png 929w, https://thesysadminchannel.com/wp-content/uploads/2018/07/Check-Boundary-Groups-Properties-768x379.png 768w" sizes="(max-width: 929px) 100vw, 929px" /></a><br />
&nbsp;</p>
<ul>
<li>Next go to <strong>Administration -> Boundary Groups -> Properties of the Boundary Groups</strong></li>
<li>Click on the <strong>References</strong> tab and make sure your WSUS server is added as a site system.</li>
<li>Be sure to also Check the boxes for site assignment.</li>
</ul>
<p><a href="https://thesysadminchannel.com/wp-content/uploads/2018/07/Boundary-Group-Properties-Check.png" target="_blank"><img decoding="async" src="https://thesysadminchannel.com/wp-content/uploads/2018/07/Boundary-Group-Properties-Check.png" alt="Boundary Group Properties Check" width="975" height="429" class="aligncenter size-full wp-image-728" srcset="https://thesysadminchannel.com/wp-content/uploads/2018/07/Boundary-Group-Properties-Check.png 975w, https://thesysadminchannel.com/wp-content/uploads/2018/07/Boundary-Group-Properties-Check-768x338.png 768w" sizes="(max-width: 975px) 100vw, 975px" /></a></p>
<p><a href="https://thesysadminchannel.com/wp-content/uploads/2018/07/Boundary-Group-Properties-Reference-Check.png" target="_blank"><img decoding="async" src="https://thesysadminchannel.com/wp-content/uploads/2018/07/Boundary-Group-Properties-Reference-Check.png" alt="Boundary Group Properties Reference Check" width="648" height="594" class="aligncenter size-full wp-image-729" /></a><br />
&nbsp;</p>
<ul>
<li>Give it some time for SCCM to do all the necessary syncs it needs.</li>
<li>On the client machine go to <strong>Control Panel -> Configuration Manager -> Actions</strong> Tab.</li>
<li>Rerun the <strong>Machine Policy Retrieval &#038; Evaluation Cycle</strong>.</li>
<li>Rerun the <strong>Software Update Deployment Evaluation Cycle</strong>.</li>
<li>Rerun the <strong>Software Update Scan Cycle</strong>.</li>
</ul>
<p><a href="https://thesysadminchannel.com/wp-content/uploads/2018/07/SCCM-Rerun-Sync-Cycle.png" target="_blank"><img decoding="async" src="https://thesysadminchannel.com/wp-content/uploads/2018/07/SCCM-Rerun-Sync-Cycle.png" alt="SCCM Rerun Sync Cycle" width="399" height="484" class="aligncenter size-full wp-image-732" /></a></p>
<p>&nbsp;</p>
<ul>
<li>Check the <strong>UpdatesStore.log</strong> located in C:\Windows\CCM\Logs and it should show that the <strong>refresh status completed successfully</strong>.</li>
</ul>
<p><a href="https://thesysadminchannel.com/wp-content/uploads/2018/07/Refresh-status-completed-successfully.png" target="_blank"><img decoding="async" src="https://thesysadminchannel.com/wp-content/uploads/2018/07/Refresh-status-completed-successfully-1024x536.png" alt="Refresh status completed successfully" width="1024" height="536" class="aligncenter size-medium wp-image-733" srcset="https://thesysadminchannel.com/wp-content/uploads/2018/07/Refresh-status-completed-successfully-1024x536.png 1024w, https://thesysadminchannel.com/wp-content/uploads/2018/07/Refresh-status-completed-successfully-768x402.png 768w, https://thesysadminchannel.com/wp-content/uploads/2018/07/Refresh-status-completed-successfully.png 1105w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></p>
<p>So hopefully this article was able to resolve your failed To refresh resync state message issues.  If you want to further your SCCM knowledge, be sure to check out <a href="https://amzn.to/2L0dnMW" target="_blank">Mastering System Center Configuration Manager</a>.  Also, don&#8217;t forget to check us out on our <a href="https://www.youtube.com/channel/UC9VnUjmZrNG3ithDZmG-S-g" rel="noopener" target="_blank">YouTube Channel</a> to get more sysadmin related videos and cool content.</p>
<p>The post <a href="https://thesysadminchannel.com/failed-to-refresh-resync-state-message-error-0x87d00310/">[Solved] SCCM Failed To Refresh Resync State Message Error 0x87d00310 in UpdatesStore.log</a> appeared first on <a href="https://thesysadminchannel.com">the Sysadmin Channel</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://thesysadminchannel.com/failed-to-refresh-resync-state-message-error-0x87d00310/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">719</post-id>	</item>
	</channel>
</rss>
