MSI Error on administration deployment

I decided to deploy Office 2003 through an administration deployment point.
However on about 1/3 of the machines i recieve an error stating
Application Launcher Status
Problem Install Failed. MSI returned error code: 1603.

These errors occur on mostly windows xp sp2 machines (but to be honest there
is no hard and fast rule for the specfication of the machines its working on
or not working on.

I was also using Zenworks to deploy the MSI but have also tried without it.

Can anyone help please.

Thanks

Scrappo

Hi Scrappo,

Can you provide additional details on how you're running the deployment
(i.e. what is the command line with Setup.exe that you are using, are you using a custom MST file, etc).

======
"Scrappo" wrote in message ...
I decided to deploy Office 2003 through an administration deployment point.
However on about 1/3 of the machines i recieve an error stating
Application Launcher Status
Problem Install Failed. MSI returned error code: 1603.

These errors occur on mostly windows xp sp2 machines (but to be honest there
is no hard and fast rule for the specfication of the machines its working on
or not working on.

I was also using Zenworks to deploy the MSI but have also tried without it.

Can anyone help please.

Thanks

Scrappo
--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Thanks for getting back to me Bob

ok
Yes i created a MST file and configured the setup.ini. All are on a Network
drive called H:\ of which i have given the users all sorts of rights (in
order to try anything to get this to work)

The deployment is being sent out via Zenworks using the admin package path as:
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)

The SETUP.INI path is
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\Files\SETUP\SETUPINI

Transform (MST) Path
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.MST

I also applied the SP2 (i have tried with and without this) which is placed
in:
H:\MSO2003\SP2 MSP file\MAINSP2ff.msp

The setup.ini file is shown here

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
MST1=H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.mst

[Options]
; The option section is used for specifying individual Installer Properties.
USERNAME=Browne Construction
COMPANYNAME=J Browne Construction Company Limited
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE predefined Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI


The problem is that this works on all but a 1/3 of the pc's/laptops we have.

Anything else you need?

Thanks

Scrappo

"Bob Buckland ?:-)" wrote:

Hi Scrappo,

Can you provide additional details on how you're running the deployment
(i.e. what is the command line with Setup.exe that you are using, are you using a custom MST file, etc).

======
"Scrappo" wrote in message ...
I decided to deploy Office 2003 through an administration deployment point.
However on about 1/3 of the machines i recieve an error stating
Application Launcher Status
Problem Install Failed. MSI returned error code: 1603.

These errors occur on mostly windows xp sp2 machines (but to be honest there
is no hard and fast rule for the specfication of the machines its working on
or not working on.

I was also using Zenworks to deploy the MSI but have also tried without it.

Can anyone help please.

Thanks

Scrappo
--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Hi Scrappo,

You mentioned that you have also tried it without ZenWorks. In that scenario what is the command line you're using and even with
ZenWorks are you using just the msi or running the Office Setup program?

What happens (errors, etc) on the machines where it fails and at what point?
(If Office 2003 'appears' to be installed on a PC then rerunning with an MST file would generally fail the 'first time install' test
that is made).

Anything common or unique on the machines where it's failing? (Domain, server, controller, Windows version, etc)?

You're chaining the SP2 update to the clients rather than updating the admin point with it and then deploying or recaching as your
preferred approach then?

==========
"Scrappo" wrote in message ...
Thanks for getting back to me Bob

ok
Yes i created a MST file and configured the setup.ini. All are on a Network
drive called H:\ of which i have given the users all sorts of rights (in
order to try anything to get this to work)

The deployment is being sent out via Zenworks using the admin package path as:
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)

The SETUP.INI path is
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\Files\SETUP\SETUPINI

Transform (MST) Path
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.MST

I also applied the SP2 (i have tried with and without this) which is placed
in:
H:\MSO2003\SP2 MSP file\MAINSP2ff.msp

The setup.ini file is shown here

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
MST1=H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.mst

[Options]
; The option section is used for specifying individual Installer Properties.
USERNAME=Browne Construction
COMPANYNAME=J Browne Construction Company Limited
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE predefined Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI


The problem is that this works on all but a 1/3 of the pc's/laptops we have.

Anything else you need?

Thanks

Scrappo

--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Hello Bob

The PC's in questions (both that work and those that doent) are either
windows xp or 2k, they are all of similar build and run similar programs.
Sorry but there just doesnt seem to be a common factor in terms of PC/Laptop
build.
When I try the install without zenworks i am running the SETUP.EXE
application directly - it gets to a certain point and the rolls back the
installation. I then get the normally Windows error report send or not send
diaglogue of which when i ask to see the report leads me to the following 2
txt files

Microsoft Office 2003 Setup(0003).txt
Microsoft Office 2003 Setup(0003)_Task(0001).txt

The first one is shown here but the second is to large to attach so i have
just copied in the last part.

Detected Windows Info:
PlatformId = 2
MajorVersion = 5
MinorVersion = 0
ServicePackLevel = 4
- - - - - - - - - - - - - - - - - - - - - - -
Launch Setup
03/03/2006 16:38:09
Setup path: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\SETUP.EXE
Trying to get version of
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)\SETUP.EXE
....succeeded.
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)\SETUP.EXE is
version 11.0.5510.0
Current version of Setup.exe: 11.0.5510.0
Searching for .INI file: SETUP.INI
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI
Settings file located: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI
GetTempPath returned: C:\WINNT\TEMP\
Setup has detected a previously failed installation - Verbose Logging ON

Reading settings file
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI
Located: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)\PRO11.MSI
Package to install: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\PRO11.MSI
Apply transform:
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.mst
Add Property:
USERNAME=Browne Construction
Add Property:
COMPANYNAME=J Browne Construction Company Limited
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Product\SkipLangCheck" (Default: 0)
Value: 0
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Product\CheckUpdates" (Default: 0)
Value: 0
Product {90110409-6000-11D3-8CFE-0150048383C9} is not installed for the user.
Checking for Windows Installer....
C:\WINNT\system32\MSI.DLL
... succeeded.
Checking for any beta version of the product.
dwNoLtCoExist = 0
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Cache\CDCache" (Default: 0)
Value: auto
Office-specific properties added: USERNAME="Browne Construction"
COMPANYNAME="J Browne Construction Company Limited"
General properties added: LAUNCHEDFROMSETUP="1"
SETUPEXEPATH="H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)\"
SETUPEXENAME="SETUP.EXE"

Writing Task: Main - Microsoft Office 2003
Path: C:\WINNT\system32\msiexec.exe
CmdLine: /I "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\PRO11.MSI" TRANSFORMS="H:\MSO2003\Workstation Install
Profile\WKSTNOFFICE11 (D_)\transforms\jbrownewkstn.mst" USERNAME="Browne
Construction" COMPANYNAME="J Browne Construction Company Limited"
LAUNCHEDFROMSETUP="1" SETUPEXEPATH="H:\MSO2003\Workstation Install
Profile\WKSTNOFFICE11 (D_)\" SETUPEXENAME="SETUP.EXE"

Looking for setup tasks to process.
03/03/2006 16:38:11 WaitForMsiExecDone...
03/03/2006 16:38:11 WaitForMsiExecDone exits
Verifying install package is available
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Cache\CDCache" (Default: 0)
Value: auto
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Cache\Purge" (Default: 0)
Value: 0
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Cache\DeletableCache" (Default: 0)
Value: 1
SetupXml is at: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\Files\Setup\PRO11.xml

Parsing Download Info
Starting to load install configuration
Transforms are being used... attempting to cache them
Successfully parsed and added transforms to cache configuration
Download Info:
Download Code : 90000409-6000-11D3-8CFE-0150048383C9
Source Path : H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)\
Product Code : {90110409-6000-11D3-8CFE-0150048383C9}
Prod Src Path : PRO11.MSI
Use Windows Installer : false

