Can't reinstall Office 2003

J

JeffPlax

All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
 
A

Ajith

Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
 
A

Ajith

Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
 
A

Ajith

Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
 
A

Ajith

Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
 
A

Ajith

Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
 
J

JeffPlax

Ajith,
Thanks for the advice. I tried all of the solutions you proposed to no
effect. I ended up reloading windows, and then reloading Office. I guess
that's pretty drastic, but I haven't cleaned out the registry in over a year,
and as a whole it wasn't performing well. Thanks again,

Jeff

Ajith said:
Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
Click to expand...
 
J

JeffPlax

Ajith,
Thanks for the advice. I tried all of the solutions you proposed to no
effect. I ended up reloading windows, and then reloading Office. I guess
that's pretty drastic, but I haven't cleaned out the registry in over a year,
and as a whole it wasn't performing well. Thanks again,

Jeff

Ajith said:
Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
Click to expand...
 
J

JeffPlax

Ajith,
Thanks for the advice. I tried all of the solutions you proposed to no
effect. I ended up reloading windows, and then reloading Office. I guess
that's pretty drastic, but I haven't cleaned out the registry in over a year,
and as a whole it wasn't performing well. Thanks again,

Jeff

Ajith said:
Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
Click to expand...
 
J

JeffPlax

Ajith,
Thanks for the advice. I tried all of the solutions you proposed to no
effect. I ended up reloading windows, and then reloading Office. I guess
that's pretty drastic, but I haven't cleaned out the registry in over a year,
and as a whole it wasn't performing well. Thanks again,

Jeff

Ajith said:
Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
Click to expand...
 
J

JeffPlax

Ajith,
Thanks for the advice. I tried all of the solutions you proposed to no
effect. I ended up reloading windows, and then reloading Office. I guess
that's pretty drastic, but I haven't cleaned out the registry in over a year,
and as a whole it wasn't performing well. Thanks again,

Jeff

Ajith said:
Jeff,

Looks like, you have modified the setup.ini file (chained install section).
Why dont you try running the pro11.msi or std11.msi directly instead of
setup.exe.

If it still fails, Try windows installer clean up utility to remove office.
http://support.microsoft.com/?kbid=290301

then reinstall office using setup.exe or pro11.msi or std11.msi

good luck,
Ajith


JeffPlax said:
All,
Recently had to repair a Windows XP SP2 installed on my computer using XP
SP1 CD due to problems with other software. The OS repair worked OK, but it
has corrupted registry beyond belief. Office was installed and functional
prior to reinstallation, but now I can't even start the setup program to
remove and reinstall office let alone repair it. When I start the setup
program, I get an error "This patch package could not be opened. Verify that
the patch package exists and that you can access it, or contact the
application vendor to verify that this is a valid windows installer package."
I've reinstalled all of the MSXML versions and the Windows Installer 3.1 -
they seem to be working fine. Upon further examination of the setup log
files I see the following in the Microsoft Office 2003 Setup(0022).txt file:

Successfully launched MsiExec....
8/28/2006 6:26:33 AM Chained install return code: 1619

Exit code was an error.
Shutting down chained setup processing.
Set Verbose logging for subsequent setup.


***** Setup exits
8/28/2006 6:26:33 AM
(return = 1619)"

checking the associated Task(0001) file I see the following :

=== Verbose logging started: 8/28/2006 6:26:30 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: D:\WINDOWS\system32\msiexec.exe ===
MSI (c) (EC:48) [06:26:30:718]: Resetting cached policy values
MSI (c) (EC:48) [06:26:30:718]: Machine policy value 'Debug' is 0
MSI (c) (EC:48) [06:26:30:718]: ******* RunEngine:
******* Product:
******* Action:
******* CommandLine: **********
MSI (c) (EC:48) [06:26:30:718]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (EC:48) [06:26:30:718]: Grabbed execution mutex.
MSI (c) (EC:48) [06:26:30:781]: Cloaking enabled.
MSI (c) (EC:48) [06:26:30:781]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (EC:48) [06:26:30:796]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (90:64) [06:26:30:812]: Grabbed execution mutex.
MSI (s) (90:60) [06:26:30:812]: Resetting cached policy values
MSI (s) (90:60) [06:26:30:812]: Machine policy value 'Debug' is 0
MSI (s) (90:60) [06:26:30:812]: ******* RunEngine:
******* Product: E:\
******* Action:
******* CommandLine: **********
MSI (s) (90:60) [06:26:30:812]: Note: 1: 2203 2: E:\ 3: -2147287037
MSI (s) (90:60) [06:26:30:812]: MainEngineThread is returning 3
MSI (c) (EC:48) [06:26:30:812]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:48) [06:26:30:812]: MainEngineThread is returning 3
=== Verbose logging stopped: 8/28/2006 6:26:30 ===

I should mention I'm running Setup.exe /fvm

Any ideas how I can pull my chestnuts out of the fire here?

Thanks,
Jeff
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

outlook 2007 bcm windows 7 0
Install fails without obvious error 2
BCM install problem on Win7 4
Office 2003 Standard MultiLingual User Interface (MUI) installation 24
Office (Outlook) 2003 MSI Failure 48
cann't upgrade my office SME (Including outlook with BCM) 3
installation and KB95449 - MSXML 6 Service Pack 2 9
install business contact manager fail 0

Top