Status Code 32
Hello,
I created a script to delete two source installers from the $(KACE_DEPENDENCY_DIR) folder. I am trying to delete the installer for Office Standard 2016 and the installer for Office 365. The script works fine in that it uninstalls the source files from the folders. However, the script returns a "Failed" job and the log shows Error Code: 0 and Status Code: 32. Can someone tell me what Status Code 32 means and how I can have the script to return a Successful outcome?
Thank you,
Dinah
I noticed in the Debug Log, runkbot doesn't return a completed exit code.
Answers (3)
Hi,
I have a question before I can help you. If you say you want to delete the Office installation files from the dependency dir, I assume you install with SMA both office version to your clients right? How are you doing that? With a script that calls the setup.exe from a dependency or how are you doing the installation? Normally the SMA cleans up all files needed for an installation depending on the configuration of the script.
Nevertheless, did you try within your script in the verify section the search for files command which can also delete folders? Maybe this works better in this case.
Cheers
Sven
Hi Sven,
Yes, we installed Office 2016 using SMA. We are also using SMA to install Office 365. The script to uninstall calls out setup.exe and the same with the install of Office 365. So we have 2 diff scripts (uninstall and install). We are using Task Chain to run both so it copies the source to its own dependency_dir folder. We have the 3rd script (not part of the Task Chain) to delete the source files on the dependency_dir, which we will run after the install of Office 365. We thought the SMA would clean up all the files but we found out that it is not deleting the source after the successful installation. Quest suggested to create a separate script to delete the source.
I'm sorry but I'm not sure what you mean by search for files command which can also delete folder?
So, the files do get deleted (both O2016 and O365), but SMA returns a Status Code of 32 and a status of Failed instead of Successful (even though it did delete the files).
Thank you for replying to my post.
Dinah
Comments:
-
Ok so when you copy the files with another script it will not clean it up during the installation. Was there a problem with uploaded files to the script or to the software inventory where you had to separate it to another script?
If you are in an online kscript and add a task to it, in the verify section when you add a new step you can search for "search" and you will see "search file system" where you are also able to delete folders. This might be better and gives better return codes.
My goal would be actually that you do not need to have that delete script at all because normally if you use a script to install something, we use already uploaded files to the appliance which will be downloaded to the clients and after the installation the agent cleans it up automatically.
If it is easier, you can also send me an email to sven.hain@quest.com with some screenshots from your scripts or maybe the exported scripts so that I get a better understanding on how you exactly configured those scripts. - sven.hain 9 months ago
Thanks, Sven for replying. Sorry I haven't been able to respond until now. I got a little busy here with other projects.
I thought SMA would also clean up after the install but we found out it was leaving the original installers in the $(KACE_DEPENDENCY_DIR).
I haven't had much time to test it again.
I'll start it up again. But for now, I'll mark this complete. We can do a cleanup after once we've upgraded everyone to O365.
Thank you again.
Dinah