Files to Download:
File: (jbrownewkstn.mst)
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: PRO11.MSI (PRO11.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: SKU011.XML (SKU011.XML_0002_1033)
File: A2561405.CAB (A2561405.CAB)
File: A3561405.CAB (A3561405.CAB)
File: A4561405.CAB (A4561405.CAB)
File: AV561403.CAB (AV561403.CAB)
File: CC561401.CAB (CC561401.CAB)
File: CD561401.CAB (CD561401.CAB)
File: CF561401.CAB (CF561401.CAB)
File: CL561401.CAB (CL561401.CAB)
File: CM561401.CAB (CM561401.CAB)
File: CP561401.CAB (CP561401.CAB)
File: CR561401.CAB (CR561401.CAB)
File: CS561401.CAB (CS561401.CAB)
File: E2561410.CAB (E2561410.CAB)
File: E3561405.CAB (E3561405.CAB)
File: E4561410.CAB (E4561410.CAB)
File: EV561405.CAB (EV561405.CAB)
File: G3561403.CAB (G3561403.CAB)
File: GV561403.CAB (GV561403.CAB)
File: IJ561401.CAB (IJ561401.CAB)
File: IS561401.CAB (IS561401.CAB)
File: IU561401.CAB (IU561401.CAB)
File: L2561403.CAB (L2561403.CAB)
File: L3561403.CAB (L3561403.CAB)
File: L4561403.CAB (L4561403.CAB)
File: L9561403.CAB (L9561403.CAB)
File: LV561403.CAB (LV561403.CAB)
File: M2561406.CAB (M2561406.CAB)
File: M3561404.CAB (M3561404.CAB)
File: M4561403.CAB (M4561403.CAB)
File: M9561403.CAB (M9561403.CAB)
File: MA561403.CAB (MA561403.CAB)
File: MC561403.CAB (MC561403.CAB)
File: MG561403.CAB (MG561403.CAB)
File: MH561401.CAB (MH561401.CAB)
File: MO561403.CAB (MO561403.CAB)
File: MT561403.CAB (MT561403.CAB)
File: O0561401.CAB (O0561401.CAB)
File: O1561403.CAB (O1561403.CAB)
File: O9561403.CAB (O9561403.CAB)
File: P2561401.CAB (P2561401.CAB)
File: P3561401.CAB (P3561401.CAB)
File: P4561402.CAB (P4561402.CAB)
File: PA561401.CAB (PA561401.CAB)
File: PR103368.CAB (PR103368.CAB)
File: PR103678.CAB (PR103678.CAB)
File: PR308246.CAB (PR308246.CAB)
File: PV561401.CAB (PV561401.CAB)
File: PW561401.CAB (PW561401.CAB)
File: Q2561405.CAB (Q2561405.CAB)
File: Q3561405.CAB (Q3561405.CAB)
File: Q4561405.CAB (Q4561405.CAB)
File: QV561405.CAB (QV561405.CAB)
File: SKU011.CAB (SKU011.CAB)
File: TR103621.CAB (TR103621.CAB)
File: TR308222.CAB (TR308222.CAB)
File: V3561403.CAB (V3561403.CAB)
File: W2561405.CAB (W2561405.CAB)
File: W3561405.CAB (W3561405.CAB)
File: W4561405.CAB (W4561405.CAB)
File: WV561405.CAB (WV561405.CAB)
File: X2561401.CAB (X2561401.CAB)
File: X3561401.CAB (X3561401.CAB)
File: YA561403.CAB (YA561403.CAB)
File: YB561408.CAB (YB561408.CAB)
File: YC561403.CAB (YC561403.CAB)
File: YH561403.CAB (YH561403.CAB)
File: YI561401.CAB (YI561401.CAB)
File: YL561402.CAB (YL561402.CAB)
File: YM561403.CAB (YM561403.CAB)
File: YO561403.CAB (YO561403.CAB)
File: YS561401.CAB (YS561401.CAB)
File: YT561401.CAB (YT561401.CAB)
File: ZA561401.CAB (ZA561401.CAB)
File: ZC561402.CAB (ZC561402.CAB)
File: ZD561402.CAB (ZD561402.CAB)
File: ZE561406.CAB (ZE561406.CAB)
File: ZF612702.CAB (ZF612702.CAB)
File: ZG561401.CAB (ZG561401.CAB)
File: ZH561403.CAB (ZH561403.CAB)
File: ZI561402.CAB (ZI561402.CAB)
File: ZJ561401.CAB (ZJ561401.CAB)
File: ZK561401.CAB (ZK561401.CAB)
File: ZM561401.CAB (ZM561401.CAB)
File: ZN561401.CAB (ZN561401.CAB)
File: ZO561401.CAB (ZO561401.CAB)
File: ZQ561401.CAB (ZQ561401.CAB)
File: ZR561403.CAB (ZR561403.CAB)
File: ZS561401.CAB (ZS561401.CAB)
File: ZT561401.CAB (ZT561401.CAB)
File: ZU561401.CAB (ZU561401.CAB)
File: ZV561401.CAB (ZV561401.CAB)
File: ZY561401.CAB (ZY561401.CAB)
File: ZZ561401.CAB (ZZ561401.CAB)
File: FILES\SETUP\SETUP.INI (PRO11.INI)
File: SETUP.EXE (SETUP.EXE_1033)
Using Office Source Engine at path: H:\MSO2003\Workstation Install
Profile\WKSTNOFFICE11 (D_)\FILES\SETUP\OSE.EXE
Connected to Office Source Engine.
Checking version of Office Source Engine...
Version: 11.0.5525.0

Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Cache\LocalCacheDrive" (Default: )
Value:
Found NTFS drive.
Local Cache Drive: C:\.
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:\
Adding temporary sources
Added temporary source: temp-jbrownewkstn.mst (H:\MSO2003\Workstation
Install Profile\WKSTNOFFICE11 (D_)\transforms\)
Completed download for file: jbrownewkstn.mst.
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: PRO11.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: SKU011.XML_0002_1033.
Finished CDCache Download, retrieving msi download info
03/03/2006 16:39:01
Package was: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\PRO11.MSI.
Setting Package to: C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\PRO11.MSI.
Done with CD Caching, cached MSI to: C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\PRO11.MSI
03/03/2006 16:39:01
Cleaning up temporary sources
Deleted temporary source: temp-jbrownewkstn.mst (H:\MSO2003\Workstation
Install Profile\WKSTNOFFICE11 (D_)\transforms\)
Parsed arg: /I
Parsed arg: H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\PRO11.MSI
Parsed arg:
Parsed arg: USERNAME=Browne Construction
Parsed arg: COMPANYNAME=J Browne Construction Company Limited
Parsed arg: LAUNCHEDFROMSETUP=1
Parsed arg: SETUPEXEPATH=H:\MSO2003\Workstation Install
Profile\WKSTNOFFICE11 (D_)\
Parsed arg: SETUPEXENAME=SETUP.EXE
Reading from "H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\FILES\SETUP\SETUP.INI": "Cache\Purge" (Default: 0)
Value: 0
Finished local caching successfully.
DWSETUPLOGFILE="C:\WINNT\TEMP\Microsoft Office 2003 Setup(0003).txt"
DWMSILOGFILE="C:\WINNT\TEMP\Microsoft Office 2003 Setup(0003)_Task(0001).txt"
Command Line Logging Parameters: /lpiwaeov "C:\WINNT\TEMP\Microsoft Office
2003 Setup(0003)_Task(0001).txt" LOGVERBOSE=1
03/03/2006 16:39:01
Executing Task:
Microsoft Office 2003
"C:\WINNT\system32\msiexec.exe" /I "C:\MSOCache\All
Users\90000409-6000-11D3-8CFE-0150048383C9\PRO11.MSI"
USERNAME="Browne Construction" COMPANYNAME="J
Browne Construction Company Limited" LAUNCHEDFROMSETUP=1
SETUPEXEPATH="H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)\"
SETUPEXENAME=SETUP.EXE /lpiwaeov "C:\WINNT\TEMP\Microsoft Office 2003
Setup(0003)_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:\WINNT\TEMP\Microsoft Office 2003 Setup(0003).txt"
DWMSILOGFILE="C:\WINNT\TEMP\Microsoft Office 2003 Setup(0003)_Task(0001).txt"
Type: msi
Ignore Return Values: False
Reboot: False


Successfully launched MsiExec....
03/03/2006 17:05:08 Chained install return code: 1603

Exit code was an error.
Shutting down chained setup processing.
Error returned from install, removing cache.
Using Office Source Engine at path: H:\MSO2003\Workstation Install
Profile\WKSTNOFFICE11 (D_)\FILES\SETUP\OSE.EXE
Successfully started Office Source Engine in stand-alone mode.
Set Verbose logging for subsequent setup.


***** Setup exits
03/03/2006 17:05:14
(return = 1603)

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2nd txt files (last part only as to large)

Property(C): PrimaryVolumePath = C:
Property(C): ProgressActionText = Now Installing Office
Property(C): LastInstallDialog = Summary
Property(C): UI_AccessState = 3
Property(C): UI_ExcelState = 3
Property(C): UI_OutlookState = 3
Property(C): UI_PowerPointState = 3
Property(C): UI_PubState = 3
Property(C): UI_WordState = 3
Property(C): UI_XDocsState = 3
=== Logging stopped: 03/03/2006 17:05:07 ===
MSI (c) (40:88) [17:05:07:812]: Note: 1: 1708
MSI (c) (40:88) [17:05:07:812]: Product: Microsoft Office Professional
Edition 2003 -- Installation operation failed.

MSI (c) (40:88) [17:05:08:296]: Attempting to delete file
C:\WINNT\TEMP\1e44768.mst
MSI (c) (40:88) [17:05:08:296]: Unable to delete the file. LastError = 32
MSI (c) (40:88) [17:05:08:546]: Grabbed execution mutex.
MSI (c) (40:88) [17:05:08:546]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (40:88) [17:05:08:546]: MainEngineThread is returning 1603
=== Verbose logging stopped: 03/03/2006 17:05:08 ===

Hope that Helps

Scrappo


"Bob Buckland ?:-)" wrote:

Hi Scrappo,

You mentioned that you have also tried it without ZenWorks. In that scenario what is the command line you're using and even with
ZenWorks are you using just the msi or running the Office Setup program?

What happens (errors, etc) on the machines where it fails and at what point?
(If Office 2003 'appears' to be installed on a PC then rerunning with an MST file would generally fail the 'first time install' test
that is made).

Anything common or unique on the machines where it's failing? (Domain, server, controller, Windows version, etc)?

You're chaining the SP2 update to the clients rather than updating the admin point with it and then deploying or recaching as your
preferred approach then?

==========
"Scrappo" wrote in message ...
Thanks for getting back to me Bob

ok
Yes i created a MST file and configured the setup.ini. All are on a Network
drive called H:\ of which i have given the users all sorts of rights (in
order to try anything to get this to work)

The deployment is being sent out via Zenworks using the admin package path as:
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)

