Office 2003 sp1 online update - froze at step 4 of 5

[Andy Babiec]

I tried installing 2003 sp1 last night from the office
update site.

Toward the end, around step 4 of 5, it asked for my
frontpage 2003 CD for a file. I did that and it seemed to
find the file and continue. I'm not 100% sure but I think
I did see the progress bar resume after that. But then,
it seemed to be stuck at step 4 of 5 for a very long
time. So I checked on it this morning and it was still in
the same place. I clicked on cancel and it sent me to the
office update site, indicating that sp1 was installed.

I tired even running the full stand-alone install file,
but that also indicates that the sp1 was already
installed.

How do I ensure that my sp1 install was complete?

This is what I see in the OHotFix(00002).log....

Starting the log on 08/01/2004 at 07:07:14...
Loading the resource .dll...
Reading the settings...
The settings are:
IsNormalUpdate=1
AdminUsesShortFilenames=1
AdminPath=""
MessageTitle="Office 2003 Service Pack 1 (SP1)"
CopyFilesToRerun=1
ShowSuccessDialog=1
RebootInQuietMode=0
RunSetupWatson=1
RequireAllPatchesNeeded=0
RequireAllProductsAtMinVersion=0
MinProductVersion=""
MinMsiVersion="2.0"
UpgradeMsi=1
MsiUpgradeURL="http://go.microsoft.com/fwlink/?
LinkId=20610"
OHotfixLogLevel="v"
MsiLogLevel="v"
OHotfixUILevel="n"
MsiUILevel="n"
FeatureToCheck=""
Making sure only this instance of the bootstrapper is
running...
Making sure the environment is okay for patching...
Getting the patches...
Getting the products to patch...
Seeing if patch C:\Temp\IXP000.TMP\MAINSP1ff.msp is
needed...
Product {901C0409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90150409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {91130409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90170409-6000-11D3-8CFE-0150048383C9}
Microsoft Office FrontPage 2003 Version 11.0.6361.0:
Already has this patch.
Product {91170409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90E00409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {901A0409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90180409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {91E30409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90110409-6000-11D3-8CFE-0150048383C9}
Microsoft Office Professional Edition 2003 Version
11.0.6361.0: Already has this patch.
Product {91110409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90190409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {91190409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90CA0409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {91CA0409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90120409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {91120409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {901B0409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90440409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {91440409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Product {90160409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Seeing if patch C:\Temp\IXP000.TMP\OWC102003SP1ff.msp is
needed...
Product {90260409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
Seeing if patch C:\Temp\IXP000.TMP\OWC11SP1ff.msp is
needed...
Product {90A40409-6000-11D3-8CFE-0150048383C9}:
Not installed. Cannot patch.
This update has already been applied.
Finished processing the update on 08/01/2004 at 07:07:19.

 

[Andy Babiec]

The log file was from my full file install this morning.
I'm not sure where I can find the log file for the online
update.

 

[Chad Harris]

Andy--

*Event Viewer Might Help With Errors to Select a Tool or a KB*

When you go to Event Viewer, by putting "eventvwr.msc" in your run box, what
error messages do you see under Application with MSI Installer as the
source. These may help see what happened and if at the end they say you
were unsuccessful, then you didn't get SP1 in. Some of these may be in
English if you're fortunate, and besides referring you to the OHotfix folder
in temp files where the logs are kept, it may say something in English you
can understand like files not found,ect. Do you have anything like that?
Post those errors in Event Viewer and you can probably get some tool or KB
or help applied here.

If you do, then some of these links might apply, and for people having
problems installing from that update catalogue link's scan progress bar
(some are) they can go to this link to start downloading the appropriate
update:

Downloads for Office 2003:
http://office.microsoft.com/officeu...ID=CD010224941033&CTT=4&Origin=ES790020041033

Take a look at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;875556
"Installation Error: File not Found" error message when you try to update
Office 2003 programs from the Office Update Web site

2) If that doesn't help, then try using this:

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

3) Then, if you can't use the Cleanup Utility and reinstall MOS 2003
afterward (save the temporary set up files for future installs when you get
the option) then take a look at this:

http://www.microsoft.com/office/ork/2003/journ/LISTool.htm.
Change the Local Installation Source After the Installation

http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.htmTaking
Advantage of a Local Installation Source

Other LIS Resources:

http://www.microsoft.com/office/ork/2003/journ/LISupdt.htm

http://www.microsoft.com/office/ork/2003/journ/LISTool.htm

*What Do I see if My Install is Successful?*

4) Go to your run box and type in services.msc and make sure you have an
entry for the Office Source Engine and that it's started.

5) I know this is probably reflex but turn off Antivirus
scripting,auto-protect, and Office plug-ins if your version has an entry. I
haven't found the XP SP2 Windows Firewall to have anything to do with
stopping Office Installs or Updates and I doubt it ever does. I don't know
about all 3rd party firewalls, but doubt they ever do, nor do hardware
firewalls like routers.

6) Delete Temporary Internet Files, as many Temporary Files as you can (the
OHotfix folder with the MSI Hotfix Logs won't be deleting so don't worry
about them).

7) Try naming your Config.msi file to old. Do a search for it on
your C:\ or OS drive with protected OS files shown.

8) Some posters have said that simply removing Office Web-Add Ins from
Add-Remove has worked wonders in getting SP1 in, but I had trouble, and I
didn't have any Web-Add ins and a lot of people don't.

*What do you see if the SP1 Install is Successful?*

If your install is successful, you get a box that says "The Update was
applied successully."

Also, to see if your MOS 2003SP1 install was complete, go to Add/Remove.
While there are some Windows and perhaps Office updates that don't show in
Add/Remove{ Direct X 9b updates are one item that bothered some Win XP
users that duly recognized in a registry key), Office 2003 updates seem to
be showing up regularly there.

For additional evidence you can put "eventvwr.msc" or "eventvwr.exe" in your
run box, and stretch the box out, click Application and look toward the last
entry at the time you did the install and the source will be "MSI
Installer":
Product: Microsoft Office Professional Edition 2003 -- Update 'Office2003
Service Pack 1 Applied Successfully.

*KBs and An Article That May Help In Undrstanding the Hotfix Logs*

How to Enable Windows Installer Logging

http://support.microsoft.com/default.aspx?scid=223300

How to use an Office 2003 Setup log file to troubleshoot Setup problems

http://support.microsoft.com/default.aspx?scid=kb;en-us;826511&Product=off2003

HOW TO: Customize Office Setup Logging Options

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

Setup Sequence of Events

http://www.microsoft.com/office/ork/2003/two/ch3/DepA03.htm

If you don't have it in, then in the same plot of real estate in event
viewer, you should be rewarded with some type of error, hopefully with a 4
digit number in English like 1603, 1336, which will offer you a panopoly of
excellent resources like System Error Code 267 whatever that is, (all
Office Users know System Error Codes except me), and a link to this KB and
cheerfully in all probability refer you to a numbered Temporary Hotfix log
that has a default verbose log and is located in your Temp Folders under a
folder called "OHotfix" or as I fondly like to call it "Oh Hotfix Whassup?"
\Temp\OHotfix\OHotfix(00010)_Msi.log.

I don't know what error you have and I can't interpret what you pasted--I
don't know the list of the type person that has the training and tools to do
this like Rohit, Sloan Crayton, Hugo Lopez and some Office MVPs. It's great
that they are available here, but the reality on the street is most Windows
and Office Users don't have a clue that these groups exist and never will.
That leaves the burning question, how do they run down to the corner to get
their Hotfix log read at the local gas station?

The fact that you had to paste part of an Office hotfix log means that the
boys and girls who develop Office for MSFT have some work to do in
transmitting on the street useful error messages for the Office user.
Because after 11 Office versions with people eagerly blogging Office
Longhorn and Office .net and Office 12 development sugar plums dancing in
their heads, Microsoft has not gotten beyond multiple Hex messages,
Hungarian notation and Hotfix log jargon whatever language this is supposed
to be. I don't see people sitting in outdoor cafes spouting those setting
phrases or in supermarket checkout lines and my point is MSFT needs to
realize that people cannot use this jargon to get their Office in so they
can be productive the way all the cutsey commercials with the guy sliding on
the floor and people piling on them on TV suggest they will--"He conquered
the World With MOS 2003--yeah, maybe if he could only get it and it's merry
band of Hotfixes and Updates in." Rohit--you all gotta get error
information in real time and plain English to people. Do Steve Sinofsky and
Jeff Raikes and the other VPs get that there's a real world out there that
can't use the Hex and other jargon????

You can put %temp% in your run box and then go to the O's. You'll see
entries with numbers with _MSI at the end and entries without numbers with
_MSI at the end. Some of them might be empty (why I don't know) and some
that the error codes reference may simply not be there--the case for me.
There you will see any number of verbose logs with numbers and often a
coresponding log without a number. Unless you are exceptional, you won't be
able to interpret these logs which take special tools. You can read these
KBs and the setup sequence resource kit articele to enlarge your
understanding of setup logging (For me some degree of verbose Hotfix Logging
was default already in operation because I didn't make any reg hacks or
other moves to get them there).

I'm not sure the percent of worldwide Office users who can actually
understand and use them is above 1%. IT Pros, Sysads, Office Mavens and
MVPs , code heads, and Office and Windows enthusiasts like many of us, but
not every legal secretary, person in a mom and pop print shop, or back
office person in a medical office I'm going to bet--and that's unfortunate
because a lot of small business have no IT department budget and will never
have.

Good luck,

Chad Harris

______________________________________________________________

 

[Sloan Crayton [MS]]

From the log file, it appears that you are successfully installed. However,
as a final verification, comparing the Office application EXE file versions
to the table in the KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;842532 should
provide further assurance. For convenience, here is the table. These files
should be located in the '\Program Files\Microsoft Office\OFFICE11' folder.

File name Version
------------------------------------
Excel.exe 11.0.6355.0
Frontpg.exe 11.0.6356.0
Infopath.exe 11.0.6357.0
Msaccess.exe 11.0.6355.0
Outlook.exe 11.0.6353.0
Powerpnt.exe 11.0.6255.0
Winword.exe 11.0.6359.0
Mspub.exe 11.0.6255.0

Sloan Crayton
Microsoft

 

[Andy Babiec]

1. Should I be concerned about any other files (dll's,
etc.)?

2. Is there any way to view the log from the web install.
The log I posted was from the full file attempt AFTER the
web install.

 

[Sloan Crayton [MS]]

If these files are the correct version, Office Update detection does not
suggest the update again, and the logs indicate patching success, then
you're fine.

Regarding your second question, a switch from the Ohotfix install handler to
a different technology lost the capability to provide logging from the
Office Update web site. We are working on changing this as it is obviously
a necessary component of providing support for patching.

Sloan Crayton
Microsoft