Error: "Failed to download and hash all additional files" when running task

• • Description
  • Cause
  • Troubleshooting
  • Resolution

Description

Launching a software distribution task often results in one of the following errors:

Failed to download and hash all additional files

Failed to download all additional files for a package

Sometimes this error, though rare, may also be seen:

No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.

Cause

There are several possible causes:

1. The hashes in the database do not match the actual hashes of the files.

2. The Scheduler Service on the core does not have access to the package files where they are stored on the network, so it cannot calculate the hash, update the database or generate the taskmanifest file.

3. The file being downloaded is not an allowed MIME type in IIS.

4. Files specified in the distribution package do not exist or cannot be found. This is common if using the auto detect feature in MSI distribution packages.

5. The path to the files in the distribution package is using a c:\program files\path format. This is incorrect, it must be a UNC or an HTTP path.

6. If the package is being hosted on a workstation vs. a server the number of connections may be exceeded.

7. The taskmanifest file is being generated with an incorrect Core server name or ip address. The scheduler account is locked out or unable to authenticate.

Troubleshooting

1. In the LANDESK Console under the Scheduled Task, under Failed, right-click on the device name with the failure and choose View log file.

   • If the log file does not exist, this indicates that the hash was never generated.  This usually means the files cannot be accessed and hashed.  If using a UNC share this indicates that the Scheduler service account does not have access to the files.  If using a Web Share it may indicate a hidden file, invalid mime types, or incorrect permissions.

   • If the log file exists, the error is after the hash generation and more likely to be a problem with a failure to download a file, or a file has been modified since the has was created.

2. View the scheduledtaskhandler_##.log in \\CoreServer\ldlog. This log helps indicate what files the package is having issues hashing or downloading.

3. If this article does not assist in resolving this issue, contact LANDESK support.

Resolution

1. Reset the package hash.  To do this do the following from the LANDESK Console:

   1. Go to Tools | Distribution | Distribution Packages.

   2. Right click on the Distribution Package and choose Reset package hash.

2. Use different credentials for the scheduler service, or modify the share and file permissions so the account that launches the scheduler service will have access.

3. Verify that IIS mime types are properly configured. To do this:

   • Open the IIS administration tool on the core.

   • Choose Default web site properties | HTTP Headers | MIME Types.

   • Add the following MIME types:
     Extension:  .*
     MIME type:  All file types

4. Verify all files in the distribution package exist and are not hidden.

5. Change the source path to the files from UNC to HTTP. This helps eliminate issues that may occur due to share permissions.

6. If the core server is in a different AD domain, add the full domain name in the properties of the package under the package location.

   For example:

7. Add the Domain Computers group to the security tab of the share.

8. Create a new Delivery Method, and uncheck the Bandwidth Throttling option.  Test using the new Delivery Method.

9. If the taskmanifest file in the ldlogon\Filelists folder does not contain the correct Core server name or IP address the name of the Core server has been changed.

10. Unlock the account used for the Scheduler service.

11. Use Preferred Servers so you can specify the account that will download package files instead of using Local System. In the console, click Configure, then Preferred Server, then Add, and specify the server and account you wish to use. (You can only configure preferred servers from the console on the core itself).