Microsoft Office 2003 chained installation is not successful with Prefix form of secure transform (818241)
The information in this article applies to:
- Microsoft Office Professional Edition 2003
- Microsoft Office Basic Edition 2003
- Microsoft Office Small Business Edition 2003
- Microsoft Office Standard Edition 2003
- Microsoft Office Students and Teachers Edition 2003
SYMPTOMSWhen you try to run a chained installation of Microsoft Office 2003, the chained programs may not be installed successfully. You chain the installation packages or executable files of additional programs to the Office Setup.ini file, but the chained programs may not be installed. A chained installation is typically run in quiet mode with the /q switch. In quiet mode, you do not receive an error
message when this problem occurs. However, if you run the chained installation without the
/q switch, you receive the following error message:
Error applying transforms. Verify that the specified
transform paths are valid. CAUSEThis problem occurs if you use the Prefix form of
a secure transform by including an at sign (@) or a pipe symbol (|) as the first character in the path of the .mst
file.
If you append an at sign to the name of the .mst file to
indicate a relative path secure transform, the at sign is
treated as part of the .mst file name. Therefore, the transform is not found.
If you append a pipe symbol to the path of the .mst file to
indicate a secure transform, Setup.exe does not recognize it as a full path
transform. The transform is treated as a relative path transform with the
pipe symbol as the first character. Setup.exe appends the
current path of the source location of the primary install to a relative path
transform. The result is a path that is not valid. The transform is not found.
WORKAROUNDTo work around this problem, use the Property form of Secure
Transforms. To do this, add the TRANSFORMSSECURE property; do not reference the .mst file with an at sign or a pipe symbol. In the Chained install section of the Setup.ini
file, add TRANSFORMSSECURE=1 to the current CmdLine= line. To do, use the following examples.
Example 1 Instead of the following
[ChainedInstall_1] path=\\AppServer\Office11\Pro11.MSI
mst=@accounting.mst tasktype=msi cmdline=REBOOT=Suppress
use the following:
[ChainedInstall_1] path=\\AppServer\Office11\Pro11.MSI
mst=accounting.mst tasktype=msi cmdline=REBOOT=Suppress
TRANSFORMSSECURE=1
Example 2Instead of the following
[ChainedInstall_1]
path=\\AppServer\Office11\Pro11.MSI
mst=|\\AppServer\Office11\Custom\accounting.mst tasktype=msi
cmdline=REBOOT=Suppress
use the following:
[ChainedInstall_1] path=\\AppServer\Office11\Pro11.MSI
mst=\\AppServer\Office11\Custom\accounting.mst tasktype=msi
cmdline=REBOOT=Suppress TRANSFORMSSECURE=1 STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 8/29/2006 |
---|
Keywords: | kbDeployment kbsetup kbSecurity kbwindowsinstaller kbprb KB818241 kbAudITPRO |
---|
|