C
Chad Harris
Despite everything I've tried, I believe I need to repair a corrupted/broken
MSI and nothing I've done to do that is working.
I had Office 2007 fully service packed up to date on my Win 7 box working
well. All of a sudden I got message it was corrupted, and I couldn't open
or work with any docs. I had been running Office 2010 Tech Preview, but it
had a few glitches, and I had docs to do, so when I couldn't uninstall 2010
Tech Preview from Add/Remove--a frequent occurrence with Office betas I've
come to expect, I used the Manual Removal MSKB meticulously and then I was
able to get Office 2007 in working fine for six months.
The problems I had with 2010 Tech Preview (a legitimate download from
MSFT--not a torrent baby) were overcome quickly. First it wouldn't install
because a series of registry keys need permission (four of them) so I hopped
over to them and gave them permission. Then 2010 finally installed. Next
(and a small percentage of us had these problems because I helped several
people with them on the TechNet newsgroups) none of the 2010 programs would
open without taking five long minutes to run Office setup. This was quickly
overcome by simply going to Drive/Program Files/Office 14/word.exe or
whichever Office program you wanted>rt. click>run as admin. I don't know
why this worked, but it did. Trying to do the same thing with the Office
shortcut on the desktop or start menu wouldn't work, and this only took
seconds so it was no big deal--just a slight annoyance. I did not have the
problem on another PC--Office 2010 Tech Preview worked great on it, it
uninstalled from
Programs and Features (the updated name for Add/Remove with no significant
improved functionality). I'm running Office 2010 RTM on the other pc and
I've transferred all my docs I need over there and I can work on it if I
have to, but it's a desktop P4 not duo core and I want to work on the faster
notebook.
When 2007 would not work or open, I again tried to uninstall from
Prog/Features>no go so I carefully uninstalled manually per the latest MSKB
for Office 2007 which worked on uninstalling Office 2010 before.
I tried to install both Office 2007 RTM and Office 2010 RTM, first getting
the errors that permissions had to be obtained with successive registry keys
for each. I'd been there and done that when the Tech Preview first
released, so I quickly gained permission to each registry key both of them
dealt to me every time I tried to install but no joy occurred this time.
After I gained permission for each registry that 2007 and then 2010 through
at me, they promptly began to give the terse message that "Office 2010 has
encountered an installation error."
That was no help of course, so I went to the Office MSI/setup logs and Event
Viewer to glean as much detail as I could.
The office setup log has the most specific and helpful error message and it
is this:
Error: Failed to install product: F:\MSOCache\All
Users\{90140000-0115-0409-1000-0000000FF1CE}-F\OfficeMUI.msi ErrorCode:
1601(0x641).
The registry key messages that I was used to from my bout installing Tech
Preview were typically like this one:
Product: Microsoft Office Professional Plus 2010 -- Error 1402. Setup cannot
open the registry key
UNKNOWN\Components\1FA18F7974E099CD0AF18C3B9B1A1EE8\b25099274a207264182f8181add555d0.
Verify that you have sufficient permissions to access the registry or
contact Microsoft Product Support Services (PSS) for assistance. For
information about how to contact PSS, see
C:\Users\A1\AppData\Local\Temp\Setup00000c54\PSS10R.CHM.
PSS couldn't begin to help with this--and there is no info in that chm
folder on contacting any of them anyway. The translation for the reg key
(why one should be needed is a fair question is really):
HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S1-5-18\Components\
People have a lot better chance finding the reg keys if they are stated
simply rather than the way MSFT chose to do it in the error message, soccer
moms and "little Kylie" included.
It would be nice if the setup logs would have proposed solutions for the
error from the MSKBs or wherever, but they don't. I try to hit the MSKBs
hard and the Technet 2010 groups to fix something where I helped for a while
when the Betas first started, before I ask for help here.
______________________________
Among the 6 unhelpful messages I got were from Event Viewer were these:
1) Windows Installer has determined that its configuration data registry key
was not secured properly. The owner of the key must be either Local System
or Builtin\Administrators. The existing key will be deleted and re-created
with the appropriate security settings.
2) The protocol handler Mapi cannot be loaded. Error description: The
specified module could not be found. (HRESULT : 0x8007007e).
3) MSI Failed to connect to server. Error: 0x80080005
4) Fault bucket , type 0
Event Name: Office12Setup
Response: Not available
Cab Id: 0
5) These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_{90140000-0011-0_7f172de3bd7d22491819de3751815769eef4ca_06003332
6) The description for Event ID 5000 from source Microsoft Office 14 cannot
be found. Either the component that raises this event is not installed on
your local computer or the installation is corrupted. You can install or
repair the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
__________________________________________________________
This isn't my first rodeo with Office setup problems I've noted since Office
2000--they will always exist in spades as long as MSFT has a campus at
Redmond--and they don't ever seem to lessen statistically with each new
highly trumpeted version of Office--2010 is the one that will be painted on
the walls and extolled for the next 24 months. The same goes for the
service packs.
I read several of the TechNet threads on 2010 setup problems, and had
already tried the standard reflex solutions for this setup error per them
and the MSKBs I could find connected with an MSI error.
1) I made sure at MSCONFIG that I had the checkmark in "load system
services" on the general tab because without it the MSI can have problems or
not run.
2) I ran the WICU again (Windows Installer Cleanup Utility) to clear the
many Office associated entries--I always use this to uninstall Office if I
have to resort to a manual uninstall. It's MVP Andre de Costa's sole
solution to this problem and it didn't help.
3) I unregistered and reregistered misexec in the run box per the MSKB and
several suggestions on the Technet groups and this did not help. Typing
msiexec in the run box shows the Win 7 MSI installed.
4) I made sure I manually unistalled meticulously before attempting to
install either of them again per this little gem:
http://support.microsoft.com/kb/928218
5) I tried Sean Fances [MSFT] suggestion for someone with a similar problem:
"More than likely there is an orphaned MSI from Technical Preview still
installed on your machine. Check your installer keys for GUID's that start
with 0000 and end with 00F01FEC. CLick on each one and verify ProductName
references Office 2010 and not Office 14. ANy ProductNames that reference
Office 14 and Technical Preview bits and delete them.
Installer keys: HKCU\Installer\Products
Also, look for GUIDs in your uninstall keys that end with 00FF1CE and verify
DisplayName says Office 2010 (Beta) and not Office 14. Remove any found.
Uninstall keys: HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall"
Sean Francis [MSFT] Office 2010 Beta Engineer - Setup and Deployment
6) I tried going to the Installer folder and looking for any Send a Smile
files and deleting them as suggested by Niyamath Khan [MSFT] support but
none were there after the manual unistall which included deleting all Office
associated folders that would delete on any drive per the manual uninstall
and the Office 12 and Office 14 files in the program files folders.
7) I tried the directions in this MSKB:
http://support.microsoft.com/kb/321497
Any help getting this in would be greatly appreciated. I thought I would
have this conquered when I obtained permission for the registry keys that
were thrown at me in successive failures because I had seen that work before
for myself and several others in the early days of the Tech Previews, but
then the error evolved into a "failure to access the MSI error."
TIA,
CH
MSI and nothing I've done to do that is working.
I had Office 2007 fully service packed up to date on my Win 7 box working
well. All of a sudden I got message it was corrupted, and I couldn't open
or work with any docs. I had been running Office 2010 Tech Preview, but it
had a few glitches, and I had docs to do, so when I couldn't uninstall 2010
Tech Preview from Add/Remove--a frequent occurrence with Office betas I've
come to expect, I used the Manual Removal MSKB meticulously and then I was
able to get Office 2007 in working fine for six months.
The problems I had with 2010 Tech Preview (a legitimate download from
MSFT--not a torrent baby) were overcome quickly. First it wouldn't install
because a series of registry keys need permission (four of them) so I hopped
over to them and gave them permission. Then 2010 finally installed. Next
(and a small percentage of us had these problems because I helped several
people with them on the TechNet newsgroups) none of the 2010 programs would
open without taking five long minutes to run Office setup. This was quickly
overcome by simply going to Drive/Program Files/Office 14/word.exe or
whichever Office program you wanted>rt. click>run as admin. I don't know
why this worked, but it did. Trying to do the same thing with the Office
shortcut on the desktop or start menu wouldn't work, and this only took
seconds so it was no big deal--just a slight annoyance. I did not have the
problem on another PC--Office 2010 Tech Preview worked great on it, it
uninstalled from
Programs and Features (the updated name for Add/Remove with no significant
improved functionality). I'm running Office 2010 RTM on the other pc and
I've transferred all my docs I need over there and I can work on it if I
have to, but it's a desktop P4 not duo core and I want to work on the faster
notebook.
When 2007 would not work or open, I again tried to uninstall from
Prog/Features>no go so I carefully uninstalled manually per the latest MSKB
for Office 2007 which worked on uninstalling Office 2010 before.
I tried to install both Office 2007 RTM and Office 2010 RTM, first getting
the errors that permissions had to be obtained with successive registry keys
for each. I'd been there and done that when the Tech Preview first
released, so I quickly gained permission to each registry key both of them
dealt to me every time I tried to install but no joy occurred this time.
After I gained permission for each registry that 2007 and then 2010 through
at me, they promptly began to give the terse message that "Office 2010 has
encountered an installation error."
That was no help of course, so I went to the Office MSI/setup logs and Event
Viewer to glean as much detail as I could.
The office setup log has the most specific and helpful error message and it
is this:
Error: Failed to install product: F:\MSOCache\All
Users\{90140000-0115-0409-1000-0000000FF1CE}-F\OfficeMUI.msi ErrorCode:
1601(0x641).
The registry key messages that I was used to from my bout installing Tech
Preview were typically like this one:
Product: Microsoft Office Professional Plus 2010 -- Error 1402. Setup cannot
open the registry key
UNKNOWN\Components\1FA18F7974E099CD0AF18C3B9B1A1EE8\b25099274a207264182f8181add555d0.
Verify that you have sufficient permissions to access the registry or
contact Microsoft Product Support Services (PSS) for assistance. For
information about how to contact PSS, see
C:\Users\A1\AppData\Local\Temp\Setup00000c54\PSS10R.CHM.
PSS couldn't begin to help with this--and there is no info in that chm
folder on contacting any of them anyway. The translation for the reg key
(why one should be needed is a fair question is really):
HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S1-5-18\Components\
People have a lot better chance finding the reg keys if they are stated
simply rather than the way MSFT chose to do it in the error message, soccer
moms and "little Kylie" included.
It would be nice if the setup logs would have proposed solutions for the
error from the MSKBs or wherever, but they don't. I try to hit the MSKBs
hard and the Technet 2010 groups to fix something where I helped for a while
when the Betas first started, before I ask for help here.
______________________________
Among the 6 unhelpful messages I got were from Event Viewer were these:
1) Windows Installer has determined that its configuration data registry key
was not secured properly. The owner of the key must be either Local System
or Builtin\Administrators. The existing key will be deleted and re-created
with the appropriate security settings.
2) The protocol handler Mapi cannot be loaded. Error description: The
specified module could not be found. (HRESULT : 0x8007007e).
3) MSI Failed to connect to server. Error: 0x80080005
4) Fault bucket , type 0
Event Name: Office12Setup
Response: Not available
Cab Id: 0
5) These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_{90140000-0011-0_7f172de3bd7d22491819de3751815769eef4ca_06003332
6) The description for Event ID 5000 from source Microsoft Office 14 cannot
be found. Either the component that raises this event is not installed on
your local computer or the installation is corrupted. You can install or
repair the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
__________________________________________________________
This isn't my first rodeo with Office setup problems I've noted since Office
2000--they will always exist in spades as long as MSFT has a campus at
Redmond--and they don't ever seem to lessen statistically with each new
highly trumpeted version of Office--2010 is the one that will be painted on
the walls and extolled for the next 24 months. The same goes for the
service packs.
I read several of the TechNet threads on 2010 setup problems, and had
already tried the standard reflex solutions for this setup error per them
and the MSKBs I could find connected with an MSI error.
1) I made sure at MSCONFIG that I had the checkmark in "load system
services" on the general tab because without it the MSI can have problems or
not run.
2) I ran the WICU again (Windows Installer Cleanup Utility) to clear the
many Office associated entries--I always use this to uninstall Office if I
have to resort to a manual uninstall. It's MVP Andre de Costa's sole
solution to this problem and it didn't help.
3) I unregistered and reregistered misexec in the run box per the MSKB and
several suggestions on the Technet groups and this did not help. Typing
msiexec in the run box shows the Win 7 MSI installed.
4) I made sure I manually unistalled meticulously before attempting to
install either of them again per this little gem:
http://support.microsoft.com/kb/928218
5) I tried Sean Fances [MSFT] suggestion for someone with a similar problem:
"More than likely there is an orphaned MSI from Technical Preview still
installed on your machine. Check your installer keys for GUID's that start
with 0000 and end with 00F01FEC. CLick on each one and verify ProductName
references Office 2010 and not Office 14. ANy ProductNames that reference
Office 14 and Technical Preview bits and delete them.
Installer keys: HKCU\Installer\Products
Also, look for GUIDs in your uninstall keys that end with 00FF1CE and verify
DisplayName says Office 2010 (Beta) and not Office 14. Remove any found.
Uninstall keys: HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall"
Sean Francis [MSFT] Office 2010 Beta Engineer - Setup and Deployment
6) I tried going to the Installer folder and looking for any Send a Smile
files and deleting them as suggested by Niyamath Khan [MSFT] support but
none were there after the manual unistall which included deleting all Office
associated folders that would delete on any drive per the manual uninstall
and the Office 12 and Office 14 files in the program files folders.
7) I tried the directions in this MSKB:
http://support.microsoft.com/kb/321497
Any help getting this in would be greatly appreciated. I thought I would
have this conquered when I obtained permission for the registry keys that
were thrown at me in successive failures because I had seen that work before
for myself and several others in the early days of the Tech Previews, but
then the error evolved into a "failure to access the MSI error."
TIA,
CH