Silent Office 2003 Install (EE) with Transform fails

[Zachary Boldt]

I am currently getting the same errors as I saw
previously on this newsgroup, but did not see any fix
posted. Here may be some additional information, if
anybody can help it would be great!!!

1. We recently upgraded from Office 2000 / 97 to Office
XP with a seamless upgrade using chained / transformed
install without problems. We are now starting to test
upgrading to Office 2003 Enterprise Edition.

2. When attempting to upgrade some systems to 2003, we
get an error if an MST is applied, but it works fine from
a standard administrative installation point. If the MST
is applied, whether through command-line arguments or
through setup.ini modification, the result is the same:
a. If Office XP is still installed, it attempts to
remove the previous installation
b. Somewhere after the configuring stage, it will fail
with nothing other than "there was an error" message.

---> If there is an MST applied, it fails!! <---

If there is NOT an MST applied, but rather we just use a
standard administrative installation, office 2003 loads
correctly, and follows the default behaviour.

The problem we have is that we need to have a COMPLETE
install of Office 2003, which you can't do silently
without an MST, as far as I know. Am I wrong here??

Error message from ...setup(0001).txt:
Successfully launched MsiExec....
11/20/2003 9:39:04 AM Chained install return code: 1603

From the ...setup(0001)_Task(0001).txt:
Action start 9:35:37: ISCacheLockedFeatureStates.
DEBUG: Error 2769: Custom Action
ISCacheLockedFeatureStates did not close 3 MSIHANDLEs.
An internal error has occurred:
(ISCacheLockedFeatureStates 3 ).
Action ended 9:35:37: ISCacheLockedFeatureStates. Return
value 1.
Action start 9:35:43: ISResetLockedFeatureStates.
DEBUG: Error 2769: Custom Action
ISResetLockedFeatureStates did not close 1 MSIHANDLEs.
An internal error has occurred:
(ISResetLockedFeatureStates 1 ).
Action ended 9:35:45: ISResetLockedFeatureStates. Return
value 1.
=== Logging stopped: 11/20/2003 9:39:03 ===
MSI (s) (20:AC): Product: Microsoft Office Professional
Edition 2003 -- Installation operation failed.

I am using the most recent download of the Office 2003
Resource Kit Tools, and creating the MST from the Custom
Installation Wizard.

Is there a problem with the CIW and it's creating a
corrupt MST file?

The results above are consistent amongst several
different systems, a mix of Win2000 and WinXP, all with
the most current CERTS.

I have attempted creating MST's from both the default CD
copy on our network and from the Admin Install point, and
the results continue to be consistent.

Any help would be appreciated!

Thx,
ZAB

 

[Bob Buckland ?:-\)]

Hi Zab,

What are the changes/selections you've made in the
MST file? Are you including any files to be be copied/
loaded as part of the installation?

What is the command line you are using to run the
install?

Does the profile you're installing under have elevated
privileges?

============
I am currently getting the same errors as I saw
previously on this newsgroup, but did not see any fix
posted. Here may be some additional information, if
anybody can help it would be great!!!

1. We recently upgraded from Office 2000 / 97 to Office
XP with a seamless upgrade using chained / transformed
install without problems. We are now starting to test
upgrading to Office 2003 Enterprise Edition.

2. When attempting to upgrade some systems to 2003, we
get an error if an MST is applied, but it works fine from
a standard administrative installation point. If the MST
is applied, whether through command-line arguments or
through setup.ini modification, the result is the same:
a. If Office XP is still installed, it attempts to
remove the previous installation
b. Somewhere after the configuring stage, it will fail
with nothing other than "there was an error" message.

---> If there is an MST applied, it fails!! <---

If there is NOT an MST applied, but rather we just use a
standard administrative installation, office 2003 loads
correctly, and follows the default behaviour.

The problem we have is that we need to have a COMPLETE
install of Office 2003, which you can't do silently
without an MST, as far as I know. Am I wrong here??

Error message from ...setup(0001).txt:
Successfully launched MsiExec....
11/20/2003 9:39:04 AM Chained install return code: 1603

From the ...setup(0001)_Task(0001).txt:
Action start 9:35:37: ISCacheLockedFeatureStates.
DEBUG: Error 2769: Custom Action
ISCacheLockedFeatureStates did not close 3 MSIHANDLEs.
An internal error has occurred:
(ISCacheLockedFeatureStates 3 ).
Action ended 9:35:37: ISCacheLockedFeatureStates. Return
value 1.
Action start 9:35:43: ISResetLockedFeatureStates.
DEBUG: Error 2769: Custom Action
ISResetLockedFeatureStates did not close 1 MSIHANDLEs.
An internal error has occurred:
(ISResetLockedFeatureStates 1 ).
Action ended 9:35:45: ISResetLockedFeatureStates. Return
value 1.
=== Logging stopped: 11/20/2003 9:39:03 ===
MSI (s) (20:AC): Product: Microsoft Office Professional
Edition 2003 -- Installation operation failed.

I am using the most recent download of the Office 2003
Resource Kit Tools, and creating the MST from the Custom
Installation Wizard.

Is there a problem with the CIW and it's creating a
corrupt MST file?

The results above are consistent amongst several
different systems, a mix of Win2000 and WinXP, all with
the most current CERTS.

I have attempted creating MST's from both the default CD
copy on our network and from the Admin Install point, and
the results continue to be consistent.

Any help would be appreciated!

Thx,
ZAB >>
--
I hope this helps you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

The Office 2003 System parts explained
http://microsoft.com/uk/office/editions.asp

 

[Zachary A. Boldt]

Basically, the changes are very limited. We are setting
it to remove all previous versions, then install
everything (not just the defaults) locally, with no user
interaction. There are no extra inclusions either
registry or file, although eventually we would like to
import a profile that defaults Outlook to show the Folder
List rather than the Mail view by default due to the Mail
view not showing the Public Folders by default, but at
this point we are not testing that yet.

We have tried a couple of shortcut methods:
1) "\\%server%\%sharename%\office2003\setup.exe"
TRANSFORMS="\\%server%\%sharename%\office2003
\custom1.MST" /qb+!

2) \\%server%\%sharename%\Office2003
\Office\SETUP.EXE /qb! /settings \\%server%\%sharename%
\Office2003\ofcSetup.ini
(This one with a modified Setup.ini calling the MST)

3) %windir%\system32\msiexec.exe /i "\\%server%\%
sharename%\office2003\PRO11.MSI" TRANSFORMS="\\%server%\%
sharename%\office2003\custom1.MST" /qb+!

Preferably, when we go to distribute, we would like to
import the MSI directly into CA's SDO then modify it with
the MST, but for the purposes of our testing this is not
being done at this point - we are a long way from that!

The account we are using is a admin on the local box, and
has full perms on the installation point.

Thx,

ZB

-----Original Message-----
Hi Zab,

What are the changes/selections you've made in the
MST file? Are you including any files to be be copied/
loaded as part of the installation?

What is the command line you are using to run the
install?

Does the profile you're installing under have elevated
privileges?

============
<<"Zachary Boldt" <[email protected]> wrote in

message news:[email protected]...