msiexec.exe Application Error "The instruction at "0x00f33fe8" referenced memory at "0x00f33fe8". Th

[Edward Ray]

I get an error box with this message (different memory reference)when I try
to install ANY program on my Dell Laptop running Windows XP SP2 (all patches
as of July applied) and running in a Windows 2003 native Active Directory
domain. The user attempt install has Local Admin privileges on the machine.

By ANY program I mean Ms Project Pro 2003, MS FrontPage 2003 and MS Visio
2003. These were the only ones I tried.

I tried copying them to the hard drive, same error. Actually tried an old
MS project 2000 stored on the DFS root share, same error. was able to
replicate problem on another Dell Laptop same model. This error did not
appear on other Windows XP laptops, desktops and Windows 2003 workstation.

If anyone has seen this problem while trying to install MS programs and has
a solution, please let me know. This smells of a Registry key missetting.

I have enclosed one of the log files from the project install below. It has
an Chained install return code: -1073741819

I looked on http://support.microsoft.com/default.aspx?scid=kb;en-us;826511
but could not find any helpful hints.

Regards,

Edward W. Ray

<<
c:\verboselog.txt
Detected Windows Info:
PlatformId = 2
MajorVersion = 5
MinorVersion = 1
ServicePackLevel = 2
- - - - - - - - - - - - - - - - - - - - - - -
Launch Setup
7/25/2005 10:10:34 AM
Recognized command line switch L*v
** Switching to new log file passed on command line. **
7/25/2005 10:10:35 AM

Setup path: D:\setup.exe
Trying to get version of
D:\setup.exe
....succeeded.
D:\setup.exe is version 11.0.5510.0
Current version of Setup.exe: 11.0.5510.0
Searching for .INI file: setup.INI
D:\FILES\SETUP\setup.INI
Settings file located: D:\FILES\SETUP\setup.INI
Reading settings file
D:\FILES\SETUP\setup.INI
Located: D:\PRJPRO.MSI
Package to install: D:\PRJPRO.MSI
Reading from "D:\FILES\SETUP\setup.INI": "Product\SkipLangCheck" (Default:
0)
Value: 0
Reading from "D:\FILES\SETUP\setup.INI": "Product\CheckUpdates" (Default: 0)
Value: 0
Product {913B0409-6000-11D3-8CFE-0150048383C9} is not installed for the
user.
Checking for Windows Installer....
C:\WINDOWS\system32\MSI.DLL
... succeeded.
Checking for any beta version of the product.
dwNoLtCoExist = 0
Reading from "D:\FILES\SETUP\setup.INI": "Cache\CDCache" (Default: 0)
Value: auto
General properties added: LAUNCHEDFROMSETUP="1" SETUPEXEPATH="D:\"
SETUPEXENAME="setup.exe"

Writing Task: Main - Microsoft Office Project Professional 2003
Path: C:\WINDOWS\system32\msiexec.exe
CmdLine: /I D:\PRJPRO.MSI LAUNCHEDFROMSETUP="1" SETUPEXEPATH="D:\"
SETUPEXENAME="setup.exe"

Looking for setup tasks to process.
7/25/2005 10:10:37 AM WaitForMsiExecDone...
7/25/2005 10:10:37 AM WaitForMsiExecDone exits
Verifying install package is available
Reading from "D:\FILES\SETUP\setup.INI": "Cache\CDCache" (Default: 0)
Value: auto
Reading from "D:\FILES\SETUP\setup.INI": "Cache\Purge" (Default: 0)
Value: 0
Reading from "D:\FILES\SETUP\setup.INI": "Cache\DeletableCache" (Default: 0)
Value: 1
SetupXml is at: D:\Files\Setup\PRJPRO.xml

Parsing Download Info
Starting to load install configuration
Download Info:
Download Code : 90000409-6000-11D3-8CFE-0150048383C9
Source Path : D:\
Product Code : {913B0409-6000-11D3-8CFE-0150048383C9}
Prod Src Path : PRJPRO.MSI
Use Windows Installer : false

Files to Download:
File: FILES\WINDOWS\INF\AER_1033.ADM (DW20.ADM_1033)
File: FILES\PFILES\COMMON\MSSHARED\DW\DW20.EXE (DW20.EXE_0001)
File: FILES\PFILES\COMMON\MSSHARED\DW\DWDCW20.DLL (DWDCW20.DLL)
File: FILES\PFILES\COMMON\MSSHARED\DW\1033\DWINTL20.DLL
(DWINTL20.DLL_0001_1033)
File: FILES\PFILES\COMMON\MSSHARED\DW\DWTRIG20.EXE (DWTRIG20.EXE)
File: FILES\PFILES\MSOFFICE\OFFICE11\OCLEAN.DLL (OCLEAN.DLL_1033)
File: FILES\PFILES\MSOFFICE\OFFICE11\OCLNCORE.OPC (OCLNCORE.OPC_1033)
File: FILES\PFILES\MSOFFICE\OFFICE11\OCLNCUST.OPC (OCLNCUST.OPC_1033)
File: FILES\PFILES\MSOFFICE\OFFICE11\1033\OCLNINTL.OPC (OCLNINTL.OPC_1033)
File: FILES\PFILES\MSOFFICE\OFFICE11\OFFCLN.EXE (OFFCLN.EXE_1033)
File: FILES\SETUP\OSE.EXE (OSE.EXE)
File: PRJPRO.MSI (PRJPRO.MSI)
File: FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10O.CHM (PSS10O.CHM_1033)
File: FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10R.CHM (PSS10R.CHM_1033)
File: FILES\PFILES\MSOFFICE\OFFICE11\1033\SETUP.CHM (SETUP.CHM_1033)
File: SKU13B.XML (SKU13B.XML_0002_1033)
File: CC561201.CAB (CC561201.CAB)
File: CD561201.CAB (CD561201.CAB)
File: CF561201.CAB (CF561201.CAB)
File: CL561201.CAB (CL561201.CAB)
File: CM561201.CAB (CM561201.CAB)
File: CP561201.CAB (CP561201.CAB)
File: CR561201.CAB (CR561201.CAB)
File: CS561201.CAB (CS561201.CAB)
File: IJ561201.CAB (IJ561201.CAB)
File: IS561201.CAB (IS561201.CAB)
File: IU561201.CAB (IU561201.CAB)
File: M2561206.CAB (M2561206.CAB)
File: M3561204.CAB (M3561204.CAB)
File: M4561203.CAB (M4561203.CAB)
File: M9561203.CAB (M9561203.CAB)
File: MG561203.CAB (MG561203.CAB)
File: MT561203.CAB (MT561203.CAB)
File: O0561201.CAB (O0561201.CAB)
File: O1561433.CAB (O1561433.CAB)
File: O9561226.CAB (O9561226.CAB)
File: PA561201.CAB (PA561201.CAB)
File: PC1033BF.CAB (PC1033BF.CAB)
File: PC561407.CAB (PC561407.CAB)
File: PJ561407.CAB (PJ561407.CAB)
File: PR103359.CAB (PR103359.CAB)
File: PR103672.CAB (PR103672.CAB)
File: PR308242.CAB (PR308242.CAB)
File: SKU13B.CAB (SKU13B.CAB)
File: TR103620.CAB (TR103620.CAB)
File: TR308220.CAB (TR308220.CAB)
File: V3561202.CAB (V3561202.CAB)
File: YA561203.CAB (YA561203.CAB)
File: YB561207.CAB (YB561207.CAB)
File: YC561202.CAB (YC561202.CAB)
File: YI561201.CAB (YI561201.CAB)
File: YM561202.CAB (YM561202.CAB)
File: YT561201.CAB (YT561201.CAB)
File: ZD561202.CAB (ZD561202.CAB)
File: ZG561201.CAB (ZG561201.CAB)
File: ZH561202.CAB (ZH561202.CAB)
File: ZM561201.CAB (ZM561201.CAB)
File: ZN561201.CAB (ZN561201.CAB)
File: ZQ561201.CAB (ZQ561201.CAB)
File: ZR561202.CAB (ZR561202.CAB)
File: ZS561201.CAB (ZS561201.CAB)
File: ZT561201.CAB (ZT561201.CAB)
File: ZV561201.CAB (ZV561201.CAB)
File: ZY561203.CAB (ZY561203.CAB)
File: ZZ561201.CAB (ZZ561201.CAB)
File: FILES\SETUP\SETUP.INI (PRJPRO.INI)
File: SETUP.EXE (SETUP.EXE_1033)
Using Office Source Engine at path: D:\FILES\SETUP\OSE.EXE
Connected to Office Source Engine.
Checking version of Office Source Engine...
Version: 11.0.5525.0

Using Local Cache Drive of already installed product: C:\.
Found pre-existing download, will use this as default drive for local cache.
Found enough space on drive "C:\" to cache all feature cabinets.
(CDCACHE=AUTO) - There is enough space to cache some or all of the image.
Drive for this download is C:\
Completed download for file: DW20.ADM_1033.
Completed download for file: DW20.EXE_0001.
Completed download for file: DWDCW20.DLL.
Completed download for file: DWINTL20.DLL_0001_1033.
Completed download for file: DWTRIG20.EXE.
Completed download for file: OCLEAN.DLL_1033.
Completed download for file: OCLNCORE.OPC_1033.
Completed download for file: OCLNCUST.OPC_1033.
Completed download for file: OCLNINTL.OPC_1033.
Completed download for file: OFFCLN.EXE_1033.
Completed download for file: OSE.EXE.
Completed download for file: PRJPRO.MSI.
Completed download for file: PSS10O.CHM_1033.
Completed download for file: PSS10R.CHM_1033.
Completed download for file: SETUP.CHM_1033.
Completed download for file: SKU13B.XML_0002_1033.
Finished CDCache Download, retrieving msi download info
7/25/2005 10:10:43 AM
Package was: D:\PRJPRO.MSI.
Setting Package to: C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\PRJPRO.MSI.
Done with CD Caching, cached MSI to: C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\PRJPRO.MSI
7/25/2005 10:10:43 AM
Parsed arg: /I
Parsed arg: D:\PRJPRO.MSI
Parsed arg: LAUNCHEDFROMSETUP=1
Parsed arg: SETUPEXEPATH=D:\
Parsed arg: SETUPEXENAME=setup.exe
Reading from "D:\FILES\SETUP\setup.INI": "Cache\Purge" (Default: 0)
Value: 0
Finished local caching successfully.
DWSETUPLOGFILE=c:\verboselog.txt
DWMSILOGFILE=c:\verboselog_Task(0001).txt
Command Line Logging Parameters: /l*v c:\verboselog_Task(0001).txt
LOGVERBOSE=1
7/25/2005 10:10:43 AM
Executing Task:
Microsoft Office Project Professional 2003
"C:\WINDOWS\system32\msiexec.exe" /I "C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\PRJPRO.MSI" LAUNCHEDFROMSETUP=1
SETUPEXEPATH=D:\ SETUPEXENAME=setup.exe /l*v c:\verboselog_Task(0001).txt
LOGVERBOSE=1 STANDALONEOSE="C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\FILES\SETUP\OSE.EXE" CDCACHE="2"
DELETABLECACHE="1" LOCALCACHEDRIVE="C" DWSETUPLOGFILE="c:\verboselog.txt"
DWMSILOGFILE="c:\verboselog_Task(0001).txt"
Type: msi
Ignore Return Values: False
Reboot: False


Successfully launched MsiExec....
7/25/2005 10:10:50 AM Chained install return code: -1073741819

Exit code was an error.
Shutting down chained setup processing.
Error returned from install, removing cache.
Using Office Source Engine at path: D:\FILES\SETUP\OSE.EXE
Connected to Office Source Engine.
Checking version of Office Source Engine...
Version: 11.0.5525.0

Set Verbose logging for subsequent setup.


***** Setup exits
7/25/2005 10:10:52 AM
(return = -1073741819)

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Gerry Hickman]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or
computer, or with your Microsoft Office.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot
version you've got.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Edward Ray]

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.

 

[Gerry Hickman]

Hi Edward,

It looks as though your MSIEXEC system is working properly, the finger
therefore points at a problem with your Office (or project) CD. Are you
sure this is a brand new CD direct from Microsoft? Have you tested it on
other machines?

Are you sure all other versions of Office, Project, Visio have been
fully uninstalled?

One other thing I noticed in your post, you say you are installing it as
a "user". I don't think this is a good idea, and you should NEVER give
users Admin rights. Have you tried installing it direct from CD as Local
Administrator, please make a log when you try it and make it clear which
version of Office the CD pertains to (e.g. Professional) and whether it
claims to have any embedded service pack, and whether it's a volume
license version.

Hi,

Please can you try installing a non-Office MSI file such as the one on
this page:

<http://www.microsoft.com/downloads/...2b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en>

Use verbose logging just like wot u did for Office.

This will simply put the latest XML components on your machine. Running
the MSI will determine whether it's a fault with your MSIEXEC or computer,
or with your Microsoft Office.

The msi file ran with no issues.

It's odd it says it failed on the chained install, because I didn't know
Project uses a chained install (unless it's something to do with OWC).

After you've done that, run MSIEXEC /? at the CMD line and see wot version
you've got.

Windows ® Installer. V 3.01.4000.1823

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options

</package | /i> <Product.msi>

Installs or configures a product

/a <Product.msi>

Administrative install - Installs a product on the network

/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]

Advertises a product - m to all users, u to current user

</uninstall | /x> <Product.msi | ProductCode>

Uninstalls the product

Display Options

/quiet

Quiet mode, no user interaction

/passive

Unattended mode - progress bar only

/q[n|b|r|f]

Sets user interface level

n - No UI

b - Basic UI

r - Reduced UI

f - Full UI (default)

/help

Help information

Restart Options

/norestart

Do not restart after the installation is complete

/promptrestart

Prompts the user for restart if necessary

/forcerestart

Always restart the computer after installation

Logging Options

/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>

i - Status messages

w - Nonfatal warnings

e - All error messages

a - Start up of actions

r - Action-specific records

u - User requests

c - Initial UI parameters

m - Out-of-memory or fatal exit information

o - Out-of-disk-space messages

p - Terminal properties

v - Verbose output

x - Extra debugging information

+ - Append to existing log file

! - Flush each line to the log

* - Log all information, except for v and x options

/log <LogFile>

Equivalent of /l* <LogFile>

Update Options

/update <Update1.msp>[;Update2.msp]

Applies update(s)

/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi |
ProductCode>

Remove update(s) for a product

Repair Options

/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>

Repairs a product

p - only if file is missing

o - if file is missing or an older version is installed (default)

e - if file is missing or an equal or older version is installed

d - if file is missing or a different version is installed

c - if file is missing or checksum does not match the calculated value

a - forces all files to be reinstalled

u - all required user-specific registry entries (default)

m - all required computer-specific registry entries (default)

s - all existing shortcuts (default)

v - runs from source and recaches local package

Setting Public Properties

[PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the

command line syntax.

Copyright © Microsoft Corporation. All rights reserved.

Portions of this software are based in part on the work of the Independent
JPEG Group.