/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Installing on KACE

01/22/2019 483 views

So I am having a problem with my script running. Everything is the same but one fails and one executes successfully. I looked at both logs and notice a slight difference but I am not sure how to fix it.

The successful one looks like this:

Running as SYSTEM
Directory DOES exist: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\266
Launched Process: WindowsSensor.exe

The failed one looks like this:

Running as SYSTEM
Directory DOES exist: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\266
Creating process returned non-zero: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\266\WindowsSensor.exe /install /quiet /norestart CID=200FBCCA0FB9433D8E21D5E071D99598-28: (0) The operation completed successfully.
Error Code: 0
Status Code: 1638

Does anyone know how to fix this? What the error code or status codes means?

Answer Summary:
0 Comments   [ + ] Show comments

Comments


Answer Chosen by the Author

0

Error 1638 means another version of the software is already installed. 

See https://support.microsoft.com/en-us/help/3077464/error-1638-another-version-of-this-program-is-already-installed-when-y

Answered 01/22/2019 by: AbhayR
Red Belt

  • Thanks for your help I will have to check if a older version was already installed

All Answers

0

try to manually install on one that is failing and see if you get this error

MSI error code 1638: “Another version of this product is already installed”


Answered 01/22/2019 by: SMal.tmcc
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