Problem

When running a Software Distribution task the task fails with: Failed to download all additional files. Here we provide a few suggestions on how to resolve this issue.

Troubleshooting

Reset the package hash

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

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 ## ## in the below will need to be replaced with the Task ID (which can be gathered from the Core Server).

“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.

Example where Core Server name is LDMS88:

"C:\Program Files\LANDesk\LDClient\sdclient.exe" /f /p="Http://LDMS88:9592/ldlogon/filelists/taskmanifest.LDMS88.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 machines 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"

Example:

"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

Using Xtrace initiate a trace on these three services lddwnld, sdclient.exe, and tmcclnt

On the client enable the following registry key:

HKEY_LOCAL_MACHINE\Software\Intel\LANDesk\XTrace

"sdclient”= dword:00000001

“lddwnld” = dword:00000001
“tmcclnt" = dword:00000001

Gather the Xtrace logs files which will have the file extension of XLG.  The.xlg files will be in the same directory as the actual files generating them (C:\Program Files\LDClient).

Get the proxyhost.log

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:127.0.0.1:3022 Connection close 0 0 0 0
2007-01-19 15:55:47(1692-952) proxyhost.exe:127.0.0.1:3022 - LANDesk.Gateway [19/Jan/2007:09:55:47 -0600] "HEAD http://LANDesk.Gateway@127.0.0.1:9592/ldlogon/FileLists/taskmanifest608.98.ini HTTP/1.1" 200 97 354
2007-01-19 15:55:47(1692-952) proxyhost.exe:127.0.0.1:3022 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.