asked on

SCCM 2012 SP1 - Distrubition points not updating

Hi recently something went wrong with two secondary site , distribution points. It seems as though they kicked off a complete re-distribution of all packages. These consist of windows and endpoint protection updates. I've been struggling for a month without the in progress bar moving. Things I've noticed is that the despool.inbox is filling up like crazy. one secondary site has a database replication link as failed, think its un-related though as the other site replication is active and I have the same content update issue with it. looking at the logs I see the distmgr.log keeps saying using 0 of 3 processing threads. the smsdpmon.log has errors 0x80070003 failed to evaluate package. Since this isn't 2012 r2 I cant use the tools to monitor the distribution points progress, so I'm not sure if anything is actually working.
Below are some extracts from the secondary site server
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:09:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:14:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:19:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:24:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:29:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:34:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:39:19 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:44:19 PM      3832 (0x0EF8)
Cannot open file e:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\11lw4p01.sni. Cause is 11      SMS_DESPOOLER      2016/06/21 10:45:52 PM      3832 (0x0EF8)
Cannot read e:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\11lw4p01.sni, skip it      SMS_DESPOOLER      2016/06/21 10:45:52 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:45:52 PM      3832 (0x0EF8)
Site currently is in maintenance mode and e:\Program Files\Microsoft Configuration Manager\inboxes\despoolr.box\receive\11lw4p01.sni is not DRS init or certificate exchange package, backup it until site becomes active.      SMS_DESPOOLER      2016/06/21 10:46:01 PM      3832 (0x0EF8)
Waiting for ready instruction file....      SMS_DESPOOLER      2016/06/21 10:46:01 PM      3832 (0x0EF8)
2.
Start to evaluate all packages ...      SMS_Distribution_Point_Monitoring      2016/06/29 05:41:39 AM      6660 (0x1A04)
Start to evaluate package 'P01000A0' version 0 ...      SMS_Distribution_Point_Monitoring      2016/06/29 05:41:39 AM      6660 (0x1A04)
Report status message 0x4000094C to MP      SMS_Distribution_Point_Monitoring      2016/06/29 05:41:39 AM      6660 (0x1A04)
Status message has been successfully sent to MP from remote DP      SMS_Distribution_Point_Monitoring      2016/06/29 05:41:39 AM      6660 (0x1A04)
CContentDefinition::CheckFiles failed; 0x80070003      SMS_Distribution_Point_Monitoring      2016/06/29 05:43:38 AM      6660 (0x1A04)
Failed to evaluate package P01000A0, Error code 0x80070003      SMS_Distribution_Point_Monitoring      2016/06/29 05:43:38 AM      6660 (0x1A04)
Report state message 0x8000094F to MP      SMS_Distribution_Point_Monitoring      2016/06/29 05:43:38 AM      6660 (0x1A04)
Report Body: <ReportBody><StateMessage MessageTime="20160629034338.000000+000" SerialNumber="0"><Topic ID="P01000A0" Type="901" IDType="0"/><State ID="2383" Criticality="0"/><UserParameters Flags="0" Count="2"><Param>P01000A0</Param><Param>["Display=\\servername\"]MSWNET:["SMS_SITE=S02"]\\servername\</Param></UserParameters></StateMessage></ReportBody>
      SMS_Distribution_Point_Monitoring      2016/06/29 05:43:38 AM      6660 (0x1A04)
Report status message 0x8000094F to MP      SMS_Distribution_Point_Monitoring      2016/06/29 05:43:38 AM      6660 (0x1A04)
Status message has been successfully sent to MP from remote DP      SMS_Distribution_Point_Monitoring      2016/06/29 05:43:38 AM      6660
(0x1A04)

Primary site: sender.log
Wrote 968360 bytes to \\servername\SMS_SITE\11M9GP01.PCK at position 1348796056      SMS_LAN_SENDER      6/29/2016 1:58:38 PM      13444 (0x3484)
Attempt to write 968360 bytes to \\servername\SMS_SITE\11M9GP01.PCK at position 1349764416      SMS_LAN_SENDER      6/29/2016 1:58:38 PM      13444 (0x3484)
Wrote 1048576 bytes to \\otherDP\SMS_SITE\11MCNP01.PCK at position 452190994      SMS_LAN_SENDER      6/29/2016 1:58:38 PM      7588 (0x1DA4)
Attempt to write 1048576 bytes to \\otherDP\SMS_SITE\11MCNP01.PCK at position 453239570      SMS_LAN_SENDER      6/29/2016 1:58:38 PM      7588 (0x1DA4)
Wrote 1048576 bytes to \\servername\SMS_SITE\11M7SP01.PCK at position 7756045312      SMS_LAN_SENDER      6/29/2016 1:58:40 PM      15720 (0x3D68)
Attempt to write 1048576 bytes to \\servername\SMS_SITE\11M7SP01.PCK at position 7757093888      SMS_LAN_SENDER      6/29/2016 1:58:40 PM      15720 (0x3D68)
Wrote 977900 bytes to \\otherDP\SMS_SITE\11MCPP01.PCK at position 30501124      SMS_LAN_SENDER      6/29/2016 1:58:42 PM      9296 (0x2450)
Attempt to write 977900 bytes to \\otherDP\SMS_SITE\11MCPP01.PCK at position 31479024      SMS_LAN_SENDER      6/29/2016 1:58:42 PM      9296 (0x2450)
Wrote 1048576 bytes to \\servername\SMS_SITE\11M94P01.PCK at position 4182372004      SMS_LAN_SENDER      6/29/2016 1:58:42 PM      5864 (0x16E8)
Attempt to write 1048576 bytes to \\servername\SMS_SITE\11M94P01.PCK at position 4183420580      SMS_LAN_SENDER      6/29/2016 1:58:42 PM      5864 (0x16E8)
Wrote 968360 bytes to \\servername\SMS_SITE\11M9GP01.PCK at position 1349764416      SMS_LAN_SENDER      6/29/2016 1:58:44 PM      13444 (0x3484)
Attempt to write 968360 bytes to \\servername\SMS_SITE\11M9GP01.PCK at position 1350732776      SMS_LAN_SENDER      6/29/2016 1:58:44 PM      13444 (0x3484)

ASKER CERTIFIED SOLUTION

Mike Taylor

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

TTAF3

ASKER

Hi Mike thanks for your suggestions. I have seen these posts previously and actioned them without much success. I will say however that umair post was more helpful. I've identified that I'm in maintenance mode on one of my secondary site servers. This I believe happened because I was setting up another distribution point that would be in pre-staged mode, it would be using another DP site as a source. stupidly I removed the role from this new distribution point, before letting it completely install. I noticed now that beside the replication issue the source DP that was going to update the new server is at 41% complete.(see attached). The tools you mentioned as well I have installed. they don't work on SCCM 2012 SP1. If you have some way to get it work then great. Please advise.
C--Users-lyndonr-Pictures-dp-stuck.JPG
C--Users-lyndonr-Pictures-dp-stuck2.JPG

Mike Taylor

Hi,
If you have SP1 then the RTM tools should work fine: https://www.microsoft.com/en-us/download/details.aspx?id=29265.

Yes, CM is never quick. As a rule when you add a role, use CMTrace to open the relevant log and watch it carefully and don't process until it says 100% complete. Normally adding a DP takes 15-20 mins tops, but there may always be gotchas lurking.

Mike

TTAF3

ASKER

Hi Mike thanks I managed to use to tools to eventually find that drsqueue was disabled in the SQL DB when re-enabling replication began working again. likewise the updates started to re-distribute once again.

now I need to fix my image deployment as it fails with 0x800002 error.

Mike Taylor

Crikey that's odd but glad you fixed it.

Feel free to post another question re the image and I'll take a look :).