Not able to delete __Download's contents

(imported topic written by ltd200991)

Hi,

I had several issues this morning after a deployment last night… the client log files reported an error regarding not being able to delete the contents of the download directory. I understand that the download action automatically does this and if cannot complete the state sits at “pending-downloading”.

I restarted clients BES service but it seems the computer had to be restarted before the action would complete.

Is there any way around this? Is it possible to have the download action bypass the deleting of the __Download folder’s contents?

thanks!

(imported comment written by SystemAdmin)

the client will delete the __download directory before it start a new action, I’ve had this issue when I ran actions out of the __Download directory and they were still open or stuck, I fixed this issue by moving the files out of the __Download directory before I run anything

you can run a program like process explorer from microsoft and do a search for __Download to see whats out there running

(imported comment written by ltd200991)

i cant manually delete the files , says they are in use…

a little inconvienent when you are pushing updates to business users who are actively using their computers… must be some way around this issue?

(imported comment written by SystemAdmin)

What has the file open ?

(imported comment written by MattBoyd)

If you don’t mind me asking, what were you trying to deploy? It really sounds like whatever executable you were running got “stuck” and is still running in the background. This would certainly cause the action to fail and prevent the file from being deleted from the download folder.If you can figure out what process is stuck, you can use a taskkill.exe command to kill it and resolve your issue. You can also try rebooting the system.

I’ve occasionally seen this with the Office 2007 installer. If, for whatever reason, Office 2007 can’t be installed, a dialog box is displayed. Normally, a user would click OK and the installer process would exit. Since the install was running in the background through BigFix, the dialog box was essentially hidden and the process continued running in the background, sending the baseline to a grinding halt… until the computer was restarted.