G
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.
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.
Edward said: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.