Hello,

I am trying to deploy a managed installation on the KB1000. The software to be installed is a zip file that contains the setup.exe and a number of other needed files. In the configuration I select the "Configure Manually" and provide the following Full Command Line: C:\Program Files\KACE\KBOX\downloads\577\setup.exe -s -f2 setup.log

After the managed install tries to work, I go to the server in question and confirm that the contents of the zip file are in the correct place and match the command line string above. However, the debug.log shows the following which seems to indicate its not looking in the correct place for the software on the server. It almost lookes like its parsing the space between "Program" and "Files". Any suggestions on the format of the Full Command Line string? Or, am I barking up the wrong tree in regards to the actual issue?

thanks,
Ben

new Process C:\Program Files\KACE\KBOX\downloads\577\setup.exe -s -f2 setup.log
[04/26/2010 19:18:19] msicmd: 'C:\Program'
[04/26/2010 19:18:19] msicmdextra: 'Files\KACE\KBOX\downloads\577\setup.exe -s -f2 setup.log'
[04/26/2010 19:18:19] msiarg: '
[04/26/2010 19:18:19] msiargextra: '
[04/26/2010 19:18:19] Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at KBClient.MIPackageMgr.launchProcess(String command, String parms, Int32 adminInstall, String workingDirectory)
[04/26/2010 19:18:19] Exception cont.: System
[04/26/2010 19:18:19] --- NO FILE ---
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
It is having issues with the space in "Program Files". Either wrap "C:\Program Files\KACE\KBOX\downloads\577\setup.exe" in quotes or just use "setup.exe -s -f2 setup.log". The full path requirement of using zip files doesn't necessarily require the FULL path - you just have to specify the executable along with any command line parameters.
Answered 04/26/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
I had tried wrapping the full path with double quotes, but the results were similiar to what I posted initially. I just attempted the 2nd item you suggested where the path isn't specified, and below are the results in the debug.log. This looks much better, but still doesn't seem to be looking in the correct place.

[04/26/2010 19:33:17] new Process setup.exe -s -f2 setup.log
[04/26/2010 19:33:17] msicmd: 'setup.exe'
[04/26/2010 19:33:17] msicmdextra: '-s -f2 setup.log'
[04/26/2010 19:33:17] msiarg: '
[04/26/2010 19:33:17] msiargextra: '
[04/26/2010 19:33:17] Rewrote process: setup.exe -s -f2 setup.log
[04/26/2010 19:33:18] --- NO FILE ---
Answered 04/26/2010 by: beljohns
Senior Yellow Belt

Please log in to comment
0
That doesn't look like an error to me. What does setup.log say in "C:\Program Files\KACE\KBOX\downloads\577" on the client?
Answered 04/26/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
The "[04/26/2010 19:33:18] --- NO FILE ---" is what I believed was stating it still couldn't find the file.

Going back to what you suggested, I selected "Configure Manually" and for the "Full Command Line" used: 'setup.exe -s f2 setup.log', and deselected "Run Command Only" and now it seems to be working. The debug.log output is as follows:
new Process setup.exe -s -f2 setup.log
[04/26/2010 19:43:47] msicmd: 'setup.exe'
[04/26/2010 19:43:47] msicmdextra: '-s -f2 setup.log'
[04/26/2010 19:43:47] msiarg: '
[04/26/2010 19:43:47] msiargextra: '
[04/26/2010 19:43:47] Rewrote process: C:\Program Files\KACE\KBOX\downloads\577\setup.exe -s -f2 setup.log

Thanks for pointing me in the right direction.
Answered 04/26/2010 by: beljohns
Senior Yellow Belt

Please log in to comment
0
new Process C:\Program Files\KACE\KBOX\downloads\577\setup.exe -s -f2 setup.log

The above is just telling you that is trying to execute "setup.exe -s -f2 setup.log" which just happens to be in C:\Program Files\KACE\KBOX\downloads\577\ since it is a managed install. So no, you do not need to worry about the output in the log showing a space in C:\Program Files

check that your zip file did not include a subdirectory and everything is at the root of the zip file
Answered 05/16/2010 by: KevinG
Purple Belt

Please log in to comment
0
For future post readers: don't forget covering the bases with this FAQ:
http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=5&id=968&artlang=en
Answered 05/17/2010 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity