Can't install Office 2003 SP1 or uninstall Office 2003 at all

T

Test Man

Hi.
I downloaded the Service Pack 1 client install and ran it on my machine.
It seemed to be taking ages to install and the progress box wasn't moving
from 0% so I just shut-down the machine. Upon restarting the machine, each
component of Office said SP1 next to it's version number on Add/Remove
Programs, however, upon trying to add a component by clicking on the Change
button in Add/Remove Programs or repair using the Detect and Repair on the
Help menu in each of the programs causes this error to appear everytime:

"This patch package could not be opened. Verify that the patch package
exists and that you can access it, or contact the application vendor to
verify that this is a valid Windows Installer patch package."

Also tried running SETUP.EXE from the original CDs and same thing comes up.

I did have an additional problem: when trying to update my Logitech Webcam,
the Windows Installer setup said that an Office 2003 update was suspended
and it had to roll-back the changes. So I had to click on YES to continue
the install and all the version numbers for all the Office components are
back to pre-SP1. However, I can't remove Office 2003, as above, to
reinstall it and the Service Pack.

Any ideas?

Machine is Dell P4 3.06GHz, 512MB RAM, Windows XP Professional, 120GB Hard
Drive.
 
C

Chad Harris

Goose[MS]--

I have these problems (Errors) getting SP1 for MOS 2003 installed and got
One Note SP1 in fine and the Outlook/BCM update offerred yesterday.

Product: Microsoft Office Professional Edition 2003 - Update 'Office 2003
Service Pack 1' could not be installed. Error code 1603. Additional
information is available in the log file
C:\DOCUME~1\RICHAR~1\LOCALS~1\Temp\OHotfix\OHotfix(00002)_Msi.log.
Product: Microsoft Office Professional Edition 2003 -- Error 1336. There was
an error creating a temporary file that is needed to complete this
installation. Folder: C:\Config.Msi\. System error code: 267

Failed to connect to server. Error: 0x800401F0

The premise of this utility is to resolve installation problems by removing
programs' Windows Installer configuration information. From the KB it seems
that it will not impact Office itself. It says it does not remove the
Windows installer. Can you clarify this? Because when you hit that
remove button, the dialogue box seems to say qauite another thing. When I
select MOS 2003 and hit the remove button, it says "in order for the
products to work properly, you must individually reinstall the products."
It doesn't say the installer, Moose, it says the product and the product is
Office 2003.

That's more than ambiguous. It says the exact opposite from the KB. Which
is it?

1)Does Office get uninstalled the way that dialogue box says clearly, or
just the install information. If you look at the dialogue box it says it's
taking Office out.
2) Should you put the Office 2003 CD in the drive whether prompted for it or
not?
3) What is the role of the Office Source Engine which these installs will
ask you to start in services if it's not started? I don't remember it in
previous versions. I turn it on but it doesn't help.
http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htm
4) I don't know if the Failed to Connect to server was temporary or
permanant--meaning MSFT's server farm is overwhelmed due to demand. I have
the enu.exe downloaded so it wouldn't seem this error is that problem so why
would I get a "failed to connect to server error" after the download has
been successful?
_____________________________________________________
If MS=MSFT and is the company headquartered in Redmond Washington, instead
of Convergs of Ohio who spells their "support" facade, then I have a
question.

I also have good reason to believe Convergys is doing MSFT and their
customers a systemic disservice in terms of poor quality support; has been
for years, and will continue to.

Convergys support and hexidecimal error messages in Event Viewer are one of
the most detrimental concepts of support in the history of computing--and
it's MSFT's approach.

http://oca.microsoft.com/en/Welcome.asp is going to give you zero as it
exists now.

I'm having the same problem and what MS uses to support millions of people
unless they are an enterprise with a lot of boxes and licenses that can
really impact the bottom line is CONVERGYS OF OHIO. A number of people are
having install problems with Office SP1 for MOS 2003 released yesterday that
can install One Note SP1 and One Note after uninstalling One Note Beta SP1
just fine.

