Error: "Failed to download additional files"

Version 10

    Verified Product Versions

    LANDESK Management Suite 9.6LANDESK Management Suite 2016.xLANDESK Endpoint Manager 2017.x


    When running a Software Distribution task the task fails with the error "Failed to download all additional files".


    Here we provide a few suggestions on how to resolve this issue.



    Reset the package hash

    A common issue when getting the error “FAILED TO DOWNLOAD ALL ADDITIONAL FILES—TASK MANIFEST” is that the hash on the file has been modified. Try resetting the hash on the package.

    reset package hash.bmp



    Gather client logs that can assist in Troubleshooting

    • C:\Program Files\LANDesk\LDClient\data\sdclient_task#.log
    • C:\Program Files\LANDesk\LDClient\sdclient.log
    • C:\Program Files\LANDesk\LDClient \ tmcsvc.log
    • C:\Program Files\LANDesk\Shared Files\proxyhost.log
    • C:\Program Files\LANDesk\LDClient\ SDClientTask.[Core-Name].[task#].log


    Verify that the files can be downloaded


    Refer to the above logs to determine which file is having a difficult time downloading.

    From the agent workstation, try to download the Task Manifest file as local system manually as directed below:


    In this example replace “core” with the name of your Core Server. The #### below will need to be replaced with the Task ID.   (To gather the task ID right-click the scheduled task and select "Info".  The ID # will be in the top right)


    “C:\Program Files\LANDesk\LDClient\sdclient.exe” /f /p="Http://core/ldlogon/filelists/taskmanifest####.inI"

    If successful the task manifest file will be downloaded to ..\Program Files\LANDesk\LDClient\sdmcache\


    Where Core Server Name is


    "C:\Program Files\LANDesk\LDClient\sdclient.exe" /f /p="Http://LDMS2016:9592/ldlogon/filelists/taskmanifest.LDMS2016.8.3.ini"


    In this example there is no need to replace “localhost”, but you do need to replace the #### with your Task ID. When you use localhost Windows resolves that to the client computer's address that the command is initiated from. The purpose of doing this is to use sdclient to redirect the request properly. If this is successful then proxyhost and lddwnld are most likely working properly.


    C:\Program Files\LANDesk\LDClient\sdclient.exe /f /p="Http://localhost:9592/ldogon/filelists/taskmanifest####.ini"




    "C:\Program Files\LANDesk\LDClient\sdclient.exe" /f /p="Http://localhost:9592/ldlogon/filelists/taskmanifest.LDMS88.8.3.ini"



    Get the sdclient_task##.log


    Enable XTrace


    1. How to enable Xtrace Diagnostic Logging
    2. Get the proxyhost.log
    3. Make sure that the proxyhost.log says that the result was 200 for the web request (see bolded below).

    2007-01-19 15:55:47(1692-952) proxyhost.exe:Made direct (non-proxy) connection to STL-NT-LD1:80
    2007-01-19 15:55:47(1692-952) proxyhost.exe: Connection close 0 0 0 0
    2007-01-19 15:55:47(1692-952) proxyhost.exe: - LANDesk.Gateway [19/Jan/2007:09:55:47 -0600] "HEAD http://LANDesk.Gateway@ HTTP/1.1" 200 97 354
    2007-01-19 15:55:47(1692-952) proxyhost.exe: EOS on request


    Resultant error codes that can indicate a problem:

    404 –Indicates that the package share is not reachable.

    401 – Indicates that the package share cannot be accessed. This indicates a permission issue.

    503 – Indicates a possible performance issue with IIS.