KACE Product Support

What version of the agent on you on?

You can enable debugging in 5.3 with this command:
AMPTools.exe debug=true

AMPTools is found in program file -> dell -> kace

klaunch / kdeploy are very tightly related. I often get them confused. At the end of the day I simply worry about the time that I tried my test and look at all logs. Usually I am looking right after a test so I sort the log directory by last modified and go from there.

Here it looks like the resource files do not exist to even invoke a launch. What was the kbox #? Did it get downloaded? If it did download what happens when you run it manually (runkbot -s kbotid 0) ?

The files didn't download. I'll try debug.

I turned on debug and I get this in the klaunch log:

[Tue Feb 14 12:34:03 2012] KDeploy ERROR - parameter 'install_cmd' is missing a value

[Tue Feb 14 12:34:03 2012] KLaunch Local command returned -1(0xFFFFFFFF)

[Tue Feb 14 12:34:03 2012] KLaunchProcess: KLaunchFlagsCmdArgs completed exitCode=-1

[Tue Feb 14 12:34:03 2012] runkbot : Failed to launch KDeploy.exe process: -1

Here's another tidbit from the log: -install_cmd=""


I'm not sure what install_cmd refers to. This is a batch file that should download and run, and I have the install command set manually with the batch file name as the command. I tried start /max kace1215.bat just for grins, but the log isn't telling me the install_cmd parameter is wrong; it just doesn't think there is one.

I can't find anything on a search for install_cmd. Any ideas what this refers to?

Thanks.

when you deploy this as a targetted kbot (targetted to your specific test machine) using run now does it work? What are the details of kbot 92.

This might be better served by a support ticket.

It's a bundle, not a script, so I don't have the run now option. However, 2 things:
- I had a similar script, so I did a run now on that. That was 11 minutes ago, and it doesn't appear to have done anything yet. There's no big dependency file, so it isn't waiting on a download
- I see my previous attempts for this bundle and others in the Run Now Status window. They almost all report success, even though they haven't and even though the debug level log files show failures.

I was on the phone with Kace support yesterday for almost 2 hours. Great guy, and we eventually got a zipped file with an msi file and a batch command to install something, so we thought it was fixed. Guess not.

Any word on the update that's supposed to be coming out this month?

Yay support! Could we get more details on the jobs here? How you set them up? The update should be out any day now.

OK, I'll put together job details. Thanks.

Since my last message, I've updated the appliance and a few agents for testing, but still no dice on running apps. I submitted a ticket yesterday, so I'm waiting on a response from that.

I have a batch file that prevents an auto shutdown at night so users can run a statistical job overnight. I had this (and several other jobs) running successfully from the user portal for some of my testing last month, but then all user apps stopped running last week. I installed the October updates for the appliance and agent, but still no dice. Then I had the support experience I mentioned above.

Here's what I did with the poweroff disable batch file:
- Create a new item in software inventory, associate to OS's and upload the batch file
- Create a new MI and used the default command which showed the batch file name. The managed action is disabled and a pc label is assigned (my test pc has that label). Max attempts is blank.
- Create a new item under service desk software tab. Enabled, Package type Install.

When I run from the user portal, the batch file isn't even downloading anymore, so maybe that explains the "install_cmd" problem since there's no file to run.

In the meantime, does anyone know what "KDeploy ERROR - parameter 'install_cmd' is missing a value" means?

I forgot to mention that I've tested this using the local system account.