"Convergys support"--I talked with four of them- and the concept I love
most--the non-technically trained supervisor---doesn't have a clue what to
do with SP1 install problems, and they don't have a clue what to do with the
logs that the errors refer to. The logs as you know are created in the
%temp% folder and when I offered to email to the Convergys rep who either is
for the most part in Nova Scotia or Bangelor India, they said the log files
aren't important. I beg to differ. I think they are the essense of the
error messages, particularly when they aren't in Hex or Hungarian
Notation--and of course some of them are in end user unfreindly HEX.

The usual song and dance from Convergys fronting as MSFT is to say they are
referring to "research" and if you'll sit by the phone for 12 hours for the
honor of taking their call, they'll call you sometimes (Phone Roulette)
during the 12 hours over the next 5 days--they don't do weekends.

The problem with them being in Bangelore and New Delhi and Nova Scotia is
that the developers who know they have birthed a setup problem that was not
properly vetted by Beta Testing of MOS 03 SP1 who reside in Redmond
Washington, or Dallas, Texas or North Carolina don't pick up the phone or
shoot an email or have a MSFT Live Meeting with these support personnel on
the front lines.

What happens then is they have 3 cookie cutter moves when dealing with the
install problems--no matter what your log files may say or what your Error
Messages happen to be. I don't know why there seem to be the setup files to
install One Note SP1 but not Office SP1--all of them have always been saved
on install on this box.

1) Name the Config.msi file to old.
2) Go to the run box and unregister msiexec by typing msiexec /unregister
the reregister it with "msiexec /regserver.
3) Try the install in Safe Mode.

Convergys has been using this canned response to Office probems of all
stripes for years and years.
Quality control monitoring of this sham is zero.

The "support episode" is constantly interrupted adding 2 hours of waiting
for every 15 minutes of conversation while the "support professional"
consults "research personnel"--people who might have a clue but don't. When
you point out this relay method of messaging is taking twice as long, you're
told those people don't talk to the public. That's consistent because under
this setup--neither does Microsoft Redmond/Dallas (Office Support
Headquaters).

Thanks,

Chad Harris

_______________________________________________
 
T

Test Man

OK, thank you. I did read that article prior to posting my message, so with
what you said, it seems that I'm going to have to take the plunge and delete
all the Windows Installer info to reinstall Office, which is gonna be a big
task I guess.

Goose said:
Try using the Windows Installer Cleanup Utility detailed here to uninstall Office:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

When you reinstall don't forget to not delete the local cache files at the
end of the installation so you will have your Local Install Source intact
and will be able to patch your Office installation without the possible need
of the CD.
 
B

Beth Melton

Hi Chad,

To answer some of your questions, the Windows Installer Clean-up
utility will remove the Windows Installer entries for Office in the
Registry - it doesn't uninstall Office. However in order to create new
Windows Installer entries you need to reinstall Office.
--
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
B

Beth Melton

It's not a major task. I've tested the Windows Installer Cleanup
Utility several times and to zap the Installer entries for Office and
reinstall Office takes a matter of minutes. :)

--
Please post all follow-up questions to the newsgroup. Requests for
assistance by email can not be acknowledged.

~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP

Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
 
T

Test Man

Hi Beth
You're right about it not being a major task, just used the Cleanup
Utility then reinstalled Office 2003 and then the SP1 update, worked pretty
fast and easy. Thanks to all.
 
C

Chad Harris

Beth--

Appreciate the clarification. I was getting confused with the sentence in
this:

Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

The Windows Installer CleanUp Utility does not:
a.. Remove Windows Installer.
b.. Remove files of any programs that are installed by Windows Installer,
such as Microsoft Office 2003.
Now I know, that if you use the WICU that you are going to uninstall the
app. But I think it means that setup files will remain, and then may be
replaced if damaged or missing by the reinstall of MOS 2003. Correct me if
I mistated this please or could state it better.

