Issues distributing content to DPs

Hi I have lots of issues distributing packages (any .. driver packages seem especially bad) to DPs. If you check distmgr.log I cant see anything really happening just messages as below.
PkgXferMgr.log doesnt reveal much either. It seems its not doing a lot ..
I am not sure if I am doing something fundamentally wrong when distributing packages and apps. It just seems I have the same issues I had in 2007 where when I try and deploy say 20 packages to several DPs its pot luck whether it makes it to all of them.
I really need this to work properly so e.g when I create a new OSD image with 30 new apps I can deploy to 20 DPs and be fairly confident it will make it to 18 of them ..If there "best practice" for distributing packages ?
Also if you check the "All Active Content Distribution" report the information is incorrect. Is there a way of seeing what packages are currently being transferred with a percentage complete or something ?
Appreciate any help here guys.
permanently deleting E7BAD7D896128F3D1B76BE40B689A0A114CCD993E3E33981A7D6D51026FAD052 SMS_DISTRIBUTION_MANAGER 1/30/2014 10:41:01 AM 5468 (0x155C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 1/30/2014 10:41:59 AM 5256 (0x1488)
permanently deleting DAF6E0AAA324A3E9250FBA7976CF6AD3EC60F37043CB9D3206E87DFF39484CBC SMS_DISTRIBUTION_MANAGER 1/30/2014 10:42:05 AM 5468 (0x155C)
permanently deleting C50F170E53C27691CD60DFA2EA980576E7DEFC4136F15A0A29DEEE3B9548022D SMS_DISTRIBUTION_MANAGER 1/30/2014 10:43:10 AM 5468 (0x155C)
permanently deleting 05967E93CD4A44B127E26F567986649DEDEDFB87BD463FCA32D2F5298A77FE36 SMS_DISTRIBUTION_MANAGER 1/30/2014 10:44:14 AM 5468 (0x155C)
permanently deleting C7F74F40D708D590EDB5D2ED064CF9C279FB1EBE33EDED073391E4D5E1CEE046 SMS_DISTRIBUTION_MANAGER 1/30/2014 10:45:21 AM 5468 (0x155C)
permanently deleting CDE3F166613BE98B2EE3EBE892DBBA176E22E0ADC1FCE31E5AF9D010154B3743 SMS_DISTRIBUTION_MANAGER 1/30/2014 10:46:28 AM 5468 (0x155C)
permanently deleting D84E3303730133A2488C1EE4165AB7771AAD1D4E5E34D4BB4C99E53E96C8605B SMS_DISTRIBUTION_MANAGER 1/30/2014 10:47:37 AM 5468 (0x155C)

Hi,
This is also possible that the pull-distribution point cannot download the content from source distribution point. In this case, Pkgxfermgr.log, PullDP.log and DataTransferService.log need to be checked.
Juke Chou
TechNet Community Support

Similar Messages

Removing and Re-distributing content to DP groups

Hi all,
Would be keen to see if anyone else has this problem...
Example: you have a DP group with ALL distribution points - lets say you have 5 in this group.
DP1, DP2, DP3, DP4, DP5
You send out a package update to the ALL DP's group - 4 arrive successfully, 1 fails.
You re-distribute the package to the failed DP, it fails again.
Now you want to remove the package, and add it again for troubleshooting. You remove the DP, you can now see that the package is sent only to 4 distribution points.
So now you re-add it, so distribute content, it's recognized as available to send to it, you add it in. and nothing - it won't update at all and won't send the package out.
The only way i found around this is to remove the whole DP group, but this then removes ALL dp's from the packages target, which is a giant pain in the rear as it means you have to re-distribute the whole package elsewhere.
Anyone else got this? A friend of mine replicated it on his own environment too, is this a bug?
Jack

I have seen a similar problem in my SCCM 2012 R2 environment. Yesterday, I wrapped up a case with Microsoft and was refunded because this is a known issue with 2012 R2. The engineer couldn't comment on when a fix would be available.
The symptom that I am seeing is that the content for the package never makes it to the distribution point. As far as all the logs are concerned, the package exists on the remote DP (the console even shows success on both the monitoring context, as
well as the status in the software library). However, if you try to deploy (in my case it was an operating system with a driver package), the sequence fails because the DP does not have the package.
This is the "workaround" I got from Microsoft:
Issue: Packages doesn’t get distribute properly on the DPs and “Monitoring Tab” shows the size of the package 0 MB.
Probable Cause: After upgrading to R2 or even with fresh installation of R2 sometimes the content lib structure doesn’t get structured in a proper way and whenever we distribute the package, the package actually doesn’t get
distribute properly even though it shows as distributed in the monitoring status.
Resolution: In order to resolve the issue, we just need to update the content/package on the DP again. Simply go the package/content and say “Update Distribution points” and it fix the issues.
I'm not 100% sure we're talking about the same thing, but the big visual indicator is that the console shows the package size as 0.0 MB. Redistributing it or validating the content does not seem to fix it. Apparently you have to Update all DPs
instead.

Distributing contents from source to DP - BITS?

I want to clarify if distribute contents from source to DP (both regular DP and Pull DP) is using BITS?
I think from source to Pull DP is using BITS, but I am not 100% about from source to regular DP.

I think from source to Pull DP is using BITS
Just a small point. Pull DPs only get content from other DPs.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Distribution Points not appearing when trying to distribute content

Hello,
When I try to distribute content for a OS task sequence to a distribution point to my 2 distribution points using distribute content wizard, my distribution points are never shown. When I click Add distribution points, the available distribution points are
empty. Just this morning I distributed the content for boot images, packages, applications, Operating system images, and operating system installers.
how can it work for these and not for Task sequence, if it is rights related. I tried to delete and recreate the task sequence, but still the DP don't show up in the list.
I understand that once the content is distributed to a DP, the DP won't show up in the list of DP when trying to distribute content. I don't see the task sequence listed on the DPs under content, but see the other boot images, etc.
•Site Status and Component Status are all green under Monitoring.
•The distribution Point configuration Status is a green Arrow.
12 successful, 0 in progress and 0 error
•Drive Settings for these DPs are set to 15,000 mb
•I have rebooted the DP, SQL and PS Server.
Thanks,
Mark

Hello,
When I try to distribute content for a OS task sequence to a distribution point
to my 2 distribution points using distribute content wizard, my distribution points are never shown. When I click Add distribution points, the available distribution points are empty.  Just this morning I distributed the content for boot images,
packages, applications, Operating system images, and operating system installers. how can it work for these and not for Task sequence, if it is rights related. I tried to delete and recreate the task sequence, but still the DP don't show up in the list.
I understand that once the content is distributed to a DP, the DP won't show up in the list of DP when trying to distribute content. I don't see the task sequence listed on the DPs under content, but see the other boot images, etc.
Site Status and Component Status are all green under Monitoring.
The distribution Point configuration Status is a green Arrow. 12 successful, 0 in progress and 0 error
Drive Settings for these DPs are set to 15,000 mb
I have rebooted the DP, SQL and PS Server.
Distmgr.log
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
Ignoring drive C:\. File C:\NO_SMS_ON_DRIVE.SMS exists.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
Share SMSPKGE$ exists on distribution point \\TXSCCMPSDR01.DR.LPL.COM\SMSPKGE$
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (TXSCCMPSDR01.DR.LPL.COM) is submitting SDK changes from site(1DR)
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:50 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Connect: For TXSCCMPSDR01.DR.LPL.COM, logged-on as DR\SCCM_Install
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:51 AM
10932 (0x2AB4)
RDC:Successfully created package signature file from \\?\E:\SMSPKGSIG\1DR00010.5 to \\TXSCCMPSDR01.DR.LPL.COM\SMSSIG$\1DR00010.5.tar
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
Setting permissions on file MSWNET:["SMS_SITE=1DR"]\\TXSCCMPSDR01.DR.LPL.COM\SMSSIG$\1DR00010.5.tar.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=10932 GMTDATE=Sat Dec 14 19:01:52.367 2013 ISTR0="1DR00010" ISTR1="["Display=\\TXSCCMPSDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMPSDR01.DR.LPL.COM\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="1DR00010" AID1=404 AVAL1="["Display=\\TXSCCMPSDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMPSDR01.DR.LPL.COM\"
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
Successfully created/updated the package server in the data source
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM       10932 (0x2AB4)
Performing cleanup prior to returning.   SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
DPConnection::Disconnect: For TXSCCMPSDR01.DR.LPL.COM, reverted to SYSTEM context
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
10932 (0x2AB4)
DP thread with array index 0 ended.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
DP thread with thread handle 0000000000001920 and thread ID 10932 ended.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
Created policy provider trigger for ID 1DR00010 SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
Package 1DR00010 does not have a preferred sender.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
Package 1DR00010 is new or has changed, replicating to all applicable sites.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=1DR00010, Version=5, Status=2301
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:52 AM
6348 (0x18CC)
StoredPkgVersion (5) of package 1DR00010. StoredPkgVersion in database is 5.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
SourceVersion (5) of package 1DR00010. SourceVersion in database is 5.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=6348 GMTDATE=Sat Dec 14 19:01:53.052 2013 ISTR0="FileZilla" ISTR1="1DR00010" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="1DR00010"
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
Exiting package processing thread.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:53 AM
6348 (0x18CC)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
Sleep 2402 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
Sleep 2402 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:01:58 AM
1916 (0x077C)
Processing PullDP response 1DR - ["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM
3872 (0x0F20)
    Package 1DR00010, Version 5(5), ActionState 32, PkgStatus 0, ActionData =
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM
3872 (0x0F20)
STATMSG: ID=9509 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=3872 GMTDATE=Sat Dec 14 19:02:56.793 2013 ISTR0="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
ISTR1="1DR00010" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="1DR00010" AID1=404 AVAL1="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
AID2=410 AVAL2="5"     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM
3872 (0x0F20)
Successfully processed PullDP response file E:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\72057594037927970.PUL
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:02:56 AM       3872 (0x0F20)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
Sleep 2339 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:01 AM
1916 (0x077C)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
Sleep 2334 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:03:06 AM
1916 (0x077C)
Processing PullDP response 1DR - ["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
    Package 1DR00010, Version 5(5), ActionState 1, PkgStatus 0, ActionData =
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
Successfully updated the package server status for ["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\ for package 1DR00010, Status 3
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TXSCCMPSDR01.DR.LPL.COM SITE=1DR PID=2948 TID=3872 GMTDATE=Sat Dec 14 19:05:22.316 2013 ISTR0="1DR00010" ISTR1="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="1DR00010" AID1=404 AVAL1="["Display=\\TXSCCMDPDR01.DR.LPL.COM\"]MSWNET:["SMS_SITE=1DR"]\\TXSCCMDPDR01.DR.LPL.COM\"
AID2=410 AVAL2="5"     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM
3872 (0x0F20)
Successfully processed PullDP response file E:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\72057594037927970.PUL
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:22 AM       3872 (0x0F20)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00005 is 12/14/2013 11:42:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00009 is 12/14/2013 10:02:17 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00009 is 12/15/2013 9:57:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR0000E is 12/14/2013 10:36:14 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR0000E is 12/15/2013 10:33:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The last source update time for pkg 1DR00010 is 12/14/2013 11:01:36 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/15/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
Sleep 2193 seconds...     SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:27 AM
1916 (0x077C)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
3992 (0x0F98)
Used 0 out of 7 allowed processing threads.
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The last source update time for pkg 1DR00002 is 12/13/2013 11:47:34 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The next start time for pkg 1DR00002 is 12/14/2013 11:47:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The last source update time for pkg 1DR00005 is 12/13/2013 11:42:39 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/14/2013 11:05:32 AM
1916 (0x077C)
The next start time for pkg 1DR00010 is 12/16/2013 10:54:00 AM Pacific Standard Time
SMS_DISTRIBUTION_MANAGER
12/16/2013 4:45:26 AM 3392 (0x0D40)
Sleep 3600 seconds...     SMS_DISTRIBUTION_MANAGER
12/16/2013 4:45:26 AM 3392 (0x0D40)
Sleep 30 minutes...
SMS_DISTRIBUTION_MANAGER
12/16/2013 5:15:29 AM 3804 (0x0EDC)
Thanks,
Mark

Can I use one Apple TV unit to distribute content to two TV's?

Can I use one Apple TV unit to distribute content to two TV's? If so, how?
I want to be able to purchase movies off of the iTunes store on both TV's and to display photos and listen to music.
Thank you for looking.

Apple TV is designed to display content on a single TV only. Although it has component and HDMI outputs they are not independent and, as has been pointed out already, HDMI will take precedence over the component video.
You will need two Apple TVs, one for each TV, and you can then sync both with one computer either with the same content or with different content selected from a common library in iTunes..
Hope this helps.

Issues distributing packages and receiving Win32 Error = 0

Within the last month or so, we've been experiencing issues distributing various packages to our DP's. There doesn't seem to be any rhyme or reason to it; it can be any combination of packages and DP's.
We've noticed that just before the Win32 error occurs, the following 4 lines usually precede the error:
UpdateStagedFile failed; 0x80070040
UpdateStagedFolderRdc failed; 0x80070040
UpdateStagedFolderRdc failed; 0x80070040
UpdateStagedFolderRdcW failed; 0x80070040
We've had an open ticket with MS for over a week now, but there hasn't been any progress.
Any light you guys could shed on this would be greatly appreciated!

This is a known issue for SCCM 2012. A official fix will be released in the near future. If you want to test instantly, contact CSS to open a case to get a test fix.
There is a KB for this issue (English not available currently)
http://support.microsoft.com/kb/2927111/fr
Juke Chou
TechNet Community Support

Does "Distribute content" on the right click menu for a OSD Task sequence also REDISTRIBUTE packages?

I have a task sequence with quite a few packages that have already been distributed. But that same task sequence has far more that have never been distributed.
When you Right click a SCCM OSD Task sequence and select "Distribute Content", does it also redistribute content that's already been distributed to existing DP's, or just the packages that have never been distributed?

Hi,
You can only select DP's that don't have the Packages required by the Task Seqeunce so no you cannot use it to update the DP's
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Distribute content failed on sccm 2012

Hello all,
As part of OS deployment, I first did a 'build and capture' a Windows 2008 x64 bit image (.wim) and saved it as part of a shared folder (with full permissions). Next, I wanted to create a 'Operating System Images' under 'Software Library' and was successfully
able to add the .wim image previously created. Next, I wanted to 'Distribute content' to Distribution Point (DP) which happens to be the same server as my Site server and where my 'shared' folder is.
As part of this 'Distribute content' when I check the 'content status' under Monitoring, I see the status in 'RED' (Failed). I checked the 'more details' on the error status and found this:
Can anyone help me understand what is missing and what needs to be done. I'm also going through documentation to troubleshoot this. thanks

Hi,
Have you configure the machine account(site server machine) to at least Read permission?
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Difference between "Distribute Content" and "Update Distribution Points"

Hi,
Can someone clarify this for me, I need to redistribute a package to all my distributions points. Should select distribute content and then select the DP's or should I just use the option "Update Distribution Points" to redistribute? TIA

Yes. Once content has been distributed you can not "Distribute Content" again to the same DP. However, you do have another option, go to the properties of the DP, "Content" tab, find the package in question and conduct a re-distribute.
This approach does not increase the versioning of the content whereas "Update Distribution Points" does.
P.S. If you have not read it yet, here is a great
article about content monitoring and validation.
-Tony

Issues distributing large content to pull DPs

I am having issues trying to distribute big files to PULL DPs. All other packages are going through fine. But when I try to ditribute wim files over 4Gb, they never start downloading. The pull site shows a bits.tmp stub file the size of
the actual file. The dataTransferService.log shows ErrorCode 0x80004005.
I initially thought it might be because my pull dp is running on a win2k3 server (using iis 6), but I tried distributing to a test windows 7 pull dp setup and got the same result. WAIK tools for win7 has been installed on the pullDP and its proper
DLLs are in the system32 folder.
I have been able to distribute wim file of roughly 3.7Gb and lower but nothing over that to pull DPs. If I make these regular DPs instead of pull DPs, everyone works fine. This and the fact that all other packages are working fine tells me permissions
and boundaries are not the issue. WebDav authoring rule is set to allow read to all content to all users as well.
My site server is running SCCM 2012 R2 with CU1 running on win2008 R2 (so iis 7.5) and I updated the client on my pull DP as well.
Bitsadmin does not give me much more to work on. State: Transient_error with no progress on byte count. error code : 0x80004005 Unspecified error and error context: 0x00000005 the error occurred while the remote file was being processed.
I have also modified the applicationHost.config file to allow all types of file extentions in the requestFiltering section, on the remote chance this was blocking somehow. This type of issue seems to creep up sometime during the transfer, not before.
One other test I made was to distribute iso files as packages instead of wim files under operating system images. I had the same results with large iso files as I did with wim files.
Things seem to point at some weird type of 4Gb package limit for a pull DP. Either an issue with settings on my site server or with the CCM client itself.
I am running out of ideas and was wondering if anyone has had this issue and has resolved it.

This is a known issue for SCCM 2012. A official fix will be released in the near future. If you want to test instantly, contact CSS to open a case to get a test fix.
There is a KB for this issue (English not available currently)
http://support.microsoft.com/kb/2927111/fr
Juke Chou
TechNet Community Support

Unable to get the file system information for: \\****servername\E$\; error = 64 Unable to distribute content to DP

One of our DPs has stopped loading content.
I've research for quite a bit and cannot find a clear cut reason to this. This server only has a DP role, I verified sharing permissions, all looked good. This DP has been running just fine for the last year or so and all sudden it will no longer load
packages. The disk drive is still present I can still reach the hidden share \\servername.com\E$
Verified that the SMSSIG$ folder is there and the last entry is from 4/23/2015
SCCM 2012 R2
OS 2008 R2 Standard
Any help is greatly appreciated!
Here's a snipit from the distmgr.log
Start updating the package on server ["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\...
Attempting to add or update a package on a distribution point.
Will wait for 1 threads to end.
Thread Handle = 0000000000001E48
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=***.com SITE=1AB PID=2472 TID=8252 GMTDATE=Thu Apr 30 19:12:01.972 2015 ISTR0="SYSMGMT Source" ISTR1="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00087" AID1=404 AVAL1="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
SMS_DISTRIBUTION_MANAGER 4/30/2015 2:12:01 PM
8252 (0x203C)
The current user context will be used for connecting to ["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\.
Successfully made a network connection to \\*****.com\ADMIN$.
Ignoring drive \\*****.com\C$\. File \\*****.com\C$\NO_SMS_ON_DRIVE.SMS exists.
Unable to get the file system information for: \\*****.com\E$\; error = 64.
Failed to find a valid drive on the distribution point ["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\
Cannot find or create the signature share.
STATMSG: ID=2324 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccmprdpr1sec2.mmm.com SITE=1AB PID=2472 TID=8252 GMTDATE=Thu Apr 30 19:12:55.206 2015 ISTR0="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
ISTR1="CAS00087" ISTR2="" ISTR3="30" ISTR4="94" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00087" AID1=404 AVAL1="["Display=\\*****.com\"]MSWNET:["SMS_SITE=1AB"]\\*****.com\"
Error occurred. Performing error cleanup prior to returning.
Cancelling network connection to \\*****.com\ADMIN$.

Error 64 is being returned which is simply "the network name is no longer available".
There can be a number of reasons for this from SMB compatibility issues (2003 servers wont support SMB2), to the expected and actual computer name of the boxes don't match (tries to authenticate with server.tld.com when the actual name is srv-01.tld.com and
you just put a C-name in). I'd start from the top: Try opening said share from the Primary Site server as that's the box doing the work. Verify the IP and computer name is legit and that no one has played ACL games between the two systems (remember
RPC only initiates/listens on port 135 but established connections are up in the dynamic port range).
At the end of the day it's an issues "underneath" SCCM, and not an SCCM problem specifically.

Disappearing Issues in Content Viewer!!!

Anyone else run into this?
I have shared a number of individual folios to a single Adobe email address.
In this way, I can log into Adobe Content Viewer with that Adobe email address to gain access to all the publications from within a single app.
While demonstrating DPS in front of a client (of course!) a number of the thumbnails of available issues simply disappeared.
They were there..then boom just went away.
Horrifying to say the least. I moved on in our presentation.
Then I got back to the office launched the app and the Library updated and there they were again.
Is this server related, app related, related to the fact that the issues were shared and not built under the Adobe email address?
Thoughts?

We have this occur from time to time. Even though the folios have been downloaded sometimes they won't show up on the Adobe Content Viewer home screen. Sometimes they come back in a few seconds, sometimes they don't. If you quit the app and open it again, or sign out and back in, it will probably show them again. It likely has something to do with the library updating/synching. We've mainly been using the Android version of the content viewer on Xooms and our client has noticed this occasionally as well on their Xooms. Since the folios always seem to come back eventually no one is freaking out about it, but it does make the Adobe Content Viewer seem buggy for the user. I'm assuming this doesn't happen with a professional or enterprise account.
Andrew

Problems distributing content to DP's after KB2910552 hotfix

I’m having a major problem sending packages/applications to distribution points after installing the KB2910552 hotfix
to our SCCM01 server, which is our CAS. I performed the install, ignoring the warning of possibly needing to do a restart first (regretting it now). The installation completed successfully. Even checked the log to make sure. From there, I rebooted the CAS.
After it came up, I went into the Admin Console and saw it created the packages for deployment. I tried to distribute them to my 3 distribution points. All 3 failed. Here's the content status description:
Distribution Manager failed to access the source directory.
Possible cause: Ditribution Manager does not have sufficient rights to the source directory.Possible cause: There is not enough disk space available on the site server.
Here's the errors from the distrmgr.log:
Cannot create \\SCCM01.domain.com\V$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.].
Cannot create the content library storage directory \\SCCM01.domain.com\V$\SCCMContentLib, use the default directory.
Failed to create share – SCCMContentLib$ on server SCCM01.domain.com . Error = 2116
GetContentLibLocation() failed
Failed to get the content library path on server SCCM01.domain.com
I noticed the V$. I have no idea why that's even there. There is no share drive using V. I have everything on an E: drive. I went to the following reg keys:
HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives
HKLM\Software\Microsoft\SMS\DP\UsablePackageShareDrives
...and they show V as the drive letter.
Again, I have no idea why??? In Admin Console, the DP role for that server has "E" for the drive.
Will removing and re-adding the DP role and re-adding it with the same drive letters resolve the issues? I have major concerns though...
1) SCCM01 is our CAS, will it remove everything we have distributed to it?
2) Will we have to re-redistribute all the packages, applications…etc, to that DP again?
I would really appreciate any help with this. I've already spent 6 hours trying to resolve this. THANK YOU!

I apologize for the confusion. I'm kind of "taking over" after this was already in place by someone else. I'm jumping in the fire, per-say. Maybe it wasn't set up correctly from the beginning. We're still fairly new to this beast.
Here's a screen cap of our servers:
I can tell you this...All three have the Distribution Point site system role. SCCM01 has "E" as the drive. Content Library and Package Share Library are "1". I do notice that the SCCMContentLib folder doesn't exist on the E drive.
I went ahead and just removed the DP site system role from SCCM01 and recreated it according to how it was set up originally. I still get the same errors in the distmgr.log. I cannot figure out why it keeps referencing V$. There is no V drive on the SCCM01
server.

Sharepoint error - Search Issue - The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1).

i see this error everywhere - In ULS logs, on site. On the site > Site settings > search keywords; I see this -
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>IIS 7.0 Detailed Error - 500.19 - Internal Server Error</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 40px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px; border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696; border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;'.
I am facing issues in searching, my managed metadata service is not running, search results page throws internal error. Any Idea why this above error comes.
P.S: We use windows authentication in our environment.

Hi IMSunny,
It seems you have solved this issue based on your another post.
http://social.technet.microsoft.com/Forums/en-US/aa468ab0-1242-4ba8-97ea-1a3eb0c525c0/search-results-page-throws-internal-server-error?forum=sharepointgeneralprevious
Thanks
Daniel Yang
TechNet Community Support

How to eliminate or customise the White preloader with Edge content in DPS apps.

I am looking for a possible solution with the White Preloader Page when creating an IPA via Indesign.
The content is fully created in Adobe Edge Animate, then its published HTML is placed via the Indesign Folio Overlay. Then via the DPS APP BUILDER converted to an IPA, this is working fantastic !!
.. but..
When the app is launched on the iPad there is always, always the white preload screen with the spinning wheel for a few instances.
Tried to customize the preloader screen in Edge but the White screen will show first, then the custum preload screen and then the content.
Also tried to modify directly the HTML but no luck, there is always the White screen with the spinning wheel.
Somebody got any idea how to hide this White Screen ? Or how to customise this ?
Thank you for any suggestion.

I'm not sure what you mean by IPA but are you using the HTML files from Edge or the .oam file. You know that the .oam file is much easier to use than the HTML files from Edge when being used in DPS. You know you can create a poster image directly in Edge as well that is not white. You can also take the posterimage.png file from the image folder and bring it into Photoshop and delete everything and save it as a transparent .png and replace it. That way what ever is behind the animating shows through. Just a suggestion.

Issues distributing content to DPs

Similar Messages

Maybe you are looking for