K
kinryuu
I'm trying to figure this out. It's a tough one.
If I try to install Office 2003 Pro or Std, the Setup will hang for a
very long time at the screen that says "Preparing Microsoft Office
Professional Edition 2003 Installation Wizard..." The last entry in the
MSI log is this when it freezes:
MSI (c) (F0:00) [14:25:09:059]: Invoking remote custom action. DLL:
C:\DOCUME~1\username\LOCALS~1\Temp\MSI33C.tmp, Entrypoint:
DoDialogSequence
Action ended 14:25:09: DoDialogSequence. Return value 3.
MSI (c) (F0:40) [14:25:09:075]: Doing action: SetupDW
Action start 14:25:09: SetupDW.
MSI (c) (F0:30) [14:25:09:075]: Invoking remote custom action. DLL:
C:\DOCUME~1\username\LOCALS~1\Temp\MSI33D.tmp, Entrypoint: SetupDWMain
Action ended 14:25:09: SetupDW. Return value 1.
Eventually, it will stop (after about 15-30 minutes) and this is what
the log says at the very end:
Action ended 14:25:09: INSTALL. Return value 3.
MSI (c) (F0:4C) [14:34:44:155]: Destroying RemoteAPI object.
MSI (c) (F0:FC) [14:34:44:155]: Custom Action Manager thread ending.
~
[A WHOLE BUNCH OF PROPERTIES SNIPPED]
~
=== Logging stopped: 3/14/2005 14:34:44 ===
MSI (c) (F0:40) [14:34:44:373]: Note: 1: 1708
MSI (c) (F0:40) [14:34:44:373]: Product: Microsoft Office Professional
Edition 2003 -- Installation operation failed.
MSI (c) (F0:40) [14:34:44:420]: Grabbed execution mutex.
MSI (c) (F0:40) [14:34:44:420]: Cleaning up uninstalled install
packages, if any exist
MSI (c) (F0:40) [14:34:44:420]: MainEngineThread is returning 1603
=== Verbose logging stopped: 3/14/2005 14:34:44 ===
I have installed tons and tons and tons of software. Here's the weird
part, if I log in as a local admin profile, the setup will work, but
the setup for my domain account will not work. I have tried deleting my
locally stored profile (we don't use roaming profiles) and re-logging
in to recreate the profile, but I get the exact same results. Other
users on the domain have no problem installing office. I can even
install office on another machine with my same user account, so that
tells me it's not a problem with my domain account. Yet... it makes no
sense.
If I try to install Office 2003 Pro or Std, the Setup will hang for a
very long time at the screen that says "Preparing Microsoft Office
Professional Edition 2003 Installation Wizard..." The last entry in the
MSI log is this when it freezes:
MSI (c) (F0:00) [14:25:09:059]: Invoking remote custom action. DLL:
C:\DOCUME~1\username\LOCALS~1\Temp\MSI33C.tmp, Entrypoint:
DoDialogSequence
Action ended 14:25:09: DoDialogSequence. Return value 3.
MSI (c) (F0:40) [14:25:09:075]: Doing action: SetupDW
Action start 14:25:09: SetupDW.
MSI (c) (F0:30) [14:25:09:075]: Invoking remote custom action. DLL:
C:\DOCUME~1\username\LOCALS~1\Temp\MSI33D.tmp, Entrypoint: SetupDWMain
Action ended 14:25:09: SetupDW. Return value 1.
Eventually, it will stop (after about 15-30 minutes) and this is what
the log says at the very end:
Action ended 14:25:09: INSTALL. Return value 3.
MSI (c) (F0:4C) [14:34:44:155]: Destroying RemoteAPI object.
MSI (c) (F0:FC) [14:34:44:155]: Custom Action Manager thread ending.
~
[A WHOLE BUNCH OF PROPERTIES SNIPPED]
~
=== Logging stopped: 3/14/2005 14:34:44 ===
MSI (c) (F0:40) [14:34:44:373]: Note: 1: 1708
MSI (c) (F0:40) [14:34:44:373]: Product: Microsoft Office Professional
Edition 2003 -- Installation operation failed.
MSI (c) (F0:40) [14:34:44:420]: Grabbed execution mutex.
MSI (c) (F0:40) [14:34:44:420]: Cleaning up uninstalled install
packages, if any exist
MSI (c) (F0:40) [14:34:44:420]: MainEngineThread is returning 1603
=== Verbose logging stopped: 3/14/2005 14:34:44 ===
I have installed tons and tons and tons of software. Here's the weird
part, if I log in as a local admin profile, the setup will work, but
the setup for my domain account will not work. I have tried deleting my
locally stored profile (we don't use roaming profiles) and re-logging
in to recreate the profile, but I get the exact same results. Other
users on the domain have no problem installing office. I can even
install office on another machine with my same user account, so that
tells me it's not a problem with my domain account. Yet... it makes no
sense.