Microsoft KB Archive/263402

From BetaArchive Wiki
Knowledge Base


Article ID: 263402

Article Last Modified on 10/27/2006



APPLIES TO

  • Microsoft Systems Management Server 2.0 Service Pack 2



This article was previously published under Q263402

SYMPTOMS

When you try to run an .msi file by specifying the name of the file at a command prompt, the Msiexec.exe program cannot process the .msi file.

CAUSE

When you run .msi files by just specifying the name of the .msi file, no command prompt parameters are passed to the Msiexec.exe program, so the Msiexec.exe program cannot process the .msi file.

WORKAROUND

To resolve this problem, obtain the latest service pack for Systems Management Server version 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

236325 How to Obtain the Latest Systems Management Server 2.0 Service Pack


To work around this problem, include an explicit call to the Msiexec.exe program at the command prompt when you want to advertise programs. You must also type the appropriate command-line switch with the Msiexec.exe program, such as /I (to install) or /f (to repair the installation). For a complete list of command-line switches that you can use with the Msiexec.exe program, view the following Microsoft Knowledge Base article:

227091 Command-Line Switches for the Microsoft Windows Installer Tool


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Systems Management Server 2.0 Service Pack 4.

MORE INFORMATION

You can run Windows Installer packages (.msi packages) by either double-clicking the .msi file itself or by calling it by using the Msiexec.exe program from a command prompt.

When you use System Management Server (SMS) 2.0, you can advertise and run .msi packages only by explicitly calling the command prompt and specifying the name of the .msi file that you want to run.


Additional query words: prodsms c line

Keywords: kbbug kbnofix kbsms200presp3 kbsms200presp4fix kbsoftwaredist KB263402