/build/static/layout/Breadcrumb_cap_w.png

Troubleshooting a failed package install

We have created a package/task in Altiris and it fails when installing on the target machine.

The error message on the client is "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer Package."

If we run the command line from the software cache folder where the files reside, it installs with no errors.

This is the command-line

msiexec /i  "Qfiniti 3.5 SP1 Client.msi" /qb WEBSERVER="axa-etalk-qfnti" ADDLOCAL="Supervisor,G729Codec,SystemMonitor" /l*v C:\TEMP\Intall.txt

 

This is the log file contents.

=== Verbose logging started: 4/20/2012  12:45:52  Build type: SHIP UNICODE 5.00.7600.00  Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (C0:0C) [12:45:52:923]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (C0:0C) [12:45:52:923]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (C0:48) [12:45:52:938]: Resetting cached policy values
MSI (c) (C0:48) [12:45:52:938]: Machine policy value 'Debug' is 0
MSI (c) (C0:48) [12:45:52:938]: ******* RunEngine:
           ******* Product: Qfiniti 3.5 SP1 Client.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (C0:48) [12:45:52:938]: Note: 1: 2203 2: Qfiniti 3.5 SP1 Client.msi 3: -2147287038
MSI (c) (C0:48) [12:45:52:938]: MainEngineThread is returning 2
=== Verbose logging stopped: 4/20/2012  12:45:52 ===

We have also tried running task with a domain admin account.


0 Comments   [ + ] Show comments

Answers (4)

Posted by: GAKIS 9 years ago
Fourth Degree Green Belt
1

Try this, I have had this issue before the %~dp0 will use the path the batch file is located.

msiexec /i  "%~dp0Qfiniti 3.5 SP1 Client.msi" /qb WEBSERVER="axa-etalk-qfnti" ADDLOCAL="Supervisor,G729Codec,SystemMonitor" /l*v C:\TEMP\Intall.txt


Comments:
  • Thanks for the idea, but as listed above it did not solve our issue. - Zboy 9 years ago
Posted by: henrik80 9 years ago
Second Degree Blue Belt
1

Have you tried to run without the "" for the ADDLOCAL properties? I don't think its needed, it should be enough to just have the features delimited by comma.

msiexec /i  "Qfiniti 3.5 SP1 Client.msi" /qb WEBSERVER="axa-etalk-qfnti" ADDLOCAL=Supervisor,G729Codec,SystemMonitor /l*v C:\TEMP\Intall.txt


Comments:
  • you are correct the " were not needed but our problem was related to the path of the .msi file - Zboy 9 years ago
Posted by: pjgeutjens 9 years ago
Red Belt
1

Have you tried adding the full path to the MSI in the commandline? You might need to resort to scripting to resolve it if it's not predictable on the client.


Comments:
  • I changed the path of the destination download from the Symantec Management Agent Cache to a set location on the client, then put full path in the package command line. It now installs with no errors. Thanks! - Zboy 9 years ago
Posted by: piyushnasa 9 years ago
Red Belt
1

When you are running the command line from Deployment software, then it will search for the msi in default location. You need to check whether the package created in Altiris is poined to the correct folder. If there are sub folders then you need to give the exact paths..


Comments:
  • Thank you, It was path related. - Zboy 9 years ago

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