Application stuck transferring to child primary distribution point

I have a single application (not a package) which is refusing to distribute to one of the child primary site servers. 
Bit of background: The server was built a few days ago and all packages were prestaged and loaded onto the server successfully except for one.
- The content status for this particular package is sitting at the state of "In Progress" (Starting to process content)
- The despool component manager is continually reporting message ID 4407 (Despooler successfully receveied the compressed image for package XXXXXXX version 9.)
- The despool.log periodically reports these messages (This package's information hasn't arrived yet for this version [9]. Retry later...) followed by (Despooler failed to execute the instruction, error code = 12)
- Distribution manager component status will loop through status messages 2300, 2311 and 2301 (Beginning to process package, Successfully created or updated package and Successfully processed package)
- Distmgr.log will report that the StoredPkgVersion is 5, and the SourceVersion in the DB is 10.
I have tried
- Removing the package from DP, waiting, and then re-adding it
- Updating the distribution points (increment the version number from 9 to 10)
I recall having this issue in 2007 with standard packages, and I could fix this easily enough by updating the PkgStatus table and then refreshing the DP so it would re-download the content and work its issues out.
In 2012 it is clearly different, especially because I'm dealing with an Application and not a Package per se. 
Is there a way to fix this? (Other than deleting the package from existence and recreating it)
Is there a way to clear all previous knowledge of this application at this particular child site, allowing it to just transfer the current, latest version of the content? (similar to how one would have fixed this in 2007)
Thanks in advance!
Tim

Hi Jason
Thanks for the reply.
The AV product does not appear to be getting in the way.
The activity in sender.log looks healthy, I can see the CAS transferring data across to this site (and others) without error.
All other content (Update packages, regular packages and OSD images) have distributed correctly
We did turn off the "Enable this distribution point for prestaged content" feature after doing the initial prestage of all media. 
Is there a way to clear this package from a given child site so that we can distribute it down again and it ignores the older StoredPkgVersion that it has?
One thing I have noticed, before I left for the day yesterday, I deleted this package from this particular distribution point. Despite doing this, the despooler continued to loop the message ID 4407 (Despooler successfully received the compressed image for
package XXXXXXX version 9.) over and over again.
The current version of the package is 10, what this server allegedly has according to DistMgr.log is version 5. 

