Distribution Point No Longer Appearing in Console

Here is the scenario.
I had a DP which was no longer accepting packages,  I examined distmgr.log and I noticed WMI errors and access denied errors connecting to the DP.
I then removed the DP role from the Console.  On the Server I then rebuilt WMI.  After that I then Re-added the DP role to the user and selected the DP to Install VIA my Service account instead of computer account.
Distmgr.log shows that the connection was now successful and files have been re-uploaded. 
Here is my problem,  the server is not appearing as a DP in the console now.  Meaning that I cannot join it to Distribution groups,  nor distribute packages and applications to it.       Has anyone
ever come across a DP that does not show as  DP in the console?  I am baffled!

I'd wait for some hours first. I've also read here in the forums that rebooting the site server has fixed it. 
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

  • Distribution Point migration status in CM12 console

    Hi,
    We are using sccm 2012 r2 cu2. we are in middle of migration.
    We have in sccm 2007 under secondary site server name assd1 it contain MP and DP role.
    Under ASSd1 server i was created one of the distribution point server and copied all the package to the new server assd2.
    I created this new distribution point last week.
    Today I gathered data from sccm 2007 to sccm2012.
    Previously I did the same almost 5 servers and after sccm2012 administration-->under site hierarchy--> shared distribution point it shows. after that i will migrate to sccm2012 DP
    but this server not showing. but when i saw migctrl.log i can see the log
     The DP assd2.xxx.org is eligible for upgrade 
    but not showing under administration-->under site hierarchy--> shared distribution 

    Issue got resolved..

  • SCCM 2007 Won't remove Distribution Points in Site Status

    I'm working SCCM 2007 and have removed  some orphaned Distribution Points by going through and removing any application assigned to them and then removing the roles under the Site Systems Folder.
    The Systems then disappeared from under Site Systems but when I look under Site Status, they're still appearing in the list there and I have no option to delete them.
    I've tried following this link (http://myitforum.com/myitforumwp/2012/02/10/removing-old-orphaned-site-systems-from-the-sms-and-configmgr-2007-database/) and changing their replication field from a 0 to -1 which removes them temporarily but they always return
    into the Site Status.
    I can't see them anywhere else in the console, they're definitely not sited under Site Systems so I'm a bit stuck and have 3 sites saying they're in a Critical State in Site Status because the Orphaned Distribution Points are still appearing there and I
    can't see how to remove them.
    To clarify, I removed the orphaned Distribution points over a week ago so I doubt it's something like waiting for the system to e them.  I've tried rebooting the SCCM server and this has made no difference
    My list of servers under Site Systems;  
    My Servers in Site Status;

    Execute the following command on the database
    Delete from DPinfo where server name like '%DPName%'
    It is completely unsupported to delete anything from the CM07 database. Before doing this you should contact CSS directly for support and ONLY with their guidance should you perform this task.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • SCCM - Branch Distribution point and Management point on the same server

    Hi All,
    Would like to know if any other SCCM roles like management point , distribution can be installed on the same server on which a branch distribution point is installed?
    Rgs,

    Hi,
    Branch Distribution Points no longer exist in Configuration Manager 2012 and above.
    I'm assuming you want to install additional roles on an existing server that is currently only acting as a Distribution Point and the answer is yes, this is possible, but it depends on which other roles you want to install and there will probably be some
    prerequisites needed.
    Can you elaborate on which roles you are considering installing? 
    Steven Hodson | http://www.stevenhodson.com | @_hodders

  • Distribution Point Offline - how long before SCCM client connects to alternative DP?

    Hi, I'm doing some testing on my SCCM 2012 setup and have been attempting to test distribution point resiliency and fall-back.
    I have a single primary site with two distribution points. One is in the main datacentre and is in the same boundary group as the clients and tagged as fast connection. The 2nd DP is in the DR datacentre, in a separate boundary group (no client subnets are
    in this group) and the distribution point has the allow failback checked.  Both DP's have the same content.
    After shutting down/taking offline the main distribution point, I've then kicked of an install of a package on a W7 client. It attempts to download and stays in that state for as long as I leave it. Looking in the logs I can see both DP's returned to
    the client (the DR tagged as REMOTE), it then attempts to connect to the main DP and just keeps retrying over and over.
    I thought if it couldn't connect to the main DP it would then failback to the DR DP, but it doesn't appear to do this. Is there a timeout on this before it would fail back?
    I'm also currently  trying adding the DR DP to the main boundary group and tagging the connection as slow so the main DP would still be used first. Again both DP's are returned to the client when installing software and the client attempts to connect
    to the main DP over and over without using the DR DP which is online.
    Is this normal behaviour or do I have a configuration issue?
    Appreciate your help.
    Carl

    Hi, just to update on this thread, I raised a support call with Microsoft and the end result is that SCCM2012 clients wont fall back to an alternative DP where a DP is offline. The fall back is only for when content isn't on a DP. The 8hr timeout doesn't
    appear to be in affect anymore.
    What I have managed to get to work and test out is removing our production DP (also primary site server) from the production content boundary group, then clients will fall back to the DR DP as this is the only other DP available with content.
    I've managed to perform the update to remove the site server from the boundary group while the primary site server is offline, by using a PowerShell script to connect to the SCCM provider on the DR site server (DP/MP/SUP) to perform the update as our site
    database is off-box. This works well and the changes replicate to the SQL replica in DR that the DR MP uses and when clients failover to the DR MP they then begin using the DR DP and packages can be installed etc.
    How funny, I just fixed this at a Client this week.
    This is default client behavior as MS CSS probably told you, the client thinks the Distribution Point is coming back online soon so it waits, for good reasons. For some reason I keep thinking "7 days" not 8 hours, but maybe wrong.
    I have a work around for this, it just requires a change to the Distribution Points DNS record. Head to the DNS server, find the record for the Distribution Point that is down, change the IP address to a different member server IP address, this will cause
    the client, when it flushes it's DNS cache, to get an updated DNS record for the Distribution Point and it will try to connect to the Distribution Point using the changed IP address, which then induces what the client thinks is a severe error which makes it
    go to the next Distribution Point in the list it got from the Management Point. Once you've recovered the Distribution Point and it is back online, change it's IP address back in DNS or just let the Distribution Point update its own DNS record when it boots
    up (if configured to do so) and viola, you are back in business.
    Test, test and test again before ever putting something from "the web" into your production environment. I just implemented this at a client to solve their issues with their DR procedure.
    Rob Marshall | UK | My Blog |
    WMUG |
    File CM12 Feedback |
    CM12 Docs |
    CM12 Release Notes

  • How long until Deleted Content from Distribution Point frees disk space?

    Hopefully this is an easy question for you guys with more experience with the product.
    Yesterday, I created a new software distribution group for Office 2013 SP1, both 32 and 64bit.   I didn't really understand at the time that it was going to download nearly 8GB into my /sources folder...which is where I save my package contents.  I
    would have not expected this download to exceed approx 2GB.
    Since I indicated that it should also be distributed to my Distribution point, which is the same server, it also increased the disk usage in the /sccmcontentlib folder, as well as increasing the amount of space used in my SQLDatabase which is on the same
    drive.  It was never deployed to anything.
    Since I'm not yet ready to deploy this update to clients, but have a few others things to do instead, I wanted to delete the content from the distribution point to free up some disk space.
    I went into Software Library, Deployment Packages, went to properties of my Office2012_SP1 deployment, went to Content Locations, picked my single distribution point from the list, and chose Remove.
    However, no disk space was cleared on my drive.   I've still got 6GB free on my 120GB volume, so I'm not out of space.    
    Is this something where a scheduled job will come through and process this removal and free up the disk space?   Or is there a way to kick of the process manually?    

    It was never setup as an application. 
    It was a Windows Update, which was added to a software update group.  Then, I went to the software update group and right clicked and chose Download.  I created a new deployment package, and then distributed the content to one of my distribution
    point.
    By doing that, I understood that it would create the D:\sources\WindowsUpdates\Office2013_SP1 folder and put the deployment files there.  And I also see that because that content was set to a distribution point, it copied it there into the ContentLib.
    So, I wanted to remove the data from ContentLib, so I went to the Deployment Package, went to Content locations and removed my Distribution Point.   
    So, are you saying that in order to remove the ContentLib, that I have to remove the entire Deployment Package?   
    I thought by removing the Content Location it would remove it from the DP, and if I later wanted to add it back ,I could go back to the Deployment Package, go into Properties and add a DP back to the content location.

  • 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

  • Distribution Point install failure

    Hi all,
    In all our company uses 8 distribution point and the majority are 2008 R2 domain controllers.
    About two days ago I have done an inplace upgrade on one server to 2012 R2.
    The upgrade went mostly without a hitch except for the SCCM DP.
    The error that I was getting was "access denied" or something along those lines when the site server was attempting to distribute content.
    So I have tried a lot of things so far to the point where I decided to remove the distribution point and start over. No Joy...
    I am getting an error on the distribution point in the SCCM console stating "Failed to verify the disk drive". when looking further into the distmgr.log, nothing makes sense to me. please see the below log.
    ~Sleep 60 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:35.310-600><thread=5576 (0x15C8)>
    ~Sleep 60 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:44.178-600><thread=5576 (0x15C8)>
    Upgrading DP with ID 18. Thread 0x1e1c. Used 1 threads out of 5.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.248-600><thread=5868 (0x16EC)>
    ~Processing 18.INS  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.253-600><thread=7708 (0x1E1C)>
    ~DPID 18 - NAL Path ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ , ServerName = [SERVER NAME HERE], DPDrive = E:, IsMulticast = 0, PXE = 0, RemoveWDS = 0  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
    22:20:59.263-600><thread=7708 (0x1E1C)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.255-600><thread=5868 (0x16EC)>
    ~Created policy provider trigger for ID 18  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.308-600><thread=5860 (0x16E4)>
    DPConnection::Connect: For [SERVER NAME HERE], logged-on as rondo\sccmpush~  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:02.712-600><thread=7708 (0x1E1C)>
    Found notification for package 'RDO00002'  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.263-600><thread=5576 (0x15C8)>
    Found notification for package 'RDO00003'  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.268-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.302-600><thread=5868 (0x16EC)>
    ~Package Thread Limit: 3  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.310-600><thread=5576 (0x15C8)>
    ~Per package Thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.315-600><thread=5576 (0x15C8)>
    ~Retry interval: 30  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.320-600><thread=5576 (0x15C8)>
    ~DP upgrade thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.325-600><thread=5576 (0x15C8)>
    ~DP upgrade retry interval: 20  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.330-600><thread=5576 (0x15C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.360-600><thread=5576 (0x15C8)>
    Failed to find a valid drive on the distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.541-600><thread=7708 (0x1E1C)>
    ~Starting package processing thread, thread ID = 0x88 (136)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.919-600><thread=5576 (0x15C8)>
    DPConnection::Disconnect: For [SERVER NAME HERE], reverted to SYSTEM context~  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.131-600><thread=7708 (0x1E1C)>
    user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine ([SITE SERVER NAME HERE]) is submitting SDK changes from site(RDO)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.348-600><thread=7708 (0x1E1C)>
    ~Starting package processing thread, thread ID = 0x2B78 (11128)  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.426-600><thread=5576 (0x15C8)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.434-600><thread=5576 (0x15C8)>
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=11128
    (0x2B78)>
    ~Retrying package RDO00003  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.450-600><thread=11128 (0x2B78)>
    No action specified for the package RDO00003.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=11128 (0x2B78)>
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00002" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=136
    (0x88)>
    ~Retrying package RDO00002  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.469-600><thread=136 (0x88)>
    No action specified for the package RDO00002.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.476-600><thread=136 (0x88)>
    Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.494-600><thread=136 (0x88)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=136 (0x88)>
    Thread Handle = 00000000000035C0  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.507-600><thread=136 (0x88)>
    Start adding package to server ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.473-600><thread=11128 (0x2B78)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=9852 (0x267C)>
    The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.538-600><thread=9852 (0x267C)>
    Error occurred. Performing error cleanup prior to returning.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.546-600><thread=9852 (0x267C)>
    ~Failed to install DP files on the remote DP. Error code = 15  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=7708 (0x1E1C)>
    ~Drive E: is not valid. Error = 15  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.566-600><thread=7708 (0x1E1C)>
    STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=7708 GMTDATE=Thu May 01 12:21:05.573 2014 ISTR0="["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER
    NAME HERE]\" ISTR1="[SERVER NAME HERE]" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\[SERVER
    NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.573-600><thread=7708 (0x1E1C)>
    ~Will try again after 20 mins ...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.582-600><thread=7708 (0x1E1C)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=11128 (0x2B78)>
    Thread Handle = 00000000000029C8  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.612-600><thread=11128 (0x2B78)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=10028 (0x272C)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.124-600><thread=136 (0x88)>
    DP thread with thread handle 00000000000035C0 and thread ID 9852 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.131-600><thread=136 (0x88)>
    The distribution point ["Display=\\[SERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[SERVER NAME HERE]\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.136-600><thread=10028 (0x272C)>
    Error occurred. Performing error cleanup prior to returning.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.164-600><thread=10028 (0x272C)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.198-600><thread=11128 (0x2B78)>
    DP thread with thread handle 00000000000029C8 and thread ID 10028 ended.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.205-600><thread=11128 (0x2B78)>
    ~Package RDO00002 does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.645-600><thread=136 (0x88)>
    The package and/or program properties for package RDO00002 have not changed,  need to determine which site(s) need updated package info.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.653-600><thread=136 (0x88)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00002, Version=3, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.659-600><thread=136 (0x88)>
    ~StoredPkgVersion (3) of package RDO00002. StoredPkgVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.687-600><thread=136 (0x88)>
    ~SourceVersion (3) of package RDO00002. SourceVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.694-600><thread=136 (0x88)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:06.700 2014 ISTR0="Configuration Manager Client Package" ISTR1="RDO00002"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.700-600><thread=136
    (0x88)>
    ~Failed to process package RDO00002 after 33 retries, will retry 67 more times  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.711-600><thread=136 (0x88)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.720-600><thread=136 (0x88)>
    ~Package RDO00003 does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.721-600><thread=11128 (0x2B78)>
    The package and/or program properties for package RDO00003 have not changed,  need to determine which site(s) need updated package info.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.749-600><thread=11128 (0x2B78)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00003, Version=1, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.757-600><thread=11128 (0x2B78)>
    ~StoredPkgVersion (1) of package RDO00003. StoredPkgVersion in database is 1.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.784-600><thread=11128 (0x2B78)>
    ~SourceVersion (1) of package RDO00003. SourceVersion in database is 1.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.790-600><thread=11128 (0x2B78)>
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[SITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:06.797 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="RDO00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003"  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014
    22:21:06.797-600><thread=11128 (0x2B78)>
    ~Failed to process package RDO00003 after 33 retries, will retry 67 more times  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.806-600><thread=11128 (0x2B78)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.814-600><thread=11128 (0x2B78)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:09.311-600><thread=5868 (0x16EC)>
    ~Package Thread Limit: 3  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.463-600><thread=5576 (0x15C8)>
    ~Per package Thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.469-600><thread=5576 (0x15C8)>
    ~Retry interval: 30  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.476-600><thread=5576 (0x15C8)>
    ~DP upgrade thread Limit: 5  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.482-600><thread=5576 (0x15C8)>
    ~DP upgrade retry interval: 20  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.488-600><thread=5576 (0x15C8)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.509-600><thread=5576 (0x15C8)>
    ~Sleep 1826 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.517-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:14.320-600><thread=5868 (0x16EC)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.544-600><thread=5576 (0x15C8)>
    ~Sleep 1821 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.553-600><thread=5576 (0x15C8)>
    Sleep 20 minutes...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:19.332-600><thread=5868 (0x16EC)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.581-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.589-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.732-600><thread=5576 (0x15C8)>
    ~Sleep 1816 seconds...  $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.872-600><thread=5576 (0x15C8)>
    So I have two questions,
    How can I fix this and how do I prevent it from happening to the remainder?
    Thank you all in advance.
    Daniel.

    The server does not appear at all
    You really need to give more information so we can help you.
    What about the logs, are you getting the same errors after making all the changes? please upload the full log to SkyDrive or any other place. 
    Did you reboot this DP\DC?
    Can you successfully ping from the primary to DP and back?
    Do you have access from primary to C$ on that DP?
    What account did you choose for installation?
    Did you choose to install IIS?
    If IIS was installed, try to remove it and let DP installation install it automatically.
    Confirm that PowerShell 3.0 is installed.
    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
    Hi Idan,
    I will go through and reply to each of the suggestions you have made below;
    1. The log that was attached was the full log. I cleared the log prior to setting up the DP and copied the contents into this forum after it has stopped.
    2. Yes I had rebooted, Many times.
    3. Yes I can successfully ping either way.
    4. Yes I can access the C$ share on the DP from the Primary
    5. I have tried both the PC account and a service account that is part of the domain admins group and also added to the local admins via a net command
    6. Yes I did choose to install IIS and I had already tried uninstalling IIS and running the install again.
    7. as above
    8. Yes Powershell 3.0 is installed
    PS C:\Users\admindg> $PSVersionTable
    Name                           Value
    PSVersion                      4.0
    WSManStackVersion              3.0
    SerializationVersion           1.1.0.1
    CLRVersion                     4.0.30319.34014
    BuildVersion                   6.3.9600.16394
    PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}
    PSRemotingProtocolVersion      2.2
    Thank you for all your suggestions and I hope that the information that I have provided is sufficient to draw a better picture of our environment.
    Regards,
    Daniel

  • SCCM 2012 R2 Pull DP fails, works on Update Distribution Points

    I'm seeing some odd behavior out of a DP, in particular around driver packages. The system is running SCCM 2012 R2.  When I create the driver package I deploy it to the DP on the Primary Site Server. That usually happens in a couple of minutes or less.
    I then deploy to a remote DP configured for Pull.  This generates the log entries below in the PullDP.log. Even waiting hours doesn't seem to help. If I do a Update Distribution Points for the package, it runs successfully.  I know
    there was something similar fixed in SP1 CU3.
    Intializing DP Monitoring Manager... PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
    Getting site code PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
    Getting DP Cert Type PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
    Getting this DP NALPath PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
    Report state message 0x00000004 to MP PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
    Report Body: <ReportBody><StateMessage MessageTime="20140322004854.000000+000" SerialNumber="1"><Topic ID="ACC0006D" Type="902" IDType="0"/><State ID="4" Criticality="0"/><UserParameters
    Flags="0" Count="3"><Param>ACC0006D</Param><Param>["Display=\\DP.xxxxx.xxx\"]MSWNET:["SMS_SITE=ACC"]\\DP.xxxxx.xxx\</Param><Param>{B187E44B-4BF3-4748-B437-AFF29D679AA3}</Param></UserParameters></StateMessage></ReportBody>
     PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
    CPullDPResponse::ReportPackageState return value 0x00000000. PullDP 3/21/2014 8:48:55 PM 3564 (0x0DEC)
    Start Download  package ACC0006D version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
    Start Download  package ACC00070 version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
    ExecuteJob (1-NotStarted) 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
     Cannot find FileInfo (\\?\E:\SMS_DP$\ACC00070\9A25E477-3C0C-499E-A0C1-65243BDBCBF0.tar), content download failed PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
    CPullDPPkgContJob::ExecuteJob() failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
    State at failure: NotStarted PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
    Content job 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
    Package job has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
    Bob

    We ended up changing the DP back to a standard distribution point.  That allowed the driver package to distribute successfully.  so as a result I can't access the logs any longer.
    I should note for anyone who goes searching for this that we had problems with every one of our driver packages.  As I dug into it I found the contents, it looked like for some reason that it wasn't being transferred from the download location into
    the final DP distribution location.  It almost looked like SCCM was ignoring driver package types.  I don't know if its a bug or just something quirky about this environment.
    We were hoping to use Pull DP to handle our distributions more effectively, but we've backed off on that because of all the issues we've had with it.  I hate say it, but it appears to be another SCCM 2012 feature that sounds like a good idea, but the
    implementation leaves a lot to be desired.
    Bob

  • Time Capsule Icon No Longer Appears on Desktop

    Two weeks ago I had AT&T U-verse cable, internet, & phone installed. As part of that installation they installed an AT&T router/wireless combination. The ethernet cable that was previously connected to Time Capsule is now connected to the AT&T device. There is no longer any ethernet connection to Time Capsule. The Time Capsule icon still appeared on my desktop and I manually performed back-ups from my Windows applications to Time Capsule. Time Capsule went from displaying a constant green light to displaying a flashing yellow light. That worked for several days. After about a week of that there appeared on my screen a 'wizard' of some sort recognizing the status of Time Capsule. It said this 'wizard' would eliminate the flashing yellow light. I followed the steps through the 'wizard' and at one point the flashing yellow light turned to constant green. There were a few more steps in the 'wizard' and when it was finished the flashing yellow light reappeared. The next time I tried saving files from Windows I could not connect to my w: drive, and the Time Capsule icon no longer appeared on my Mac desktop. I went into Airport Utilities and there is a box checked that should display the icon properly. Any ideas what's happening? How do I restore Time Capsule so I can back-up my files. Thank you.

    Welcome to the discussions!
    I don't have 10.6.1 yet, but have noticed this happens very occasionally on my MacBook Pro, but not on my iMac. Simply resetting Time Machine on my laptop has done the trick.
    Open System Preferences
    Click on Time Machine
    Click your Time Capsule to highlight it
    Click Use for Backups
    If that does not do it then delete the "com.apple.TimeMachine.plist" file. It's located as follows:
    Macintosh HD > Library > Preferences
    Restart your computer
    Then perform the same steps as above to setup Time Machine again.
    The resets will not affect any of your backups.

  • Blank DVDs and CD-Rs No Longer Appear

    Since installing the latest security update for 10.3.9 on my 1.8 Dual Processor PowerMac (yes, I repaired permissions immediately before and after installing the update) blank recordable media no longer appear in Finder or on the Desktop. I am able to use iTunes and apps with the ability to burn to record some things and the discs behave normally, but I can no longer insert a blank disc and copy folders or files to it to burn because it does not appear anywhere on the system. Named blank discs do not come up when I use Search either. These are the same batch of discs I have been using for months with 100% success (Imation brand of DVD-R and +Rs), and like I said, they work fine through certain apps that have a burn function. Seems like a Finder issue to me. Any thoughts?
    When I insert a blank it get this error in Console:
    Apr 25 11:35:57 ####-####-Computer kernel: disk4: media is not formatted.
    My optical drive is a SONY DVD RW DW-U10A
    Here is a list of what I have done in an attempt to resolve the issue:
    -repaired permissions
    -in System Preferences set the action to open Finder when blank discs are inserted (tried changing settings and restarting)
    -used Onyx to clean system and app caches
    -put machine to sleep and woke it (read somewhere this might do it)
    -trashed the finder.plist file
    -used Panther install disc to verify and repair the Volume (says all's good)
    -downloaded the update again and reinstalled
    My three external firewire drives all show up as usual, and USB CF cards mount normally. Recorded DVDs and CD-Rs appear normally.
    In Disk Utility I see the disc icon with the name of the optical drive when there is a blank disc in the drive, but it says under Total Capacity: 0Bytes, and under Write Ability: Read Only (CD-R).
    Any thoughts or ideas on what I could try will be greatly appreciated! I really need to burn some backups!
    Thanks very much,
    Kevan
    15 1Ghz TiBook 1GB RAM: Dual Processor 1.8Ghz PowerMac G5 w/ additional 300GB Maxtor Drive Internal   Mac OS X (10.3.9)   160GB and 300GB externals; 10GB, 40GB, 60GB iPods
    15 1Ghz TiBook 1GB RAM: Dual Processor 1.8Ghz PowerMac G5 w/ additional 300GB Maxtor Drive Internal   Mac OS X (10.3.9)   160GB and 300GB externals; 10GB, 40GB, 60GB iPods

    Alright! I have it fixed using a little deductive reasoning and a post by Roam on another thread. Thanks roam!
    Resetting Launch Services did it. Here's a link on how to do it:
    http://www.thexlab.com/faqs/resetlaunchservices.html#Anchor-Reset-11481

  • .XMP files no longer appear as sidecars--how to clear metadata?

    Photoshop CS2 ver 9.0.2
    Bridge ver 1.0.4.6
    ACR ver 3.7
    eMac G4 800 MHz
    Mac OS X ver 10.4.9
    1 Meg RAM
    12 GB available disk space
    Bridge and Photoshop are set to save metadata in .XMP sidecar files, but sidecar files no longer appear. That is, up till a few days ago, .XMP files appeared when I opened raw files, but no longer. The drop-down menu is still set to save metadata in sidecar files.
    Cannot clear metadata in Bridge. I can select "Camera Raw Defaults" in ACR, but that doesn't clear cropping.
    1) How do I return already-stored metadata to .XMP files?
    2) How do I get PSCS2 to store future metadata as .XMP files?
    3) How do I clear metadata currently stored in ACR/PS database?
    4) What did I do to cause system to store metadata in ACR/PS database despite being set to save in sidecar files?
    Thanks.
    --HC

    Noel,
    Excellent point.  I have no idea.  Maybe this was only working for
    .PSDs/etc. (which contain the metadata embedded in the file itself[,
    right?]).  I may have been deluding myself this whole time.  It's
    possible that it never really worked the way I thought it did to begin with.
    But, more specifically, here's the current question:  If I have this
    file (which is a backup from long ago):
    J:\backup of M90\Documents and Settings\philipt\Application
    Data\Adobe\CameraRaw\Database
    ...assuming that drives are currently mapped (by drive letter) the same
    way they were when that backup was made), can I just replace the current
    file:
    C\Documents and Settings\philipt\Application Data\Adobe\CameraRaw\Database
    ...with the one from J: and expect it to work correctly?
    What's the worst that can happen if I do this?
    BTW, the file on J: is 2,569 Kb; the (new) one on C: is 2,754 Kb.  This
    doesn't seem to bode well, since the old one (J:) should have much, much
    more data in it (assuming that the "Database" file per se is where the
    metadata is stored): the older file has complex,
    multi-tiered data for 10s of 1000s of images.  "??"
    Thanks again for your willingness to help with this!!
    Aloha,
    -pt

  • Advanced option no longer appears in SB Entertainment Center tab

    @Advanced option no longer appears in SB Entertainment Center tabD I recently wanted to watch movie DVD's on my computer. Knowing very little about video/sounds concepts, I installed the ffdshow video/audio decoder (part of the K-Lite Codec package). After several days I was able to watch movie DVD's on my computer, both video and audio using a movie DVD that had Dolby Surround 5.. However, I was unable to hear any sound from my rear speakers, so I began to experiment with different settings.
    At one point in the SB Entertainment Center I clicked on the Entertainment Center tab/Advanced settings, brought up the AC3Filter window and changed one of the settings to Filter merit/Prefer other decoder. Testing this setting resulted in no sound. Now the Advanced settings option also no longer appears when I bring up the Entertainment Center tab so that I can change this setting back to its default.
    How do I get this option back or bring up the AC3Filter window?
    I would appreciate any suggestions you might have. Thank you.
    Sound setup:
    Sound Blaster X-Fi Fatalty FPS
    Logitech Z-5450 Digital 5. [email protected]

    I seem to see that using
    * Firefox Button or Tools -> Options -> | Advanced | ->[-Offline Storage-]
    *see [[Options window - Advanced panel#w_network-tab]]_network-tab
    Possibly something is interfering
    * try in Firefox's [[safe mode]]
    ** do not make changes on the first window, just click on continue
    ** use the default theme
    ** it may also help to disable all plugins
    Note <br/>
    Firefox 5 is no longer supported and not considered secure. It would be recommended you use the current public release which is Firefox 7.0.1
    * see [[updating firefox]]

  • SCCM 2012 R2 - Distribution Point

    Hello,
    I have a SCCM environment configured only one server to handle all the Role MP, DP, etc..
    SQL Server 2012 is Remotely installed.
    I am using Windows server 2012 R2 Standard with installed SCCM 2012 R2.
    I am using VMware vSphere 5.1
    I want to use SCCM 2012 R2 for PXE boot to deploy Windows 7 Enterprise 32 bit and 64 bit.
    But I am unable to install the Windows 7 Enterprise 32 bit and 64 bit through PXE Boot.
    When I am trying to install on VM this error message is:
    Downloaded WDSNBP from 10.100.1.178
    Pending request ID : 31
    Message from Administrator:
    Configuration Manager is looking for Policy.
    Contacting Server 10.100.1.178
    PXE Boot aborted. Booting to next device...
    PXE-MOF: Existing Intel PXE ROM.
    The operating system was not found. Try Disconnecting.......
    And 2nd thing when I am selecting Packages in SCCM 2012 R2 Console and right clicking on User State Migration Tool for Windows 8.1 and Selecting Distribute Content and After clicking next when its asking for Specify the Content destination its now showing
    any Distribution Point.
    Can someone help me please to fix this issue.
    Thanks a lot and help/advise much appreciated.

    Contacting Server 10.100.1.178
    PXE Boot aborted. Booting to next device...
    This indicates that there's no task sequence deployed to the computer that was PXE booted.
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 R2 - Distribution Point untrusted domain - Not acknowledging Network Access Account (FYI)

    Hello!
    Scenario
    Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
    The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
    DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
    errors indicate that this software can'tbe downloaded.
    In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
    Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
    implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
    Problem
    The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
    The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
    A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
    were reinstalled. A fresh install didn't detect the NAA.
    Solution
    After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
    the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
    Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
    domains aren't approved automatically (by default).
    In this case something as simple as an Approving the client fixed these issues. 
    The DataTransferService.log highlights the issue:
    <![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
    context="" type="1" thread="3136" file="dtsjob.cpp:3501">
    <![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
    ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
    <![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
    context="" type="3" thread="3136" file="dtsjob.cpp:3513">
    <![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
    file="dtsjob.h:166">
    <![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
    {38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download.  Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
    context="" type="2" thread="3136" file="dtsjob.cpp:3652">
    <![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
    file="dtsjob.cpp:3205">
    <![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
    thread="3136" file="netaccessaccount.cpp:288">
    <![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
    type="1" thread="3136" file="netaccessaccount.cpp:858">
    <![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
    (0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
    The IIS server logs u_ex150219.log captures the request:
    2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
    401 2 5 1509 2
    2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
    401 1 3221225581 1509 4
    2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
    401 1 3221225581 1509 3
    2 x Domains: DomainA and DomainX
    - Single domain forests
    - No trusts between domains/forests
    DomainA\PRIMARYSERVER
    - Primary Site Server, MP, DP, IIS, all roles
    DomainX\DP1
    - Distribution Point, IIS, etc
    - CCM client installed

    Based on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
    Jason | http://blog.configmgrftw.com | @jasonsandys

Maybe you are looking for