Systems Management Question

Project 2003 via sms2003 mst

07/31/2006 6645 views

i created a mst file with ORK.

In SMS2003 i created a new Package from Definition:
msiexec.exe /q ALLUSERS=2 /m MSISWL0I /i "PRJPROE.MSI" TRANSFORMS="MSProject2003.MST" /l* C:\install\msproject2003.log

Is the command wrong? I tried the mst without sms but with setup.exe TRANSFORMS="MSProject2003.MST"
and that worked. But what about SMS ?

Error is:

The program for advertisement "MUC20090" failed ("MUC0004A" - "MS Project 2003 - per system unattend"). A failure exit code of 1619 was returned.

Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 1619 is considered a failure.
Solution: For more information on the exit code, refer to the documentation for the program you are distributing.

Thanks for your help,
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

You're not running this with user permissions are you?

Also, does C:\Install exist on the target machine?
Answered 08/22/2006 by: Bladerun
Green Belt

You should specify where the msi is


Unless you are including the files in the distribution, check that you included the files in the package.
Answered 08/22/2006 by: Rhys
Orange 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


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