none
Application not downloading to Client

    Question

  • Hi,

    We are testing some application deploys.   We have configured these and ran machine policy retrieval and evaluation.

    All of the apps show in the Software CEnter.

    The ones that were configured as required have started to download.   We have also started one other that was available.

    However in the installation status area, it shows 0 percent on the download as shown in screenshot below.

    What log would show information related to this download to help us debug?

    Thanks in advance.


    Thanks Lance

    Tuesday, September 24, 2013 8:31 PM

Answers

All replies

  • CAS.log and LocationServices.log. It's most likely a boundary / group issue or missing content on a DP.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, September 24, 2013 8:39 PM
    Moderator
  • Hi,Are the boundaries and boundary Groups configured so that the client is within a boundary and boundary Group? it looks like the client cannot find a DP with the content to download it..

    Check the contentTransfermanager.log and DataTransferService.log files on the client for more information.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, September 24, 2013 8:41 PM
    Moderator
  • i see this error in the dataTransferService.log file

    <![LOG[GetDirectoryList_HTTP('http://machinename:80/SMS_DP_SMSPKG$/P0100012') failed with code 0x87d0027e

    i cant get to http://machinename:80/SMS_DP_SMSPKG$/P0100012 from the installed  client.  We get a 500 internal server error.

    same error on the actual config manager server prod-sccm.olh.local.

    in the Distribution Group Configuration Status Details I see this.

        9/24/2013 4:16:00 PM    Content was distributed to distribution point    Distribution Manager successfully distributed package "P0100012" to distribution point "["Display=\\machinename\"]MSWNET:["SMS_SITE=P01"]\\machinename\".    Success    P0100012    

    Any suggestions on what to check next?



    • Edited by Lance Lyons Thursday, January 23, 2014 10:49 PM
    Wednesday, September 25, 2013 12:11 AM
  • 0x87d0027e = Bad HTTP status code.
    Check \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status if the DP was installed successfully at all.


    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, September 25, 2013 7:06 AM
    Moderator
  • Have you cheked  if the "HTTP activation" option of .NET Framework 3.5 Feature is installed?
    Wednesday, September 25, 2013 8:28 AM
  • 0x87d0027e = Bad HTTP status code.
    Check \Monitoring\Overview\Distribution Status\Distribution Point Configuration Status if the DP was installed successfully at all.


    Torsten Meringer | http://www.mssccmfaq.de

    Hi Torsten

    From my previous reply, the distribution Point Configuration Status Details shows below.  Is this what you mean by checking the status?

        9/24/2013 4:16:00 PM    Content was distributed to distribution point    Distribution Manager successfully distributed package "P0100012" to distribution point "["Display=\\machinename\"]MSWNET:["SMS_SITE=P01"]\\machinename\".    Success    P0100012  


    Thanks Lance


    • Edited by Lance Lyons Thursday, January 23, 2014 10:50 PM
    Wednesday, September 25, 2013 3:44 PM
  • Have you cheked  if the "HTTP activation" option of .NET Framework 3.5 Feature is installed?

    I Tried this and it did not help.

    Thanks Lance

    Wednesday, September 25, 2013 4:17 PM
  • Hi,

    I found a blog talking about a similar issue. Please see whether it helps.

    http://venusingireddy.blogspot.com/2013/07/error-sending-dav-request-http-code-500.html


    Juke Chou
    TechNet Community Support

    • Marked as answer by Lance Lyons Thursday, September 26, 2013 4:57 PM
    Thursday, September 26, 2013 3:52 PM
    Moderator
  • Thanks Juke,

    That was it.  I am not sure how the paths pointed to c:\ and we actually had the folders on E:\

    I wonder if some cumulative update or perhaps a reinstall of Config manager caused that scenario?


    Thanks Lance

    Thursday, September 26, 2013 5:14 PM