The most common way this happens is you modify one of the files of the package and you neglect to reset the hash.
The first time a SW distribution package is distributed, a hash value is calculated for each of the files (i.e. main file + any additional files) that you have defined as being part of the package. If you subsequently change one of the files, there will be a discrepancy between the physical file and its hash value in the database. Further distribution of the package will fail in exactly the way that you describe.
To rectify the situation, select the package in the "distribution packages" console plugin and click the "reset package hash" icon in the icon bar.
I would check on the system that all the services are installed - I had that message alot after installing 8.8sp2 and found the multicast services was missing or if i restarted it I was OK.
Also might be worth checking out
I have reset the hash value, still failing. Services soudns like where the issue could lie. Silly question, where can I find what has been installed or what else I can install.
Right click on my computer, goto manage and then to services.
I use the commands from the run box to install a missing service
Install the LANDesk Remote Control Service
"C:\Program Files\LANDesk\LDClient\issuser.exe" /resident
Install the LANDesk(R) Management Agent service
"C:\Program Files\LANDesk\Shared Files\residentagent.exe" /register
Install or remove the LANDesk(R) Software Monitoring service
"C:\Program Files\LANDesk\LDClient\softmon.exe" /install
"C:\Program Files\LANDesk\LDClient\softmon.exe" /remove
Install or remove the LANDesk Targeted Multicast service
"C:\Program Files\LANDesk\LDClient\tmcsvc.exe" /i
"C:\Program Files\LANDesk\LDClient\tmcsvc.exe" /r
Installed all the services, though multicast wont install. rebooted but nothing.
Seems really strange just tried the batch file on some client machines and it failed as well.
Could there be some down-to-earth explanation such as permissions preventing the client from accessing the files? Has distribution from the this distribution point ever worked?
Here's a way to get more debug info: on the client, create a DWORD value named lddwnld with data = 1 in HKLM\Software\Intel\LANDesk\xtrace. On your next distribution, you will get a file called lddwnld.xlg in the ldclient folder. It should tell you what happened when the client tried to download the files.
This is a debug setting. Don't use it in production...
THis update resolves this issue. In some cases you have to re-create the scheduled task.
Is this update included in 8.8 SP2a?