Help please! Office 2003 SP2 update to install point causes client installations to fail.

[tony.vo]

Hi,

I've update my admin install point to Office 2003 SP2, both Pro11 and
OWC11 have been updated. The problem is when people try to install
using a shortcut to a tranform, the install fails. The status bar goes
along for a minute and then the status bar goes backwards then the
installer disappears. Any help will be greatly appreciated!

Tony

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Donnie]

Tony,

I have the same problem I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log
then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though. Can anyone shed some light on our problem?

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.

 

[Gerry Hickman]

Hi Donnie,

I have the same problem

I don't think you do, he was talking about a TRANSFORM (and you are not
supposed to use a transform when doing RECACHE and REINSTALL
[FearureList] to client boxes).

I'm trying to setup Office 2003 SP2 using the Admin
share point that we have and the custom MSI. I run this command msiexec.exe
/p "D:\Office SP2\Office 2003 SP2\whatever.msp" /a
"D:\packages\office2003\whatever.msi" /qb /lv* D:\office2003.log

Here you are talking about patching an AIP, the original poster was
talking about the matter of rolling out to clients _after_ patching his
AIP. Anyway, terms such as 'whatever.msp' are hopeless. You need to be
clear or no one can help you.

then it progresses and then I get an erroe and then the MSI file disappears.
I saw something on MS website about possibly needing the latest Windows
Installer 3.1. I have not tried loading that on the server where the package
resides yet though.

If you're running MSIEXEC on the server I'd suggest using MSIEXEC 3.1,
but you can also patch an AIP from an Admin workstation with 3.1 using
UNC paths. Simple answer - install 3.1 anyway. We did a blanket install
to all our boxes.