Error 1402 - windows installer keeps coming up

[scroce]

Running win2k professional with Microsoft Office 2002.

I'm suspecting registry damage, but am not sure. Even if that is true, I don't know how or if I can fix it.

Here is the situation:
I log in. I open up Word, Outlook, Excel, whatever. It works fine. I can open and close it. I step away for a few hours. I come back. I close up the windows I was using before. I try to open Outlook/Exel/Word. Windows installer pops up and says "attempting to install Office XP" - Eventually bombs out with error 1402.


If I log off and log back on, the problem goes away, but then comes back shortly thereafter.

I've seen various documentation on support.microsoft.com about 1402, but most of it applies to win98 or ME, and only talks about attempting to install it for the first time.

I've considered re-installing office or possibly using the windows2000 Registry Repair utility that I have seen around.

Anyone else have any ideas/recommendations?




I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[bcastner]

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q265194

 

[scroce]

thanks bcastner - you found exactly what I was looking for, but didn't think existed.

I'll try that and let you know.

much obliged

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[RandyCSC]

Bcastner... you never seem to be out of surprises... That was a great link.. And I know I will be book morking that one.. Just can't wait until I am able to use that information...

R

 

[bcastner]

Hope it helps.

Bill Castner

 

[scroce]

I finally got a chance to look this over - this is for windows 2000 running office 2000 - I am running Office 2002 (XP i guess) on windows 2000 professional. While the instructions are similar, some of the registry keys don't match up, and I didn't want to take any guesses.

Has anyone found any other documentation on this issue that might help my cause?

thanks

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[Jump1ng]

Have you applied the service packs for office 2002? Seems service pack 3 is the latest version. Have a look here.

http://office.microsoft.com/officeu...ID=CD010225741033&CTT=4&Origin=CD010224911033

Usually applying service packs fixes problems with office. If all else fails you could try uninstalling it and reinstalling it.

 

[bcastner]

This might be different:
HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Common


The number should be higher with Office 2002.

But, did you try the orktools (in Method 1)?

 

[scroce]

bcastner - yes, the version is 10.0, and if I remember correctly, the keys were different that what the article said. I tried the orktools, but that didn't fix it.

jump,

I'll try that service pack installation - if that doesn't do it, I'll have to try to uninstall and reinstall office.

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[sabSpeaks]

I had the same problem (Windows 2000 and Office XP). After reading this post and doing some other research, I have found the solution!

The problem is with registry permissions, which get screwed up for some unknown reason. You need to be an Administrator to perform the following surgery.

1.) Start> Run...
2.) Type "regedt32" (NOT "regedit"; there is a difference)
3.) Bring the HKEY_LOCAL_MACHINE window to front
4.) Browse to SOFTWARE/Microsoft/Windows/CurrentVersion/Run/OptionalComponents
5.) Go to Security> Permissions...
6.) Click "Add..."
7.) On the list that comes up, add your username and the "Administrators" group.
8.) Click "OK"
9.) Select your username from the list
10.) Check "Allow" under both "Read" and "Full Control"
11.) Do the same for the Administrators group.
12.) Click "Apply" and "OK"
13.) Close the Registry Editor
14.) Install the latest patches and service packs from Microsoft. They should work now.

Enjoy!

 

[scroce]

thanks sab - here is another solution that seemed to work:

I was able to obtain the original installation disks for Office 10 (XP) - I ran setup and chose the option for "repair installation".

However, like sab said, I had to log off and log back on as administrator for this solution to work, it would bomb out if I was logged in as my user name and attempted to repair the installaion. I thought I had given myself full admin rights, but I guess somewhere I was missing some.

Anyway, it seems to be working well now.

I am a nobody, and nobody is perfect; therefore, I am perfect.