I'm a bit of a newbie to LANDesk, and I'm having dificulty with deploying a software package.
I have a distribution package that I have created that when I run the scheduled task to deploy it fails with the following code:
16422 Failed to download all additional files for a package
I am attempting to have the client download using http. I have confirmed that I can enter the location of the files and download at least the msi via browser (in fact, I can browse the files in the structure with no problem. And I have another executable package that I can distribute via http with no issues to the same test machine).
The installation fails pretty quickly, probably within 60 seconds and I cannot find a log file that describes any kind of issue as to why. This software package has a LARGE number of additional files that are needed for the installation (in the order of ~1700 files), I don't know if that plays into it or anything?
Can someone point me to where I can get more information regarding why it's failing and what I can do about it?
Thanks in advance.
First thing u have to check is that path (UNC/Http) u gave is rite or not.
secondly try to access the unc / Http paths from the client side.
Third ritght click on the software package and press on reset package hash.
I think these will helpful for u.
Do you have modified your packages recently or do you change someting in the source files?
Check your the source path. Try to remove all special characters or space.
If it still not works, some times you shoud create a self-extracting compress file with all the source files and folders, ant then, package it... Dont forget to configure the comand line that the self extractor will automaticly run to install the soft.
Hope it will help you.
Ce message a été modifié par: Gilles PORTAL
I have checked both the path and that the client has access to the files. I'm attempting to use http, and the files are browsable/downloadable througth a browser on the client (mentioned in the question). Rehashing didn't work.
No software changes to it, it's newly created.the path DOES have some spaces in the additional files, however i can't take them out or they will not be found when the MSI kicks off. Are spaces not allowed in http distributions?
Really I'm looking for a means of figuring out what's wrong, I don't know where to find logs or error reporting.
For log first you need to right click on your scheduled task and click info, it will show you the ID, now in log folder ScheduledTaskHandler_ID.log is available
one thing more you can do is when your scheduler task gets fail you can right click on it and view log file
you need to past your log file here for further solution
I tried to find the log by right clicking on the failed node in the task, but it didn't give me any kind of option for log file. Othe tasks that succeeded had this, but this one I could select, but I couldn't find a log file anywhere.
Did you check your scheduled task ID ? (right click on scheduled task and click info) then in log folder sort by date and you will find scheduler taskshandler ID.log
what version you are using
Checked for a scheulertaskshandler id log and there wasn't one. I changed the package to unc and now it's downloading correctly, but I'd like to figure out why the http one is working right.
Using version 9 sp3
Try verifying that there aren't any .config files in your installation package. If there are, rename the file extension to something else, then use a batch file client side to rename it back before the installation runs. Windows/IE uses the .config file association and will foul up a LANDesk package with the error message you described. It took me a LONG time to figure this out....
There are in fact 3 that end in .config. That must have been frustrating to figure out. I think I may try to do a install from source with this one...
Cool, please post whichever solution works for you.
on the client, look under \ldclient\data
Sort by date, you will see two logs with the same ID but slightly different names, one of those will show you more details
There wasn't a log file for it there either. That's the frustrating part, I couldn't find a log file for it anywhere.
I experienced the same thing. With the .config file issue no log files get generated on clients.
Good to know that I'm not just going nuts. Looks ilke it downloaded successfully as a unc and did it's install.
I was looking at other log files there and wondering how to interpret some of it, especially return codes, does anyone know of any documentation that helps with that?