The SETUP.INI path is
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\Files\SETUP\SETUPINI

Transform (MST) Path
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.MST

I also applied the SP2 (i have tried with and without this) which is placed
in:
H:\MSO2003\SP2 MSP file\MAINSP2ff.msp

The setup.ini file is shown here

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
MST1=H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.mst

[Options]
; The option section is used for specifying individual Installer Properties.
USERNAME=Browne Construction
COMPANYNAME=J Browne Construction Company Limited
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE predefined Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI


The problem is that this works on all but a 1/3 of the pc's/laptops we have.

Anything else you need?

Thanks

Scrappo

--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Hello Bob

Did you have any luck analysing the setup report?

Thanks

Scrappo

"Bob Buckland ?:-)" wrote:

Hi Scrappo,

You mentioned that you have also tried it without ZenWorks. In that scenario what is the command line you're using and even with
ZenWorks are you using just the msi or running the Office Setup program?

What happens (errors, etc) on the machines where it fails and at what point?
(If Office 2003 'appears' to be installed on a PC then rerunning with an MST file would generally fail the 'first time install' test
that is made).

Anything common or unique on the machines where it's failing? (Domain, server, controller, Windows version, etc)?

You're chaining the SP2 update to the clients rather than updating the admin point with it and then deploying or recaching as your
preferred approach then?