Also I wondered a couple thingsgoing over the list and would value your
comment.

1) All items that make use of the MSI or Windows Installer are not listed in
the utility. And I believe some use the MSI in partnership with Install
Shield unless Install Shield makes part of the Windows Installer for MSFT
and sometimes a third party installer and I always though that one of the
problems was, and I'd appreciate any comment that someone will write a great
3rd party app who is working on his own and doesn't have the
resources/budget of MSFT or a large software company, so they may not be
able to make as good an installer for their product. I don't mean all 3rd
parties at all, but sometimes that this might be a factor in a less than
pristine install or uninstall.

2) Having had my share of problems from time to time installing or
uninstalling apps like Norton AV or System Works or Internet Security, I
know they have their own uninstall utilities and Norotn has KBs for hand
uninstalling various GUIDs, other registry keys, and Norton Shared files,
and what I was getting at was I wonder if using this Clean Up Installer
could help there, and I alos wondered if you could consider it VIP
Add/Remove, i.e. why not go to the Clean Up Utility to remove anything
that's listed when you had occasion to remove it as a more thorough removal?

Thanks,

Chad Harris

_____________________________________________________________________________
 
S

Sloan Crayton [MS]

I think I can clarify the use of the Windows Installer Cleanup Utility a
bit. When the Windows Installer was first being created, a tool called
MSIZap was created that would be able to 'zap' an application's Installer
registry information. Later it was included in the Windows Installer SDK
products. That tool is a command line utility that must be used via command
prompt; so it's not the most user friendly utility.

To answer a need for a utility that could more easily be used by the
majority of users that need a way to recover a corrup installation, the
Windows Installer Cleanup Utility was created that leverages the
functionality of MSIZap but provides nice wizard-like UI.

The function of the utility is to remove the remove the corrupted Windows
Installer registry information for an application that was installed via the
Windows Installer. There are several things that it does not do ...
- It does not uninstall any applications
- It does not delete the Windows Installer

After using this utility, the application should then be installed again so
that Setup will function (otherwise, the Windows Installer has no
information that it was ever installed). If the real objective is to remove
a product, it can be uninstalled after this reinstall has occurred.

Sloan Crayton
Microsoft
 
C

Chad Harris

Sloan--

Thanks to you and Beth for perspective and clarity on this tool. I
appreciate the perspective a lot because it helps fill in blanks that much
more. I remember going after MSIZap when I had a bear of a setup problem a
couple months ago--I got rid of "wisptis.exe" which MSFT default installs to
support the tablet pen, and then Office wouldn't install for that and other
reasons. Adobe programs as well as Office install wisptis so after my
last dust up I'm leaving alone and just kill it from TM Processes when it
shows up which is often.

There might be more ways to fix that problem having read this group the last
few days that I would be able to try now.

This was really helpful for me in finally getting what the utility does:

The function of the utility is to remove the remove the corrupted Windows
Installer registry information for an application that was installed via the
Windows Installer. There are several things that it does not do ...
- It does not uninstall any applications
- It does not delete the Windows Installer


After using this utility, the application should then be installed again so
that Setup will function (otherwise, the Windows Installer has no
information that it was ever installed). If the real objective is to
remove
a product, it can be uninstalled after this reinstall has occurred.

I find this explanation much more clear than the KB on the utility

http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

because now I understand that *it* doesn't actually uninstall the program,
but that *you* need to uninstall and reinstall the program. It would be
good, I think if the utility had that clarity on it and KB 290301 had your
language in it. I know the KB said it didn't install the program, but a
couple people I talked to intimated it did rather than what you need to do
when you use it.

I appreciate that you and others from [MS] are putting in so much time to
help fill in some blanks with KBs, explanations about tools from the
Resource Kit and tips, because I have been trying to differentiate some of
the tools including LIS. For some of us, setup, and dealing with these logs
is daunting at first because it is more demanding than seeing an error, and
getting a simple KB with a set of steps and a few clicks that solve a
problem.

