toddthejackass
asked on
Problems installing Office 2007 on a 64-bit Windows 2003 Terminal Server
Experts,
Am having an issue where Office 2007 will not install on a 64-bit Windows 2003 Terminal Server. When I try to install (through Add/Remove programs, or through using the user /install mode), the setup.exe crashes immediately with Setup did not complete successfully. We are sorry for the inconvenience.
The error report is below.
The computer is a Windows Server 2003 R2 x64 with SP2. Office 2007 Pro with a Volume License. The Server is a Terminal Server that also (shudder) is the Terminal Server Licensing server as well.
I have tried the following:
Making sure all users are logged out and installing from console
Changing to the user /install
Installing from the Office64MUI.msi / Office64MUISet.msi
Installing it on another x64 server (successfully)
Installing after a fresh reboot from console
I'm guessing it has to do with Terminal Services. Any input would be much appreciated.
Thanks!
-----------------
PERF: TickCount=512303640 Name=OBootStrapper::Run Description=Begin function
Terminal Server detected
Operating System version: 5.2.3790 Service Pack 2. Platform ID: 2
Running on a 64-bit operating system.
Command line: "C:\0ffice2007install\setu p.exe"
No command line arguments given
Verify file signature in "C:\0ffice2007install\setu p.exe"
Verify file signature in "C:\0ffice2007install\ProP lus.WW\OSE TUP.DLL"
Using setup controller dll at [C:\0ffice2007install\ProP lus.WW\OSE TUP.DLL].
PERF: TickCount=512304359 Name=OBootStrapper::Run Description=Calling RunSetup
Opening log file C:\DOCUME~1\ADMINI~1\LOCAL S~1\Temp\6 \SetupExe( 2010113011 310914AC). log.
========================== ========== ========== ========== ========== =======
PERF: TickCount=512304359 Name=RunSetup Description=Begin function
Terminal Server detected
Catalyst execution began: 11/30/2010 11:31:09.
Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
Searching for updated versions of resource files under the 'updates' folder [C:\0ffice2007install\upda tes].
Found [0] resource files under the update folder.
Searching for default versions of resource files under the folder [C:\0ffice2007install].
Resource File Manager : Found (CultureTag=en-US) resource file at [C:\0ffice2007install\Offi ce.en-us\O SETUPUI.DL L].
Found [1] resource files under the default folder.
Resource File Manager : Current user's LCID is [1033].
Resource File Manager : Selecting resource file (File=C:\0ffice2007install \Office.en -us\OSETUP UI.DLL) for CultureTag [en-US].
Running in [InstallExecutionMode]. Run from TEMP folder at [C:\DOCUME~1\ADMINI~1\LOCA LS~1\Temp\ 6\Setup000 014ac].
Loaded resource file [C:\DOCUME~1\ADMINI~1\LOCA LS~1\Temp\ 6\Setup000 014ac\OSET UPUI.DLL] (CultureTag=en-US).
Loaded Dll : C:\0ffice2007install\ProPl us.WW\OSET UP.DLL.
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
Error: failed MsiEnumProducts ErrorCode: 2(0x2).
Catalyst execution finished: 11/30/2010 11:31:09. Return code: 30015. Exception caught: ErrorCodeOnly.
PERF: TickCount=512304921 Name=RunSetup Description=End function
========================== ========== ========== ========== ========== =======
Am having an issue where Office 2007 will not install on a 64-bit Windows 2003 Terminal Server. When I try to install (through Add/Remove programs, or through using the user /install mode), the setup.exe crashes immediately with Setup did not complete successfully. We are sorry for the inconvenience.
The error report is below.
The computer is a Windows Server 2003 R2 x64 with SP2. Office 2007 Pro with a Volume License. The Server is a Terminal Server that also (shudder) is the Terminal Server Licensing server as well.
I have tried the following:
Making sure all users are logged out and installing from console
Changing to the user /install
Installing from the Office64MUI.msi / Office64MUISet.msi
Installing it on another x64 server (successfully)
Installing after a fresh reboot from console
I'm guessing it has to do with Terminal Services. Any input would be much appreciated.
Thanks!
-----------------
PERF: TickCount=512303640 Name=OBootStrapper::Run Description=Begin function
Terminal Server detected
Operating System version: 5.2.3790 Service Pack 2. Platform ID: 2
Running on a 64-bit operating system.
Command line: "C:\0ffice2007install\setu
No command line arguments given
Verify file signature in "C:\0ffice2007install\setu
Verify file signature in "C:\0ffice2007install\ProP
Using setup controller dll at [C:\0ffice2007install\ProP
PERF: TickCount=512304359 Name=OBootStrapper::Run Description=Calling RunSetup
Opening log file C:\DOCUME~1\ADMINI~1\LOCAL
==========================
PERF: TickCount=512304359 Name=RunSetup Description=Begin function
Terminal Server detected
Catalyst execution began: 11/30/2010 11:31:09.
Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
Searching for updated versions of resource files under the 'updates' folder [C:\0ffice2007install\upda
Found [0] resource files under the update folder.
Searching for default versions of resource files under the folder [C:\0ffice2007install].
Resource File Manager : Found (CultureTag=en-US) resource file at [C:\0ffice2007install\Offi
Found [1] resource files under the default folder.
Resource File Manager : Current user's LCID is [1033].
Resource File Manager : Selecting resource file (File=C:\0ffice2007install
Running in [InstallExecutionMode]. Run from TEMP folder at [C:\DOCUME~1\ADMINI~1\LOCA
Loaded resource file [C:\DOCUME~1\ADMINI~1\LOCA
Loaded Dll : C:\0ffice2007install\ProPl
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
Error: failed MsiEnumProducts ErrorCode: 2(0x2).
Catalyst execution finished: 11/30/2010 11:31:09. Return code: 30015. Exception caught: ErrorCodeOnly.
PERF: TickCount=512304921 Name=RunSetup Description=End function
==========================
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER