msiexec.exe Application Error "The instruction at "0x00f33fe8" referenced memory at "0x00f33fe8". The memory could not be "written"."

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...b;en-us;826511
but could not find any helpful hints.

Hi,

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

<http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-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.

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 (London UK)[/color]

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.

Gerry:

My users are Local Admins. It makes things easier, and they use
"DropMyRights" for outlook, firefox, etc.

The install is done by users (as local admins) on the laptops. Right now MS
Office 2003 pro with SP1 and all patches is installed. with the MSIexec
failure I cannot do a reinistall/repair, and I am afraid to uninstal lest I
never be able to reinstall office back again. Only thing I wanted was MS
project, but it is not as impt as word, outlook, excel, powerpoint.

CD for MS projects seems OK, as I have used it to install MS Project Pro
2003 on other Windows 2003 and XP desktops.

Thanks for the help and advice.

Edward W. Ray

Hi Edward,

> My users are Local Admins. It makes things easier,

LOL, it makes things 1000 easier for SpyWare and Viruses too. Ever heard
of impersonation? Of all the "do and don't s" of Windows security this
is second most important on the list.

> The install is done by users (as local admins) on the laptops.

Very bad idea. This could screw up your installs (especially non-MSI)
and some things might crash when trying to uninstall, and you're left
with a mess. Installers should never be allowed access to a user profile
or registry hive, unless it's the "All Users" one. Unfortunately,
Microsoft don't design their software with this in mind, so unless you
deny Admin rights to users it will end up a total mess. The default
installer is really designed for a home user with Admin rights, there's
no perception of corporate roll-outs until you get into the ORK and the
command line, and even then the preference defaults still won't work
properly with domain users and roaming profiles.

> Right now MS
> Office 2003 pro with SP1 and all patches is installed. with the MSIexec
> failure I cannot do a reinistall/repair, and I am afraid to uninstal lest I
> never be able to reinstall office back again. Only thing I wanted was MS
> project, but it is not as impt as word, outlook, excel, powerpoint.

OK, well I think you have to accept the laptop may need rebuilt and just
uninstall anyway. It's only one laptop. Office _likes_ being
uninstalled, as does most software. It cleans up a lot of junk and
prevents problems in the future. It's also safer to run the MSI cleanup
tool if you've uninstalled everything first.

Can you post the SETUP.INI file from your Project 2003 CD.

--
Gerry Hickman (London UK)