Similar Messages

  • Application won't download/install from distribution point

    Hello,
    I have a new distribution point that clients refuse to download application deployments from. The advertisement(s) get stuck at "Downloading 0%". 
    The DP monitor confirms that the package is distributed. Boundary and boundary group is created and should be OK for this DP (which has firewall disabled).
    When I take a client and put it on a different subnet, the application downloads from another working DP.
    Any suggestions?

    CAS.log --->Download started for content Content_310d8d2d-9457-455b-ac4a-1a03fb4567f3.1
    -->And it will just hang until I cancel the deployment/install on the client.
    LocationServices.log --> no errors
    Unable to retrieve AD site membership --> ????both the client and the DP are domain members
    Distribution Point='http://MNTH-SP-SRV01.xxxx.local/SMS_DP_SMSPKG$/Content_310d8d2d-9457-455b-ac4a-1a03fb4567f3.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState"
    Value="0"/></Capabilities>', Signature='http://MNTH-SP-SRV01.xxxx.local/SMS_DP_SMSSIG$/Content_310d8d2d-9457-455b-ac4a-1a03fb4567f3.1.tar', ForestTrust='TRUE'
    (MNTH-SP-SRV01, this is the DP I'm trying to deploy from)
    DP is associated to a boundary group, and the boundary with the address range which the server is on is a member of the boundary group.

  • Deploying operating system and applications to branch distribution points

    Dears,
    Is there a way to distribute the content of an operating system image or an application package manually to a branch distribution point to overcome network bandwidth limitation and let SCCM know it is distributed there or you still need to distribute
    content via SCCM console?
    Regards,  

    You will always need to perform action via the console (or do something similar via PowerShell). I think the options of prestaging content, or a pull distribution point could be beneficial for you. Have a look here for more information:
    http://technet.microsoft.com/en-us/library/gg682083.aspx
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Problem with option: enable this distribution point for prestaged content

    Hi, for past few days I have been focused on application deployment with SCCM 2012 R2 (I am learning SCCM 2012 R2 reading books, watching video trainings . . .). Having followed allong book Mastering System Center 2012 R2 Configuration Manager I also did
    deployment of Microsoft Office 2013, Adobe Reader 11, Foxit Reader 4.2 and Notepad ++ to test collection containing one Windows 7 computer. In one of examples prestaged content file is created for Foxit Reader application. In order to do so, if I am
    right, option Enable this distribution point for prestaged content
    has to be checked on distribution point and I did that.
    Problem is that I noticed deployment of any application to test collection failed every time - system waits for prestaged content file if this option is selected. Then I have to delete deployment of given application, application itself, deselect option
    Enable this distribution point for prestaged content and create app, distribute it to DP and deploy to test collection - then everything works well.
    To make things worse, having deselect option Enable this distribution point for prestaged content (I did it yesterday and I checked that several times) this morning I checked again and this option is selected again. What might be the cause
    of this behaviour? I expected this option to be deselected - this is weird to say at least.
     

    When you enable the option "Enable this distribution
    point for prestaged content" on a DP, it causes newly created applications/packages to default to "Manually copy the content in this package to the distribution point"... This would then cause the deployments on the clients to remain
    at 'waiting for content' - unless if you manually prestage the content, as this option requires it.
    If you enable the option "Enable this distribution
    point for prestaged content" on the DP, but want to automatically have CM distribute the content, then configure the app/package to do so,
    before distributing the content: Distribution Settings tab > Prestaged distribution point settings > Automatically download content when packages are assign to distribution points.

  • Content Available on Distribution Points

    Hi,
    I would like to create a report for the content (packages, Image files, driver package, applications) available on Distribution Points in our environment.
    If i go to the properties of Distribution Point -> content, it shows all the data available on DP.
    Is there a way to export this to excel or any other SCCM report which provides all the details of the content available on DP.
    Thanks

    Torsten, Let me explain 
    If you go to Administration -> Distribution Points -> Properties -> Content
    I could see all the content available on this distribution point
    Now when i run the report All
    content on a specific distribution point. This report shows the names of all the package/application etc. names available on this distribution point.
    But in this report it shows names of applications/software which are not available on this and are not showing under the Content section of the distribution point. 

  • Package content on Primary Site Server (no Distribution Point Role)

    Hey,
    I have the situation that there are 3 Servers with following roles installed:
     1.File Server
     2.SCCM 2012 R2 CU3 Primary Site Server / Database Server (Was a distribution Point previously to update to CU3)
     3.Distribution Point
    Our packages are all stored as "source" on the File Server.
    Now some SCCM Applications / packages are created and distributed to the distribution point.
    Unfortunately on the Primary Site Server the folder "SCCMContendLib" extends as it does on the distribution point (so this means that all packages are distributed to the primary site server, too.
    My question is now- why? :)
    Is this really needed (I see no reason for it) or is it a problem in the infrastructure (if yes - how can I resolve it)?
    Thank you for help
    Kind Regards

    Not a problem with your infrastructure. What you're describing it the default behavior for ConfigMgr, in terms of storing content on the primary.
    -Nick O.

  • Problems streaming specific App-V applications from specific distribution point. Cannot find any KB article on the error?

    Hi there,
    Some clients are having trouble streaming specific app-v packages from a specific distribution point.
    sftlog.txt shows the following on the client:
    [05/14/2014 10:39:25:442 AMGR WRN] {tid=E7C}
    Attempting Transport Connection
    URL:
    https://APPVSERVER:443/NOCERT_SMS_DP_SMSPKGE$/VirtualAppStreaming/AGR00215/{85738DDB-F118-48F3-9459-47354509E464}/AGR00215.sft
    Error: 2460410A-40002EFD
    [05/14/2014 10:39:25:458 JGSW ERR] {hap=34:app=APPNAME 2.0 2.0.0.0:tid=1334:usr=*****}
    The Application Virtualization Client could not connect to stream URL 'https://APPVSERVER:443/NOCERT_SMS_DP_SMSPKGE$/VirtualAppStreaming/AGR00215/{85738DDB-F118-48F3-9459-47354509E464}/AGR00215.sft' (rc 2460410A-40002EFD, original rc 2460410A-40002EFD).
    [05/14/2014 10:39:25:458 SWAP ERR] {hap=34:app=APPNAME 2.0 2.0.0.0:tid=1334:usr=****}
    The client was unable to connect to an Application Virtualization Server (rc 2460410A-40002EFD)
    I have recreated the DP based on the best practice for removing the DP and re-adding, as we've had other app issues which needed tidying up, but that has not fixed this issue.
    I have searched for the above error (The client was unable to connect to an Application Virtualization Server (rc 2460410A-40002EFD) but I get no results.
    Please help me with this, I've deleted the DP content and re distributed the content to the DP with no change.. If I remove the DP, the content is able to be streamed from other DP's no problem.
    Cheers
    Max
    Max Christopher

    It looks as though this may have been sorted out  - A re bind of the computer cert on the DP to the default website https binding seems to have resolved this for me.
    Max Christopher

  • Redistributing Application to Distribution Point Group

    Hey Guys - 
    Just a quick question for you about something I've never been 100% sure about and wanted to clear up...
    Let's say I have an "Application" in which I've added files to the source folder which is required by the script the application runs.  After adding the file, I need to update it's distribution on all 3 of my distribution points (which all
    happen to be in a DP Group.)  Which of the following methods will accomplish this or is the preferred method?  
    1. Select Application in console, choose "Deployment Types" tab, right click on type I want to update and choose "Update Content"
    2. Open Application's Properties, choose "Content Locations" tab, select the Distribution Group (which contains all 3 DPs) and click "Redistribute"
    3. Open Application's Properties, choose "Content Locations" tab, select each of the 3 distribution points and choose to "Redistribute" to each one of them
    Below is what my Content Locations looks like when distributed to all 3 DPs.  As is was distributed to the group containing all 3, it lists the group and the 3 DPs for a total of 4 objects.  Which of the above methods (or a different one) is the
    best way to go?
    Thanks!
    Ben K.

    Option #1
    http://eskonr.com/2013/09/sccm-configmgr-2012-how-do-i-refresh-the-application-after-change-in-source-files-or-source-location/
    Benoit Lecours | Blog: System Center Dudes

  • Content is being distributed to the distribution point - stuck at "In Progress"

    I have Windows Updates due to be installed on all international machines tonight at 12 AM, and our main distribution point gets the files just fine. Our international sccm server, however, is not.
    I'm get the "In progress" on the Content View under Monitoring, but it has been sitting like that for over 8 hours. I know there are a ton of logs in the C:\Program Files\SMS_CCM\Logs location that are constantly updating.
    Is there a log in there I can attach or show to help determine what's going on? There are so many logs. However, this is a very serious issue, and I don't know what's going on. It worked just fine, then last months worked, except for the fact that after
    about a week, it would say that the content "Failed" on the second sccm distribution point. And now, this month's updates are stuck on "In Progress" on copying it over.
    Please let me know what I can look into, as soon as possible.
    Thank you!

    Alright, so this is what it's looking like:
    PkgXferMgr.log has a ton of these:
    ========  Finished Processing Cycle ( 12/13/2014 6:20:56 AM Mountain Standard Time) ========~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 06:20:56.397+420><thread=3628 (0xE2C)>
    Sleeping for maximum 3600 seconds.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 06:20:56.397+420><thread=3628 (0xE2C)>
    Checking for sending capacity.  Used 0 out of 15.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.696+420><thread=3632 (0xE30)>
    COutbox::TakeNextToSend(pszSiteCode)  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.697+420><thread=3632 (0xE30)>
    No (more) send requests found to process.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.697+420><thread=3632 (0xE30)>
    ~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:00:14.698+420><thread=3632 (0xE30)>
    ========  Starting Processing Cycle ( 12/13/2014 7:20:56 AM Mountain Standard Time) ========~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:20:56.584+420><thread=3628 (0xE2C)>
    ========  Processing Jobs  ========  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:20:56.584+420><thread=3628 (0xE2C)>
    Job count is 0.  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.588+420><thread=3628 (0xE2C)>
    ========  Finished Processing Cycle ( 12/13/2014 7:21:06 AM Mountain Standard Time) ========~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.592+420><thread=3628 (0xE2C)>
    Sleeping for maximum 3600 seconds.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 07:21:06.592+420><thread=3628 (0xE2C)>
    Checking for sending capacity.  Used 0 out of 15.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.890+420><thread=3632 (0xE30)>
    COutbox::TakeNextToSend(pszSiteCode)  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.890+420><thread=3632 (0xE30)>
    No (more) send requests found to process.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.892+420><thread=3632 (0xE30)>
    ~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:00:14.892+420><thread=3632 (0xE30)>
    ========  Starting Processing Cycle ( 12/13/2014 8:21:06 AM Mountain Standard Time) ========~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:06.771+420><thread=3628 (0xE2C)>
    ========  Processing Jobs  ========  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:06.771+420><thread=3628 (0xE2C)>
    Job count is 0.  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.774+420><thread=3628 (0xE2C)>
    ========  Finished Processing Cycle ( 12/13/2014 8:21:16 AM Mountain Standard Time) ========~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.777+420><thread=3628 (0xE2C)>
    Sleeping for maximum 3600 seconds.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><12-13-2014 08:21:16.777+420><thread=3628 (0xE2C)>
    distmgr.log:
    Start adding package to server ["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\...  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.455+420><thread=2464 (0x9A0)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=2464 (0x9A0)>
    Thread Handle = 00000000000010C0  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=2464 (0x9A0)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.456+420><thread=4932 (0x1344)>
    The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.484+420><thread=4932 (0x1344)>
    STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=4932 GMTDATE=Sat Dec 13 06:23:08.485 2014 ISTR0="Workstation Patching - Dec 2014" ISTR1="["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="US10008A" AID1=404 AVAL1="["Display=\\sccm03.mydomain.com\"]MSWNET:["SMS_SITE=JP1"]\\sccm03.mydomain.com\"
     $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.485+420><thread=4932 (0x1344)>
    ~The contents for the package US10008A hasn't arrived from site US1 yet, will retry later.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.486+420><thread=4932 (0x1344)>
    STATMSG: ID=2372 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=4932 GMTDATE=Sat Dec 13 06:23:08.486 2014 ISTR0="US10008A" ISTR1="US1" ISTR2="JP1"
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="US10008A"  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.486+420><thread=4932
    (0x1344)>
    DP thread with array index 0 ended.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.487+420><thread=2464 (0x9A0)>
    DP thread with thread handle 00000000000010C0 and thread ID 4932 ended.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.487+420><thread=2464 (0x9A0)>
    ~Package US10008A does not have a preferred sender.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:08.999+420><thread=2464 (0x9A0)>
    ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=US10008A, Version=3, Status=2301  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.000+420><thread=2464 (0x9A0)>
    ~StoredPkgVersion (0) of package US10008A. StoredPkgVersion in database is 0.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.090+420><thread=2464 (0x9A0)>
    ~SourceVersion (3) of package US10008A. SourceVersion in database is 3.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.090+420><thread=2464 (0x9A0)>
    STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm03.mydomain.com SITE=JP1 PID=2184 TID=2464 GMTDATE=Sat Dec 13 06:23:09.096 2014 ISTR0="Workstation Patching - Dec 2014" ISTR1="US10008A"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="US10008A"  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.096+420><thread=2464
    (0x9A0)>
    ~Exiting package processing thread.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:09.097+420><thread=2464 (0x9A0)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:12.865+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:13.394+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:13.395+420><thread=3348 (0xD14)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:18.409+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:23:18.410+420><thread=3348 (0xD14)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-12-2014 23:53:17.953+420><thread=3992 (0xF98)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:00:08.191+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:14:38.368+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:23:23.041+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 00:53:28.130+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:00:13.375+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:00:13.376+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:14:38.544+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:23:33.227+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 01:53:38.332+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:00:18.577+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:00:18.579+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:14:38.734+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:23:43.428+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 02:53:48.526+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:00:23.783+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:00:23.785+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:14:38.926+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:23:53.624+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 03:53:58.722+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:00:28.985+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:00:28.986+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:14:39.116+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:24:03.820+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 04:54:09.080+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:00:34.393+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:00:34.394+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:14:39.521+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:24:14.228+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 05:54:19.325+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:00:39.612+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:00:39.613+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:14:39.713+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:24:24.423+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 06:54:29.521+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:00:44.817+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:00:44.819+420><thread=3348 (0xD14)>
    Sleeping for 60 minutes before content cleanup task starts.~  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:14:39.905+420><thread=3988 (0xF94)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:24:34.623+420><thread=3992 (0xF98)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 07:54:39.721+420><thread=3992 (0xF98)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:00:50.021+420><thread=3348 (0xD14)>
    ~Sleep 3600 seconds...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:00:50.023+420><thread=3348 (0xD14)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:35.600+420><thread=3992 (0xF98)>
    Found package properties updated notification for package 'US10008A'  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:40.602+420><thread=3348 (0xD14)>
    Sleep 30 minutes...  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:40.604+420><thread=3992 (0xF98)>
    Found notification for package 'US10008A'  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:45.606+420><thread=3348 (0xD14)>
    ~Used 0 out of 3 allowed processing threads.  $$<SMS_DISTRIBUTION_MANAGER><12-13-2014 08:12:45.624+420><thread=3348 (0xD14)>

  • SCCM 2012r2 - Remove "invisible" packages/applications from Distribution Point

    Hello alltogether,
    I've encountered the following issue:
    Our distribution points are displaying applications/packages as "In Progress - Waiting for Prestage content".
    These packages doesn't exist anymore. Neither as prestage file nor in the config manager itself. We never tried to apply this package by using a prestage file because such a file never existed.
    Even if I open the "content" tab of one distribution point, I can't find these packages in there.
    The exact status of this package is the following:
    Message: Distribution Content
    Message Detail: Distribution Manager instructed Package Transfer manager to send Package "x" to distribution point "y".
    Status Type: In Progress
    I want to remove these "ghost" packages from the Distribution Status overview. Anyone has a clue how to accomplish this?
    Thanks in advance!
    Best Regards
    Feyh

    Hello,
    thanks for your answer!
    Unfortunately no, there is no information about these files.
    Yesterday we installed a new one, extracted all of our prestage files on it and watched the status. The Packages weren't listed in the "Distribution Point Configuration Status".
    After some time we added the new DP to our general DP-group where all of our packages/applications are assigned to. Now the "non-existing" packages are added with the "in Progress" status.
    I had a look into "Distribution Point groups -> Our group -> properties -> content" but these packages aren't displayed in the list. Some of the packages are now in the "waiting for prestage content" state, others are staying with the "Detail will
    be available after the server finishes proccessing ...".
    We managed to remove one of the packages by deleting it from the database.
    The following statement removed it from the Distribution status overview. However, we still are able to find the package in the database.
    select  * from SMSPackageswhere PkgID = 'P100003B'
    DELETE from SMSPackages
    where PkgID = 'P100003B'
    Apparently the delete-statement affected 72 rows. But we are having no clue which. As long as we are not sure we killed anything important we are not going to do this with the other packages because it's the productive system. We can't reproduce this in our
    test system...

  • Distribution Point IIS Config - Multiple applications using Default Web Site

    Hi all,
    I've having some problems with a distribution point, when trying to download content I'm getting the following error in the datatransferservices.log:
    Error sending DAV request. HTTP code 500, status 'Internal Server Error'
    Looking at IIS, I can see that another application (uniflow print server) has published folders under the Default Web Site. 
    Reading
    similar errors it appears it may be to do with ISAPI filters being configured by the other application. Unfortunately these filters are required by the Uniflow application. So, my question is:
    Is there any way to change the web site used by the distribution point?
    Thanks,
    Iain 

    Not on a one off basis, no. The web sites are tied to ports which means you would also have to change the port. Both are global changes. The better solution is to not multi-purpose a DP.
    Jason | http://blog.configmgrftw.com

  • Is there a way to avoid having a content library on a site server when the Distribution Point role is not installed on that server (disk cost issue)?

    Hello,
    I don't think it is possible, but my goal is to start a discussion about content libraries and maybe suggest something for a future release or version of Configuration Manager.
    Actually, based on Configuration Manager Technet documentation, Configuration Manager creates a content library on each site server and on each distribution point.
    Often, when designing the architecture, people will offload the distribution point role from the site server to an external server (and add the role to other servers too for redundancy). They could also do the same for the Management Point role, but this
    is not related to content library. The idea is to save the site server from having to deal with clients for software distribution (applications, software updates, OS, etc.), this is especially true for organizations having a large number of clients and/or
    primary site servers involved in a hierarchy. Doing so will allow more resources on the site server to deal with the database and also replication in the case of a hierarchy.
    When doing that, you still have to maintain a content library on the site server and the thing is this library will usually become huge, especially for organizations having more than 1000 applications (add also OS images to this). Will the content library
    on the site server become as huge as the one for a distribution point having a copy of all content? I guess the answer is yes.
    I know that Pull distribution points will help offloading the task from the site server to distribute content to distribution points, but, correct me if I'm wrong, you still have to maintain a content library on the site server when using them, and they
    will not make the content library smaller on the site server. Also, I don't like the fact that you lose the rate limits feature with Pull DPs, but this is another story.
    Storage cost is high and in this scenario, it hurts to have to pay this cost for a content library not used by the clients, but only to distribute content to DPs.
    Correct me if I'm wrong, but the key component here is Distribution Manager on the site server; this is the one which has to maintain a content library to do its job.
    It would be nice if we could have a way to elect a specific distribution point (not on the site server) as the Distribution Manager for a site, that main DP would hold a copy of all content by default, but would be used to distribute content to other DPs
    and avoid the content library on the site server. Said differently, the Distribution Manager component would become a site system role that could be transferred outside the site server.
    Tnx for comments, answers or suggestions.
    Patrick

    There is no way to avoid that the contentlib will be placed on the site server.
    I don‘t agree that storage cost is high. It might be true for fast storage, but that‘s not needed for it.
    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

  • SCCM 2012 R2 Distribution Point Installs but does not send packet.

    I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
    send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got. 
    The computer account is in the Administrators group and Admin Domains; 
    Already checked the WMI with Wbemtest; 
    I uninstalled and installed the DP again; 
    Below is the log, changed the name to contoso by issues of customer privacy.
    Sleep 928 seconds...      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:00:07       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:12:13       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:40       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5264 (0x1490)
    Thread Handle = 0000000000002330       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5264 (0x1490)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41              
    5264 (0x1490)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41       5364 (0x14F4)
    DP thread with thread handle 0000000000002330 and thread ID 5264 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41       5364 (0x14F4)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:41       5364 (0x14F4)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:41                5364 (0x14F4)
    Failed to process package LAA00003 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:41      
    5364 (0x14F4)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:41      
    5364 (0x14F4)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:46       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    2528 (0x09E0)
    Sleep 1824 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5736 (0x1668)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5736 (0x1668)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47              
    5736 (0x1668)
    Thread Handle = 0000000000002A50      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47       5328 (0x14D0)
    DP thread with thread handle 0000000000002A50 and thread ID 5736 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:15:47       5328 (0x14D0)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:15:47       5328 (0x14D0)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47       5328 (0x14D0)
    Failed to process package LAA00004 after 66 retries, will retry 34 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:15:47      
    5328 (0x14D0)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:47      
    5328 (0x14D0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:15:52       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:42:18       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    2528 (0x09E0)
    Sleep 60 seconds...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Retrying package LAA00003       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5012 (0x1394)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:23       5112 (0x13F8)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:23       5112 (0x13F8)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23              
    5112 (0x13F8)
    Thread Handle = 0000000000001CF0      SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:23       5012 (0x1394)
    DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended.   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:23      
    5012 (0x1394)
    Only retrying local DP update for package LAA00003, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24       5012 (0x1394)
    SourceVersion (1) of package LAA00003. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:24       5012 (0x1394)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
    ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:24                5012 (0x1394)
    Failed to process package LAA00003 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:24      
    5012 (0x1394)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:24      
    5012 (0x1394)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
    ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"       SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Retrying package LAA00004       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\...                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       5996 (0x176C)
    Will wait for 1 threads to end.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    Attempting to add or update a package on a distribution point.               SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:29       4576 (0x11E0)
    The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet.           SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:29       4576 (0x11E0)
    Error occurred. Performing error cleanup prior to returning.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29              
    4576 (0x11E0)
    Thread Handle = 00000000000025F8       SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with array index 0 ended.     SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:29       5996 (0x176C)
    DP thread with thread handle 00000000000025F8 and thread ID 4576 ended.    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:29      
    5996 (0x176C)
    Only retrying local DP update for package LAA00004, no need to replicate package to child sites.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1.                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:46:30       5996 (0x176C)
    SourceVersion (1) of package LAA00004. SourceVersion in database is 1.            SMS_DISTRIBUTION_MANAGER               
    14/08/2014 00:46:30       5996 (0x176C)
    STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
    ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"             
    SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30       5996 (0x176C)
    Failed to process package LAA00004 after 67 retries, will retry 33 more times   SMS_DISTRIBUTION_MANAGER                14/08/2014 00:46:30      
    5996 (0x176C)
    Exiting package processing thread.         SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:30      
    5996 (0x176C)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Sleep 1825 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:46:35       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA.   SMS_DISTRIBUTION_MANAGER             14/08/2014
    00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       5292 (0x14AC)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32       4008 (0x0FA8)
    Processing status update for package LAA00003              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32               
    4008 (0x0FA8)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Sleep 1048 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       2528 (0x09E0)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:32       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA     SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:32               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Sleep 1043 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:37       2528 (0x09E0)
    Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA.  SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39              
    4008 (0x0FA8)
    Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\                SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39       4008 (0x0FA8)
    Processing status update for package LAA00004              SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39               
    4008 (0x0FA8)
    Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5            
    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:39       4008 (0x0FA8)
    Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA    SMS_DISTRIBUTION_MANAGER            
    14/08/2014 00:59:39               4008 (0x0FA8)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 1038 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:42       2528 (0x09E0)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       5292 (0x14AC)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleep 1033 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 00:59:47       2528 (0x09E0)
    Sleeping for 60 minutes before content cleanup task starts.      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:10:52              
    5772 (0x168C)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:28       5292 (0x14AC)
    Sleep 30 minutes...        SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       5292 (0x14AC)
    Found notification for package 'LAA00003'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Found notification for package 'LAA00004'          SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33      
    2528 (0x09E0)
    Used 0 out of 10 allowed processing threads.   SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33       2528 (0x09E0)
    Starting package processing thread, thread ID = 0x388 (904)      SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:33              
    2528 (0x09E0)
    Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34              
    2528 (0x09E0)
    Sleep 3600 seconds...    SMS_DISTRIBUTION_MANAGER             14/08/2014 01:11:34       2528 (0x09E0)
    STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
    Lucas Simoes MCTS

    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              13/08/2014 23:57:10               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    13/08/2014 23:57:10       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xBE8)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x3B4)     SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:11               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:11       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       3048 (0x0BE8)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:35       948 (0x03B4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       3048 (0x0BE8)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:36       948 (0x03B4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       3048 (0x0BE8)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45       3048 (0x0BE8)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45      
    3048 (0x0BE8)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:45               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:45       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
     PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       948 (0x03B4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52       948 (0x03B4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52      
    948 (0x03B4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:17:52               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:17:52       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:52       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x1680)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:52               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x18A4)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:37:53               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:37:53       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:16       5760 (0x1680)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:17       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       6308 (0x18A4)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:20       5760 (0x1680)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       6308 (0x18A4)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43       6308 (0x18A4)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43      
    6308 (0x18A4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:43               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:43       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
     PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       5760 (0x1680)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50       5760 (0x1680)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50      
    5760 (0x1680)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:38:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:38:50       4004 (0x0FA4)
    Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0xF28)      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200  SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Created sending thread (Thread ID = 0x11D0)   SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:58:50               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:58:50       4004 (0x0FA4)
    Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       3880 (0x0F28)
    Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:15       4560 (0x11D0)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:16       3880 (0x0F28)
    Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       3880 (0x0F28)
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:17       4560 (0x11D0)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       3880 (0x0F28)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27       3880 (0x0F28)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27      
    3880 (0x0F28)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:27               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:27       4004 (0x0FA4)
    Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
     Attempted max retry count. The job would be marked for deletion now.                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO"                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4560 (0x11D0)
    STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
    ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"               
    SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34       4560 (0x11D0)
    Pull DP Sending thread complete            SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34      
    4560 (0x11D0)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 00:59:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 00:59:34       4004 (0x0FA4)
    No (more) send requests found to process.      SMS_PACKAGE_TRANSFER_MANAGER              14/08/2014 01:19:34               
    4004 (0x0FA4)
    Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes                SMS_PACKAGE_TRANSFER_MANAGER             
    14/08/2014 01:19:34       4004 (0x0FA4)
    No (more) send requests found to process.     
    SMS_PACKAGE_TRANSFER_MANAG
    Lucas Simoes Rezende MCP, MCTS , ITIL V3

  • After installing SCCM 2012 R2 CU4, I show a Distribution Point warning that won't clear.

    I recently installed SCCM 2012 R2 CU4 on a LAB environment, and nowhere is it more important to wait until all requisite site roles are reinstalled before doing anything else.
    I did, and still do, have an warning/ error on the Site components that shows up on one of the child primary sites after the CU4 installation.
    Distribution Manager has not tried to install IIS component of operating system to distribution point “[“Display=\\SCxxx\”]MSWNET:[“SMS_SITE=xxx”]\\xxx\”. You should install and configure IIS manually. Please ensure RDC is also enabled.
    IIS is installed, RDC is enabled, but I get this error. What could be the real issue?

    Hi,
    So you have tried to reinstall IIS conponents and DP?
    Have you checked the distmgr.log? Anything helpful?
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Maybe you are looking for