I first packaged Word, Excel, Outlook and PowerPoint with an MST and put Access, InfoPath and Publisher on 'not installed' (I also moved the shortcuts to another location in the start menu and deleted the shortcuts which I didn't need).
After that I needed another MST to add only Access. With ADDLOCAL=ACCESSFiles, that wasn't a problem, but I had no shortcut in my start menu. I found out that I shouldn't have deleted the shortcuts in my first MST, so I had to rebuild that. After that, all worked fine!
There is a conflict between Acrobat Reader 7.0 (including 7.01) and Office 2003 on Windows XP whereby there will be an application crash in AcroRd32.exe with on-screen error upon system shutdown or logoff. It does not matter if the user is an admin or not. We've been able to isolate the conflict between Acrobat Reader 7 and Office 2003 on XP down to a sub-component of one of the Office tools. By leaving out the "web debugging" portion of the "HTML Source Editing" tool, we can no longer reproduce the problem. Note this only happens if the Acrobat Reader is configured to open PDFs in-line as AcroRd32.exe hangs out in memory even after IE is closed.
Adobe Acrobat: AcroRd32.exe - Application Error
The instruction at "0x030db8fb" referenced memory at "0x00000154". The memory could not be "read".
Click OK to terminate the program....
*****
*****
Adobe Acrobat: AcroRd32.exe - Application Error
The instruction at "0x5ad71531" referenced memory at "0x00000014". The memory could not be "read".
After installing Office 2003 in a High Security environment where the local system has been locked down using MS's high security settings, you may seen a problem with Office where you get a similar error:
"Microsoft <program> has not been installed for the current user. Please run setup to install the application"
This can happen if the All Users profile is set to Read-Only for the end-user. The folder "C:\Documents and Settings\All Users\Application Data\Microsoft\Office\Data\" is the folder that requires write access for a normal user.
Also, you may see registry errors like:
"Error 1401: Setup cannot create Registry Key"
"Error 1402: Setup cannot open Registry Key"
"Error 1406: Setup cannot write the value to the registry key"
This also is caused by the registry being locked down. The error should provide the path to the registry entry in question. That key should be opened up for write access as well
If you really want to hide the installation dialogs (installation with /qb switch) it's not enough to disable the dialogs but you have to change the following two properties:
InstallExecuteSequence Table
Action SKURED
Condition "0 and NOT Installed"
InstallUISequence Table
Action DoDialogSequence
Condition "0 and NOT Installed"
Last extract from Post on the message board "Office2003 SP2 Upgrade":
"We are already slipstreaming our AIP.
We have a transform file which is not being applied if the msi runs an upgrade. The original transform file (and settings) remain and are not overwritten in:
C:\Windows\Installer\{90110409-6000-11D3-8CFE-0150048383C9}
Our transform has some security changes in it, so even though the upgrade to O2K3SP2 is successful the changes from the transform are not applied unless you uninstall O2K3SP1 and then reinstall O2K3SP2. This also will remove any Office customisations that have been set...."
Resolved by:
Running from script/command line:
msiexec.exe /X{90110409-6000-11D3-8CFE-0150048383C9} /qb-!
This gave us a fresh slate to do a reinstall.
* Note: the custom11.prf file in C:\Program Files\Microsoft Office is not removed on uninstall. We have a modified prf file to configure our archive folder location to a home server location. This was imported into the O2K3SP2.mst using the CIW in the ORK. The default/existing file is removed using the CIW and our one added.
So, ended up with the O2K3SP2.prf being applied for each user. The O2K3SP2.mst is set by running the Setuppro.exe, which refs the Setuppro.ini. Our ini was configured to log and chain the install of the OWC11.msi ie:
[ChainedInstall_1]
TaskType=MSI
Path="OWC11.MSI"
Display=Basic
;MST=[MST file]
;Cmdline=property=value
Squeezed in the latest Office Hotfixes into the AIP and tested extensively on VPC.
Hope this helps someone in the future,
Cheers
WayneB
When installing Clip Organizer 2003 onto a machine that already has it installed from a previous Office version, the original version of the Clip Organizer may load with an error message. After you install a later version of the Clip Organizer, a value in the registry is reordered to load the latest version first and therefore cause this error.
The work around for this is to amend the following registry value;
HKLM\Software\Classes\CLSID\{09E767A6-4481-4791-86A5-A739E5290E4C}\LocalServer32
After the installation, a new entry will be added to the start of the expanded string. Simply move the first entry to the end of the string and everything hould be fixed.
After upgrading Office XP to Office 2003, the standard components from Microsoft Office XP that were installed on your computer are removed.
This includes the Microsoft Photo Editor program.
So, all the image files (jpg, jpeg, jpe, jfif, gif, bmp, dib, png, tif, tiff, wmf, emf) are associated with nothing !
At the end of the Office 2003 package you can add the followings line (in a bach) to associates all the image files to the Microsoft Office Picture Manager (that is included in Office 2003).
I used the following command line for unattended installation:
setup.exe /EULA_ACCEPT=YES
I also made changes in setup.exe file which was placed in Msoffice2003\files folder.Also add the PID key(product key) under the [options]in setup.exe file.
PIDKEY=abcdadfdfdgggagkjfgh (with out dash).
It works.
as the article of qadmin write here a special failure which is solved with kb943452.
Microsoft Office Outlook kann nicht gestartet werden. MAPI32.DLL ist beschädigt oder in der falschen Version vorhanden. Dies wurde möglicherweise durch die Installation einer anderen Messagingsoftware verursacht. Installieren Sie Microsoft Office Outlook neu.
here the link to the hotfix: http://support.microsoft.com/kb/943452/en-us
as the article of qadmin write here a special failure which is solved with kb943452.
Microsoft Office Outlook kann nicht gestartet werden. MAPI32.DLL ist beschädigt oder in der falschen Version vorhanden. Dies wurde möglicherweise durch die Installation einer anderen Messagingsoftware verursacht. Installieren Sie Microsoft Office Outlook neu.
here the link to the hotfix: http://support.microsoft.com/kb/943452/en-us
I had a problem where Microsoft Word would freeze for 60 seconds whenever the thesaurus/research tab was opened. Disabling Microsoft Translator and Wordlingo fixed this, but the changes would not stick when closing/reopening Word 2003. I fixed this by adding the following two registry keys:
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
