Office 2003 Setup May Not Run Correctly When You Use the CreateProcess() API (817111)



The information in this article applies to:

  • Microsoft Office 2003, All Editions, when used with:
    • the operating system: Microsoft Windows XP
    • the operating system: Microsoft Windows 2000

SYMPTOMS

When you use the CreateProcess() application programming interface (API) to run Microsoft Office 2003 Setup, the Setup routine may not function as expected. You may experience the following symptoms:
  • Setup may not run in quiet mode as specified.
  • Logging functions may not occur.
  • You may receive an error message about an invalid command-line parameter.
The symptoms that you experience depend on the order of the Setup parameters.

CAUSE

This problem occurs because the CreateProcess() API removes the first parameter of the Setup command line. The CreateProcess() API expects the first parameter to be a reference to the program executable file (.exe file).

WORKAROUND

To work around this problem, modify your command line to move the program executable statement so that it is the expected first parameter.

For example, suppose that you use the following command line to run Setup in quiet mode:

\\server\share\Setup.exe /qb- PIDKEY=pidkey TRANSFORMS=\\server\share\filename.mst /lv* C:\Temp\Log.txt



To modify this command line, add a Null string, as in the following example:

Null \\server\share\Setup.exe /qb- PIDKEY=pidkey TRANSFORMS=\\server\share\filename.mst /lv* C:\Temp\Log.txt

Note You can use any literal string for Null.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Office 2003.

Modification Type:MinorLast Reviewed:1/10/2006
Keywords:kbpending kbBug KB817111 kbAudEndUser