RE: Office 2007 Install Error 2203

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Leon,

Hi Leon,

Thank you for the suggestions. Even though I believe I've tried most of
this in a haphazard manner before my first post to the discussion group, I'm
going to go through it all again as you suggested, being very careful to
follow each step precisely.

(In all of this, I am using the TRUE administrator account, which I enabled,
not the user/administrator account. I actually logged on as the true
administrator as opposed to just running the various programs with
administrator authority).

Bottom Line: Installation still fails with same error 2203

Notes regarding my efforts in following your directions:

Suggestion 1:
I had previously installed and tried the "Windows Installer Cleanup
Utility". I just now uninstalled the Cleanup Utility, downloaded the latest
version again and reinstalled the Cleanup Utility.

Results: Neither the ControlPanel "Programs and Features" nor the Windows
Installer Cleanup Utility listed that Office 2007 (or any other office
version) was installed.
Regarding (your) steps 3-5 from the KB article: In general, there were only
a couple of Office/Office12 files/keys to be removed, all of which which were
successfully deleted; most of the files/registry keys listed in the KB
article did not exist.

There were a couple of anomalies that occurred during the following of the
steps in the KB article:
Regarding "Remove the beta release version of the 2007 Office Installation
files and folders", step 6: There was no MSOCache directory on the Vista
boot disk ( there are no other local disks on this Vista machine), but there
was an MSOcache directory on a filesystem mounted from another computer, but
I was unable to gain permission to search this directory for any Office files.
Regarding "Remove the beta release version of the 2007 Office Installation
files and folders", step 9: The directories referenced in the KB article,
namely, "%appdata%\microsoft\document build blocks\...lang...\" was not
available at all. There was a different directory structure involving Local,
LocalLow and Roaming directories. The "Local" directory had an entry for
Office, which I completely removed.

After following your Suggestion 1, I went on to your Suggestion 2, just as
insurance that we might solve the problem and also to not have to redo
Suggestion 1 (which was quite time-consuming) if the installation failed
again.

Suggestion 2:

I was not able to reinstall the Windows Installer 3.1. Perhaps you failed
to realize from my inital post to the discussion group that I am running
VISTA RTM Ultimate x64, which I just installed several days ago. The KB
article you referenced allowed me to redownload a new 3.1 x86 installer, but
not a 3.1 x64 installer compatible with VISTA. I was not able to find a 3.1
x64 installer in microsoft downloads. I was able to find an installer update
for Vista x64 RC1, but when I tried to install it on my Vista x64 RTM, I got
a message saying "The update does not apply to your system".

Suggestion 3:

I had checked \windows\temp permissions previously, as I stated in my first
post, but I did it again. It seems all is OK. The following permissions
were found for \windows\temp:

Creater/Owner - no permissions specified;
SYSTEM - All permissions but "Special"; Administrators - All permissions
except "Special";
Users - All permissions except "Special".

For \windows\temp, there was no entry for just "administrator" (without the
s). I also checked Program Files, Program Files(x86), Documents and
Settings (and subdirectories) and all permissions seemed OK.

So, I'm still stumped. I believe that if we can get a better interpretation
of which files don't have the correct permissions, as described in the cause
of error 2203, then I/we could narrow in on the cause more precisely than
shotgun approaches as I have done up to now. Or perhaps you found out that
2203 can mean something more than just permission errors on files?

So, what's next?

Thanks, Tom
OneNoOne@xxxxxxxxxxxxx
--
Tom


"Leon Hao [MSFT]" wrote:

Hi Tom,

Based on my experience, you can try the following three suggestions:

Before we start, please make sure that you are using an Administrator
account to perform the following steps. (Not the user account in the
administrator group)

* Suggestion 1
===========

To remove Office 2007 Beta completely, follow the steps below:

1. Download Windows Installer CleanUp Utility. The information and download
link is contained at the following KB article:

290301 Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301/en-us

2. After you have downloaded and installed it, please see if Office 2007
entry is displayed on the list. If it is, please highlight and remove it.
If not, please skip this step.

3. Remove the installation files, and stop the 2007 Office services

4. Remove the beta release version of the 2007 Office registry subkeys

5. Remove the beta release version of the 2007 Office installation files
and folders

The detailed information on how to perform steps 3-5 can be found at the
following KB article:

928218 Error message after you remove the beta release version of a 2007
Office suite or program and then try to install the original release
version of a 2007 Office suite or program: "Setup is unable to proceed"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;928218

* Suggestion 2
===========

In some situations, this issue can also be caused by the corruption of
Windows Installer. The latest version of Windows Installer is 3.1. To
manually install Windows Installer 3.1, please visit the following web link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=889482FC-5F56-4A38-
B838-DE776FD4138C&displaylang=en

Download and install Windows Installer 3.1, then double click Setup.exe on
your Office media to install Office again.

* Suggestion 3
===========

Additionally, you can try to check the permission of following folder:

C:\Windows\Temp

To make sure that you have full control of this folder.


Regards,

Leon Hao

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages

  • Re: Windows Installer
    ... Local Computer Policy\Computer Configuration\Administrative ... "The Windows Installer Service Could Not Be Accessed" ... On the Edit menu, click Permissions. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Why does Office go through Configuration routine every time?
    ... I then reapplied the registry updates, ... are registry keys whose permissions need changing. ... A Windows Installer shortcut provides two key features ... When a Microsoft Office program is activated, the Windows Installer ...
    (microsoft.public.office.setup)
  • Re: Why does Office go through Configuration routine every time?
    ... I then reapplied the registry updates, ... are registry keys whose permissions need changing. ... A Windows Installer shortcut provides two key features ... When a Microsoft Office program is activated, the Windows Installer ...
    (microsoft.public.office.setup)
  • Re: Why does Office go through Configuration routine every time?
    ... I then reapplied the registry updates, ... are registry keys whose permissions need changing. ... A Windows Installer shortcut provides two key features ... When a Microsoft Office program is activated, the Windows Installer ...
    (microsoft.public.office.setup)
  • Re: Automatic Update downloadng multiple copies of the same update
    ... For Suggestion 1, wuauserv works just as well as WuAuServ and there's no need to delete the entire SoftwareDistribution folder, especially with a fresh install of XP as compared to a Repair installation ... For Suggestion 3, there is no URL provided for Windows Installer 3.1 Redistributable, such as: ... If it still does not work, please proceed to suggestion 3 to reinstall Windows Installer 3.1. ...
    (microsoft.public.windowsupdate)