KACE Product Support

almost sounds like rights issue with the kbots directory. have you tried to remove the kace client, delete the kace directory if it does not and reinstall? - SMal.tmcc 11 years ago

not yet, but I will give that a try - wd_bs 11 years ago

Uninstalled, deleted the KACE dir,reinstalled, same problem. Error creating process: C:\ProgramData\Dell\KACE\tmp\huhsrnlz\packages\kbots\319\WDFileAudit.exe : (2) The system cannot find the file specified. - wd_bs 11 years ago

try temp disabling AV/windows defender, etc to see if it is blocking the exe for some reason - SMal.tmcc 11 years ago

It's not, the executable I am trying to run is on the client, but in a different Kace directory. - wd_bs 11 years ago

We have the same issue.

Same Script run on separate machines two different results.

working path.
C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\521

Error path.
C:\ProgramData\Dell\KACE\tmp\y7dhs4w5\packages\kbots\521

We have checked the AV and have found no Blocking. The Kace Agent is current and up to date. - jander32 10 years ago

Full control for both System and Administrators, - jander32 10 years ago

I think the issue coming from the files you attachced to "Dependencies".

It happened to me the same thing. I found out the issue coming from the way the zip file that we created and attached to the Dependencies. I did not specify correct path in "Scripting"

I zipped the files at the parent folder of all files and attached zipped folder to Dependencies. So when the zip is unzipped, it is put the parrent folder in the same location of the zip folder.

Here is the command I called in the Script
$(KACE_DEPENDENCY_DIR)\InstallLawsonSoft.vbs

The correct command is "$(KACE_DEPENDENCY_DIR)\LawsonSoftware\InstallLawsonSoft.vbs". - CodyNguyen 10 years ago