06/19/2012 5921 views

I have recently been having some headaches with Reader and have a script that runs adobe's cleaner to remove all traces of reader, sleep for 30 seconds, and then installs reader 10.1.3

For some of the machines the script is going wrong in a few ways. In some cases it seems that the cleaning software fails to run, and in other cases the adobe installation doesn't run.

Looking at the local dependency directory, I can see that some of the files are failng to download. looking at runkbot.log I can see messages logged indicating a access failure when downloading dependencies.

If I run the script again, it usually is able to download all the depencies, and runs fine. What could be causing this issue?

In one case I found one of the files as a ".part" file, and everytime I tried to run the script it woudl fail to finish the download. Once I deleted the .part file I was able to run the script successfully.

Has anybody else seen any issues with scripts and downloading dependencies? 

0 Comments   [ + ] Show comments


Community Chosen Answer


on the segment of our network that was miss-configured.  They had a trunk set with a different setting at each end and all machines down steam did things like this.

Answered 06/20/2012 by: SMal.tmcc
Red Belt

All Answers


I agree - I would consider looking into network issues first.  Just a couple of things to test:

Can you copy the files manually to one of the problem PCs without issue? 

Can a problem PC download the file from the KBOX share without issue?  Just put the file(s) in the kbox\client share for testing.


Answered 06/21/2012 by: jverbosk
Red Belt

  • I am having this same issue with one 2 of my scripts (no others). Both scripts point to files that I uploaded with a software item so they get put in the downloads folder of the kace file dir. I know it isn't a network problem because nothing else has trouble communicating with the machine in question and the same problem presents itself on other computers. Does anyone know of a fix?
  • If you are tying this to a software item, have you considered setting this up as a Managed Install (Distribution) item?

    On the script side, other things to play with are the Script Type, Supported Operating Systems and Run As settings. If it's your own script, you'll also need to make sure it's set up with the correct parameters in order to run (of course...).