Office installation fails with custom transform file

[eots]

I created an Administrative installation point on the network for Office 2003
Pro and created a custom transform file with the Custom Installation Wizard.
Every time the installation includes the transform file it fails immediately
after the "gathering required information" stage and automatically backs out
of the installation. The installation will only complete successfully if I
don't include the transform file. I also have a custom installation for
Office 2003 Standard and it runs fine with its transform file.

What is the problem with Office 2003 Professional? I recreated my
installation point and transform file but it still fails.

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?

 

[Gerry Hickman]

Hi,

This is odd; I use different TRANSFORMS with o2k3pro all the time and
have never seen this. I have some for home users and some for corporate.
If you enabled logging on the CMD line, you should get two log files;
one for SETUP.EXE and one for MSIEXEC; did you look at them to see if
there are any clues?

If you need help with this, I suggest you post the EXACT command line
you used.

I assume you slipstreamed the latest service pack into the AIP and
created the TRANSFORM afterwards based on the newly updated MSI?