==========
"Scrappo" wrote in message ...
Thanks for getting back to me Bob

ok
Yes i created a MST file and configured the setup.ini. All are on a Network
drive called H:\ of which i have given the users all sorts of rights (in
order to try anything to get this to work)

The deployment is being sent out via Zenworks using the admin package path as:
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11 (D_)

The SETUP.INI path is
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\Files\SETUP\SETUPINI

Transform (MST) Path
H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.MST

I also applied the SP2 (i have tried with and without this) which is placed
in:
H:\MSO2003\SP2 MSP file\MAINSP2ff.msp

The setup.ini file is shown here

; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must
be in
; the same folder as Setup.exe, and both must be in the root of the
installation
; tree.
MSI=PRO11.MSI

[Product]
ProductCode={90110409-6000-11D3-8CFE-0150048383C9}
ProductName=Microsoft Office 2003
ProductVersion=11.0.5614.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
MST1=H:\MSO2003\Workstation Install Profile\WKSTNOFFICE11
(D_)\transforms\jbrownewkstn.mst

[Options]
; The option section is used for specifying individual Installer Properties.
USERNAME=Browne Construction
COMPANYNAME=J Browne Construction Company Limited
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name
unique
Template=Microsoft Office 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[Cache]
; The cache section provides settings for caching the install source locally
; Value Default Description
; CDCACHE 2 Option to specify cache level
; [auto, 0, 1, 2]
; LOCALCACHEDRIVE predefined Option to specify a drive to cache
; the install source to
; DELETABLECACHE 1 Option to display UI to remove the
; cache at the end of setup [0,1]
; PURGE 0 Option to always remove cache at end
of
; setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\
DELETABLECACHE=1
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI


