So, what this log is telling you is that you can't download the taskmanifest.XERXES.31.7.ini file. This file is (or at least should be) created when the task is started. The first thing to do is to verify that this file does indeed exist on the coreserver. It should reside in the ..\Program Files\LANDesk\ManagementSuite\LDLogon\filelist directory. If the file is not there then you will need to cancel the task and restart it. This should create teh xml file.
Assuming that the file exists there try the following:
1-Make sure that you have the patches listed in this article applied: http://community.landesk.com/support/docs/DOC-5190
2- Under your Delivery Method look under Network usage--> Download and uncheck (if checked) "Dynamic bandwidth throttling". Restart the task. If you continue to get the error continue to the next step.
3- Check the proxyhost.log file (located in ..\program files\landesk\shared files directory)
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:
4- Try to download the file from the client machine using the following commands:
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"
"C:\Program Files\LANDesk\LDClient\sdclient.exe" /f /p="Http://localhost:9592/ldlogon/filelists/taskmanifest.LDMS88.8.3.ini"
Remember that when the client is trying to download the file it is using Local System and not the logged in user.
This should get you looking in the right direction at least.
Bitte um Kontaktaufnahme auf meine private e-mail Adresse.
I am having this issue is well. When I manually run it like the example from a command prompt on a test machine, it works fine. It starts out with a partial and then finishes. On the same test PC, when I push a package, it stops at the partial and fails. I have tried with both the core name and with http://LANDesk.Gateway@coreIP/ldlogon/FileLists/taskmanifest.KQPLDCORE01.529.71.ini
From Log file:
Wed, 27 Jan 2010 11:54:02 DownloadFile returned 490
Wed, 27 Jan 2010 11:54:02 ..\AdditionalFiles.cpp(65): (8DAC4026): Failed to download file http://LANDesk.Gateway@coreIP/ldlogon/FileLists/taskmanifest.KQPLDCORE01.529.71.ini : (80070002)
Wed, 27 Jan 2010 11:54:02 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)
Any ideas as to what to look for?