I wish it weren't necessary to have to resort to the Hotfix verbose logs to
feret out what might be blocking an install, because everyone likes to have
a solution at hand and you don't have much ability to fix if one of the
tools is a log that most users have no way to translate.

Thanks very much for clearing this utility up. If I can just get a handle
on the LIS feature now.

Chad Harris
__________________________________________________________________
 
S

Sloan Crayton [MS]

I guess I need to take another look at KB290301 since I helped to create it.
<g>

As for reading the log files, I'll agree that it's an art that is not easily
mastered. I get help from others in interpreting them. Each Office release
adds a few wrinkles to the interpretation, and I'll take a look at the
creation of a log interpretation KB (as we have for the initial Setup MSI
logs).

Sloan Crayton
Microsoft

Chad Harris said:
Sloan--

Thanks to you and Beth for perspective and clarity on this tool. I
appreciate the perspective a lot because it helps fill in blanks that much
more. I remember going after MSIZap when I had a bear of a setup problem
a couple months ago--I got rid of "wisptis.exe" which MSFT default
installs to support the tablet pen, and then Office wouldn't install for
that and other reasons. Adobe programs as well as Office install
wisptis so after my last dust up I'm leaving alone and just kill it from
TM Processes when it shows up which is often.

There might be more ways to fix that problem having read this group the
last few days that I would be able to try now.

This was really helpful for me in finally getting what the utility does:

The function of the utility is to remove the remove the corrupted Windows
Installer registry information for an application that was installed via
the
Windows Installer. There are several things that it does not do ...
- It does not uninstall any applications
- It does not delete the Windows Installer


After using this utility, the application should then be installed again
so
that Setup will function (otherwise, the Windows Installer has no
information that it was ever installed). If the real objective is to
remove
a product, it can be uninstalled after this reinstall has occurred.

I find this explanation much more clear than the KB on the utility

http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

because now I understand that *it* doesn't actually uninstall the program,
but that *you* need to uninstall and reinstall the program. It would be
good, I think if the utility had that clarity on it and KB 290301 had your
language in it. I know the KB said it didn't install the program, but a
couple people I talked to intimated it did rather than what you need to do
when you use it.

I appreciate that you and others from [MS] are putting in so much time to
help fill in some blanks with KBs, explanations about tools from the
Resource Kit and tips, because I have been trying to differentiate some of
the tools including LIS. For some of us, setup, and dealing with these
logs is daunting at first because it is more demanding than seeing an
error, and getting a simple KB with a set of steps and a few clicks that
solve a problem.

I wish it weren't necessary to have to resort to the Hotfix verbose logs
to feret out what might be blocking an install, because everyone likes to
have a solution at hand and you don't have much ability to fix if one of
the tools is a log that most users have no way to translate.

Thanks very much for clearing this utility up. If I can just get a handle
on the LIS feature now.

Chad Harris
__________________________________________________________________

Sloan Crayton said:
I think I can clarify the use of the Windows Installer Cleanup Utility a
bit. When the Windows Installer was first being created, a tool called
MSIZap was created that would be able to 'zap' an application's Installer
registry information. Later it was included in the Windows Installer SDK
products. That tool is a command line utility that must be used via
command prompt; so it's not the most user friendly utility.

To answer a need for a utility that could more easily be used by the
majority of users that need a way to recover a corrup installation, the
Windows Installer Cleanup Utility was created that leverages the
functionality of MSIZap but provides nice wizard-like UI.

The function of the utility is to remove the remove the corrupted Windows
Installer registry information for an application that was installed via
the Windows Installer. There are several things that it does not do ...
- It does not uninstall any applications
- It does not delete the Windows Installer

After using this utility, the application should then be installed again
so that Setup will function (otherwise, the Windows Installer has no
information that it was ever installed). If the real objective is to
remove a product, it can be uninstalled after this reinstall has
occurred.

Sloan Crayton
Microsoft
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top