The problem is that this works on all but a 1/3 of the pc's/laptops we have.

Anything else you need?

Thanks

Scrappo

--
Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Hi Scrappo,

I'm a bit unclear on one aspect of what you're working with. If you setup an Office Admin Point and deploy from that Admin point,
then the Local Install Source (LSI) option isn't available, but it appears that you are antint to use a Local Install source, from
what you posted in your logs/.ini file. (i.e. you can use a compressed image central point and create the Local Install Source, as
an either/or choice) http://microsoft.com/office/ork/2003

Error 1603 is, unfortunately, somewhat in itself 'broad' in possiblilities.
You may want to see if the information here applies.

http://support.microsoft.com/kb/835209/en-us.

You may need to then go to verbose logging to get more detail on the boxes that are not working properly as described in
http://support.microsoft.com/kb/826511/en-us.

=======
"Scrappo" wrote in message ...
Hello Bob

The PC's in questions (both that work and those that doent) are either
windows xp or 2k, they are all of similar build and run similar programs.
Sorry but there just doesnt seem to be a common factor in terms of PC/Laptop
build.
When I try the install without zenworks i am running the SETUP.EXE
application directly - it gets to a certain point and the rolls back the
installation. I then get the normally Windows error report send or not send
diaglogue of which when i ask to see the report leads me to the following 2
txt files

Microsoft Office 2003 Setup(0003).txt
Microsoft Office 2003 Setup(0003)_Task(0001).txt

The first one is shown here but the second is to large to attach so i have
just copied in the last part...
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends

Pricing and Packages for '2007 Microsoft Office System'
http://microsoft.com/office/preview

Hello Bob thanks for your reply

When you say about the local admin point where do you see this? The H: drive
is a network drive and as for the D: (written in at some points) isnt an
actual drive it was just part of the name of the folder (silly i know). Is it
one of these that you ment?

Also i with reference to the ork hotfix - i tested this by taking out the
additional files that were placed in the MST and still recieved the same
message.

As for the verbose logs - i had thought id done this as they were the logs
that i placed on a thread above. Are these not the ones (as i say the second
one is to big to fit on this site).

Any ideas?

Thanks again

Scrappo

"Bob Buckland ?:-)" wrote:

Hi Scrappo,

I'm a bit unclear on one aspect of what you're working with. If you setup an Office Admin Point and deploy from that Admin point,
then the Local Install Source (LSI) option isn't available, but it appears that you are antint to use a Local Install source, from
what you posted in your logs/.ini file. (i.e. you can use a compressed image central point and create the Local Install Source, as
an either/or choice) http://microsoft.com/office/ork/2003

Error 1603 is, unfortunately, somewhat in itself 'broad' in possiblilities.
You may want to see if the information here applies.

http://support.microsoft.com/kb/835209/en-us.

You may need to then go to verbose logging to get more detail on the boxes that are not working properly as described in
http://support.microsoft.com/kb/826511/en-us.

=======
"Scrappo" wrote in message ...
Hello Bob

The PC's in questions (both that work and those that doent) are either
windows xp or 2k, they are all of similar build and run similar programs.
Sorry but there just doesnt seem to be a common factor in terms of PC/Laptop
build.
When I try the install without zenworks i am running the SETUP.EXE
application directly - it gets to a certain point and the rolls back the
installation. I then get the normally Windows error report send or not send
diaglogue of which when i ask to see the report leads me to the following 2
txt files

Microsoft Office 2003 Setup(0003).txt
Microsoft Office 2003 Setup(0003)_Task(0001).txt

The first one is shown here but the second is to large to attach so i have
just copied in the last part...
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends

Pricing and Packages for '2007 Microsoft Office System'
http://microsoft.com/office/preview