Does Windows XP pro sp2 cause problems with doing updates to Micr.

C

casselp

I have had problems with downloading updates from the office web site since I
insstalled Windows XP sp2. The download process starts in the normal way but
stops without completing the down load. I have to abort the process to stop
it. I tried setting up the office update web site as a trusted web site and
that helped with ine update but now the latest update won't down load similar
to before. Has anyone else experienced this problem?
 
C

Chad Harris

Casselp--

The short answer is no to the best of my knowledge. I based this on Office
2003 but I don't know what version of Office you are updating.

There have been numerous problems with downloads/installs of different
Office updates, particularly SP1 for MOS 03 and other service packs for
other applications. Many have to do with the MSOCache folder being deleted
or source files missing With respect to some updates, using the Full File
may help.

I'm not sure what version of Office you have or what particular updates are
causing you a problem because you didn't say. That makes it difficult for
me to *guess which MSKBs might apply to you.* These issues have been tracked
and covered well on the microsoft.public.office.update group and if you scan
some of the posts, you'll see tips there and what I mean.

Also if you scan this \group, you will see some helpful hints about
overcoming some of the obstacles of installing MOS 03 SP1 in multiple
threads, including use of tools from the Resource Kit like LIS or use of the
Windows Uninstall Utility. Sloan Crayton [MS] and others have posted a
number of helpful tips on getting updates in, and on explanations on how to
use the tools like the local install source feature from the Office
Resource Kit for whichever version you have, and contexting problems with
the MSOCACHE folder or with source files missing.

To my knowledge, there haven't been any of the 190 plus MSKBs created for XP
SP2 that have to do with Office update difficulty but I'll check again.
However, there have been a number of MKSBs issued in reference to difficulty
updating Office, particularly with the last wave of SP1 updates for MOS 03
and related apps. I'll try to link a couple or more. One thing I have
noticed is that some but not all Office updates require the Office Source
Engine to be started in services or the installation will abort at setup.
Be sure before you try to download and install an Office update that you go
to "services.msc" in your run box and start the Office Source Engine by
right clicking and setting to manual and automatic and then clicking the
start button. Chances are it will not stay on later, which is fine because
it isn't needed until you install and it takes some CPU so you can manually
restart it again.

Office 2003 Setup Resource Center: Highlights & Top Issues
http://support.microsoft.com/gp/off2003set

You cannot update your Office 2003 program to Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;884298&Product=off2003

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

Repairing Office 2003 Installations
http://www.microsoft.com/office/ork/2003/five/ch19/MntB01.htm

Differences Between Repair and Reinstall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;298027

Office 2003 Service Pack 1 installs successfully but not all Office 2003
programs are updated
http://support.microsoft.com/default.aspx?scid=kb;en-us;884186

How to check the version of Office 2003 products
http://support.microsoft.com/kb/821549

Frequently asked questions about the local install source feature in Office
2003
http://support.microsoft.com/default.aspx?kbid=830168

How to troubleshoot an update installation by using log files in Office 2003
http://support.microsoft.com/default.aspx?kbid=884290

A History of Office 2003 Updates
http://support.microsoft.com/default.aspx?scid=kb;en-us;883677

You receive the "A required installation file SKU0A4.CAB could not be found"
error message when you try to update Office 2003 programs
http://support.microsoft.com/default.aspx?scid=kb;en-us;884824

If you're running from the update scanner, and it stops in the middle, try
getting the update from here and if
the Client file doesn't install, try the FullFile.

History of Office 2003 updates
http://www.microsoft.com/downloads/...A6-7CB1-4F61-837E-5F938254FC47&displaylang=en

If that fails, go to "eventvwr.msc" by typing that without quotes in your
run box>application>any error message numbers and copy during the time of
install attempt from MsiInstaller as source?

Another issue I've found is that it may be necessary after an unsuccessful
install to use the Windows Installer Cleanup Utility:

Use the Windows Installer Cleanup Utility:

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

Here's a very clear explanation of the WICU from Sloan Crayton [MS]:

"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
____________________________________________________________

hth, and it might be easier if you said what version of Office you have and
which particular updates you are trying to install.

Best,

Chad Harris

___________________________________________________________



I have had problems with downloading updates from the office web site since
I
insstalled Windows XP sp2. The download process starts in the normal way
but
stops without completing the down load. I have to abort the process to stop
it. I tried setting up the office update web site as a trusted web site and
that helped with ine update but now the latest update won't down load
similar
to before. Has anyone else experienced this problem?
 
C

casselp

Chad,
Thanks for your response. I was trying to install update KB837253 for
Office 2002 (i.e. Office XP poffessional) because the update site said it was
recommended. I did not experience the previously reported problem until
shortly after installing Windows XP pro sp2. That is why I think the problem
is connected with the installation. Prior to the install any downloads I
requested from the office update site worked fine. I would also like to
stress that the changes I made to make the office down load site a trusted
site seemed to work once with a previous update. But when the above update
was released the problem occurred again. The only other situation you may
want to know is that when I installed the update for SP2, I had been using
ZoneAlarm pro as my firewall also with no problems downloading office
updates. When sp2 was installed, I turned off the Microsoft firewall
function. Other that that I did nothing to alter the sp2 install. I had no
problems whatsoever with the sp1 install.

Chad Harris said:
Casselp--

The short answer is no to the best of my knowledge. I based this on Office
2003 but I don't know what version of Office you are updating.

There have been numerous problems with downloads/installs of different
Office updates, particularly SP1 for MOS 03 and other service packs for
other applications. Many have to do with the MSOCache folder being deleted
or source files missing With respect to some updates, using the Full File
may help.

I'm not sure what version of Office you have or what particular updates are
causing you a problem because you didn't say. That makes it difficult for
me to *guess which MSKBs might apply to you.* These issues have been tracked
and covered well on the microsoft.public.office.update group and if you scan
some of the posts, you'll see tips there and what I mean.

Also if you scan this \group, you will see some helpful hints about
overcoming some of the obstacles of installing MOS 03 SP1 in multiple
threads, including use of tools from the Resource Kit like LIS or use of the
Windows Uninstall Utility. Sloan Crayton [MS] and others have posted a
number of helpful tips on getting updates in, and on explanations on how to
use the tools like the local install source feature from the Office
Resource Kit for whichever version you have, and contexting problems with
the MSOCACHE folder or with source files missing.

To my knowledge, there haven't been any of the 190 plus MSKBs created for XP
SP2 that have to do with Office update difficulty but I'll check again.
However, there have been a number of MKSBs issued in reference to difficulty
updating Office, particularly with the last wave of SP1 updates for MOS 03
and related apps. I'll try to link a couple or more. One thing I have
noticed is that some but not all Office updates require the Office Source
Engine to be started in services or the installation will abort at setup.
Be sure before you try to download and install an Office update that you go
to "services.msc" in your run box and start the Office Source Engine by
right clicking and setting to manual and automatic and then clicking the
start button. Chances are it will not stay on later, which is fine because
it isn't needed until you install and it takes some CPU so you can manually
restart it again.

Office 2003 Setup Resource Center: Highlights & Top Issues
http://support.microsoft.com/gp/off2003set

You cannot update your Office 2003 program to Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;884298&Product=off2003

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

Repairing Office 2003 Installations
http://www.microsoft.com/office/ork/2003/five/ch19/MntB01.htm

Differences Between Repair and Reinstall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;298027

Office 2003 Service Pack 1 installs successfully but not all Office 2003
programs are updated
http://support.microsoft.com/default.aspx?scid=kb;en-us;884186

How to check the version of Office 2003 products
http://support.microsoft.com/kb/821549

Frequently asked questions about the local install source feature in Office
2003
http://support.microsoft.com/default.aspx?kbid=830168

How to troubleshoot an update installation by using log files in Office 2003
http://support.microsoft.com/default.aspx?kbid=884290

A History of Office 2003 Updates
http://support.microsoft.com/default.aspx?scid=kb;en-us;883677

You receive the "A required installation file SKU0A4.CAB could not be found"
error message when you try to update Office 2003 programs
http://support.microsoft.com/default.aspx?scid=kb;en-us;884824

If you're running from the update scanner, and it stops in the middle, try
getting the update from here and if
the Client file doesn't install, try the FullFile.

History of Office 2003 updates
http://www.microsoft.com/downloads/...A6-7CB1-4F61-837E-5F938254FC47&displaylang=en

If that fails, go to "eventvwr.msc" by typing that without quotes in your
run box>application>any error message numbers and copy during the time of
install attempt from MsiInstaller as source?

Another issue I've found is that it may be necessary after an unsuccessful
install to use the Windows Installer Cleanup Utility:

Use the Windows Installer Cleanup Utility:

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

Here's a very clear explanation of the WICU from Sloan Crayton [MS]:

"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
____________________________________________________________

hth, and it might be easier if you said what version of Office you have and
which particular updates you are trying to install.

Best,

Chad Harris

___________________________________________________________



I have had problems with downloading updates from the office web site since
I
insstalled Windows XP sp2. The download process starts in the normal way
but
stops without completing the down load. I have to abort the process to stop
it. I tried setting up the office update web site as a trusted web site and
that helped with ine update but now the latest update won't down load
similar
to before. Has anyone else experienced this problem?
 
C

casselp

Chad I forgot to check the box to notify me of replies I did it in this note.
Thanks.

Chad Harris said:
Casselp--

The short answer is no to the best of my knowledge. I based this on Office
2003 but I don't know what version of Office you are updating.

There have been numerous problems with downloads/installs of different
Office updates, particularly SP1 for MOS 03 and other service packs for
other applications. Many have to do with the MSOCache folder being deleted
or source files missing With respect to some updates, using the Full File
may help.

I'm not sure what version of Office you have or what particular updates are
causing you a problem because you didn't say. That makes it difficult for
me to *guess which MSKBs might apply to you.* These issues have been tracked
and covered well on the microsoft.public.office.update group and if you scan
some of the posts, you'll see tips there and what I mean.

Also if you scan this \group, you will see some helpful hints about
overcoming some of the obstacles of installing MOS 03 SP1 in multiple
threads, including use of tools from the Resource Kit like LIS or use of the
Windows Uninstall Utility. Sloan Crayton [MS] and others have posted a
number of helpful tips on getting updates in, and on explanations on how to
use the tools like the local install source feature from the Office
Resource Kit for whichever version you have, and contexting problems with
the MSOCACHE folder or with source files missing.

To my knowledge, there haven't been any of the 190 plus MSKBs created for XP
SP2 that have to do with Office update difficulty but I'll check again.
However, there have been a number of MKSBs issued in reference to difficulty
updating Office, particularly with the last wave of SP1 updates for MOS 03
and related apps. I'll try to link a couple or more. One thing I have
noticed is that some but not all Office updates require the Office Source
Engine to be started in services or the installation will abort at setup.
Be sure before you try to download and install an Office update that you go
to "services.msc" in your run box and start the Office Source Engine by
right clicking and setting to manual and automatic and then clicking the
start button. Chances are it will not stay on later, which is fine because
it isn't needed until you install and it takes some CPU so you can manually
restart it again.

Office 2003 Setup Resource Center: Highlights & Top Issues
http://support.microsoft.com/gp/off2003set

You cannot update your Office 2003 program to Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;884298&Product=off2003

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

Repairing Office 2003 Installations
http://www.microsoft.com/office/ork/2003/five/ch19/MntB01.htm

Differences Between Repair and Reinstall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;298027

Office 2003 Service Pack 1 installs successfully but not all Office 2003
programs are updated
http://support.microsoft.com/default.aspx?scid=kb;en-us;884186

How to check the version of Office 2003 products
http://support.microsoft.com/kb/821549

Frequently asked questions about the local install source feature in Office
2003
http://support.microsoft.com/default.aspx?kbid=830168

How to troubleshoot an update installation by using log files in Office 2003
http://support.microsoft.com/default.aspx?kbid=884290

A History of Office 2003 Updates
http://support.microsoft.com/default.aspx?scid=kb;en-us;883677

You receive the "A required installation file SKU0A4.CAB could not be found"
error message when you try to update Office 2003 programs
http://support.microsoft.com/default.aspx?scid=kb;en-us;884824

If you're running from the update scanner, and it stops in the middle, try
getting the update from here and if
the Client file doesn't install, try the FullFile.

History of Office 2003 updates
http://www.microsoft.com/downloads/...A6-7CB1-4F61-837E-5F938254FC47&displaylang=en

If that fails, go to "eventvwr.msc" by typing that without quotes in your
run box>application>any error message numbers and copy during the time of
install attempt from MsiInstaller as source?

Another issue I've found is that it may be necessary after an unsuccessful
install to use the Windows Installer Cleanup Utility:

Use the Windows Installer Cleanup Utility:

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

Here's a very clear explanation of the WICU from Sloan Crayton [MS]:

"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
____________________________________________________________

hth, and it might be easier if you said what version of Office you have and
which particular updates you are trying to install.

Best,

Chad Harris

___________________________________________________________



I have had problems with downloading updates from the office web site since
I
insstalled Windows XP sp2. The download process starts in the normal way
but
stops without completing the down load. I have to abort the process to stop
it. I tried setting up the office update web site as a trusted web site and
that helped with ine update but now the latest update won't down load
similar
to before. Has anyone else experienced this problem?
 
C

Chad Harris

Casselp--

I truly apologize i did not get back to you for 5 days. I was swamped and
not hitting these groups.

I read on that particular update. You can imagine at first I had no idea
what version of Office you were updating with what u pdate and that always
helps or makes a huge difference because certain updates have certain
problems and a lot of the recent Office 2003 updates have caused setup
problems for people that have gotten a good deal of attention.

Your update is here:
http://www.microsoft.com/downloads/...9a-9196-421b-83f0-3d2f93189028&displaylang=en

I noticed that one requirement for this update is to have Office XP Service
Pack 3 and Microsoft Windows Installer version 2.0 Since I began using MOS
2003 I haven't paid near as much attention to Office XP updates. I don't
know what version of Windows you're using in regards to the version of the
MSI or Windows installer.

Make sure to check event viewer by putting "eventvwr.msc" in your run box,
and going to the time under Applications of your attempted install and using
MSI as the source. Long for Error info rather than Event info there. You
can also go to the temp files and look for the OHotifix logs if you know how
to read them or get help with reading them as to logging the problem you
had.

Also I want to remind you to make sure to go to "services.msc" in the run
box--Services, and scroll alphabetically down to Office Source Engine
becasue many updates for Office require this to be set to either Manual or
Automatic--doesn't matter which and Started.

You should be getting an error when the install aborts and the error will be
found in Event Viewer if it is too transient for you to copy it but that
shouldn't be hapening as well. Often I take a screenshot of the error box
for easy retrieval if it is longer or has terms I can't remember.

Let me know if you have satisfied the above requirements and also I urge you
to put this problem on the Office Update group and setup groups where many
excellent people with expertise will be willing to help you--often from MSFT
who are Office udpate experts. I'll be happy to monitor this and help any
way I can.

I'd like to stress that so far I can find no SP2 specific issues with
respect to Office updates anywhere, but that doesn't mean they're not in
existence. However, by now there would probably be an MSKB and I don't find
any.

Good luck,

Chad Harris
__________________________________________




Chad I forgot to check the box to notify me of replies I did it in this
note.
Thanks.

Chad Harris said:
Casselp--

The short answer is no to the best of my knowledge. I based this on
Office
2003 but I don't know what version of Office you are updating.

There have been numerous problems with downloads/installs of different
Office updates, particularly SP1 for MOS 03 and other service packs for
other applications. Many have to do with the MSOCache folder being
deleted
or source files missing With respect to some updates, using the Full File
may help.

I'm not sure what version of Office you have or what particular updates
are
causing you a problem because you didn't say. That makes it difficult for
me to *guess which MSKBs might apply to you.* These issues have been
tracked
and covered well on the microsoft.public.office.update group and if you
scan
some of the posts, you'll see tips there and what I mean.

Also if you scan this \group, you will see some helpful hints about
overcoming some of the obstacles of installing MOS 03 SP1 in multiple
threads, including use of tools from the Resource Kit like LIS or use of
the
Windows Uninstall Utility. Sloan Crayton [MS] and others have posted a
number of helpful tips on getting updates in, and on explanations on how
to
use the tools like the local install source feature from the Office
Resource Kit for whichever version you have, and contexting problems with
the MSOCACHE folder or with source files missing.

To my knowledge, there haven't been any of the 190 plus MSKBs created for
XP
SP2 that have to do with Office update difficulty but I'll check again.
However, there have been a number of MKSBs issued in reference to
difficulty
updating Office, particularly with the last wave of SP1 updates for MOS 03
and related apps. I'll try to link a couple or more. One thing I have
noticed is that some but not all Office updates require the Office Source
Engine to be started in services or the installation will abort at setup.
Be sure before you try to download and install an Office update that you
go
to "services.msc" in your run box and start the Office Source Engine by
right clicking and setting to manual and automatic and then clicking the
start button. Chances are it will not stay on later, which is fine
because
it isn't needed until you install and it takes some CPU so you can
manually
restart it again.

Office 2003 Setup Resource Center: Highlights & Top Issues
http://support.microsoft.com/gp/off2003set

You cannot update your Office 2003 program to Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;884298&Product=off2003

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

Repairing Office 2003 Installations
http://www.microsoft.com/office/ork/2003/five/ch19/MntB01.htm

Differences Between Repair and Reinstall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;298027

Office 2003 Service Pack 1 installs successfully but not all Office 2003
programs are updated
http://support.microsoft.com/default.aspx?scid=kb;en-us;884186

How to check the version of Office 2003 products
http://support.microsoft.com/kb/821549

Frequently asked questions about the local install source feature in
Office
2003
http://support.microsoft.com/default.aspx?kbid=830168

How to troubleshoot an update installation by using log files in Office
2003
http://support.microsoft.com/default.aspx?kbid=884290

A History of Office 2003 Updates
http://support.microsoft.com/default.aspx?scid=kb;en-us;883677

You receive the "A required installation file SKU0A4.CAB could not be
found"
error message when you try to update Office 2003 programs
http://support.microsoft.com/default.aspx?scid=kb;en-us;884824

If you're running from the update scanner, and it stops in the middle,
try
getting the update from here and if
the Client file doesn't install, try the FullFile.

History of Office 2003 updates
http://www.microsoft.com/downloads/...A6-7CB1-4F61-837E-5F938254FC47&displaylang=en

If that fails, go to "eventvwr.msc" by typing that without quotes in your
run box>application>any error message numbers and copy during the time of
install attempt from MsiInstaller as source?

Another issue I've found is that it may be necessary after an unsuccessful
install to use the Windows Installer Cleanup Utility:

Use the Windows Installer Cleanup Utility:

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

Here's a very clear explanation of the WICU from Sloan Crayton [MS]:

"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
____________________________________________________________

hth, and it might be easier if you said what version of Office you have
and
which particular updates you are trying to install.

Best,

Chad Harris

___________________________________________________________



I have had problems with downloading updates from the office web site
since
I
insstalled Windows XP sp2. The download process starts in the normal way
but
stops without completing the down load. I have to abort the process to
stop
it. I tried setting up the office update web site as a trusted web site
and
that helped with ine update but now the latest update won't down load
similar
to before. Has anyone else experienced this problem?
 
B

Bill

I should change this to Office 2003 update problems. To take this discussion
further, I have encountered a problem after installing XP SP2 that I cannot
Install the latest Office 2003 update. This is the latest junk mail filter
update. Sorry I do not have the actual error as I am at work right now.
What has happened is the download proceded just fine. The installation
itself failed. It will not do the installation. I will admit I have not
attacked this problem as of yet, but I am curious. Our second machine, XP
w/o SP2, downloaded and installed the update without a hitch, so I know SP2
did something.

I will check a couple of things and may even try a Repair of Office to see
if the problem clears.

As you can tell I am in the preliminary troubleshooting stage. If there is
any suggestions I am open to them.

thanks!
Bill

Chad Harris said:
Casselp--

I truly apologize i did not get back to you for 5 days. I was swamped and
not hitting these groups.

I read on that particular update. You can imagine at first I had no idea
what version of Office you were updating with what u pdate and that always
helps or makes a huge difference because certain updates have certain
problems and a lot of the recent Office 2003 updates have caused setup
problems for people that have gotten a good deal of attention.

Your update is here:
http://www.microsoft.com/downloads/...9a-9196-421b-83f0-3d2f93189028&displaylang=en

I noticed that one requirement for this update is to have Office XP Service
Pack 3 and Microsoft Windows Installer version 2.0 Since I began using MOS
2003 I haven't paid near as much attention to Office XP updates. I don't
know what version of Windows you're using in regards to the version of the
MSI or Windows installer.

Make sure to check event viewer by putting "eventvwr.msc" in your run box,
and going to the time under Applications of your attempted install and using
MSI as the source. Long for Error info rather than Event info there. You
can also go to the temp files and look for the OHotifix logs if you know how
to read them or get help with reading them as to logging the problem you
had.

Also I want to remind you to make sure to go to "services.msc" in the run
box--Services, and scroll alphabetically down to Office Source Engine
becasue many updates for Office require this to be set to either Manual or
Automatic--doesn't matter which and Started.

You should be getting an error when the install aborts and the error will be
found in Event Viewer if it is too transient for you to copy it but that
shouldn't be hapening as well. Often I take a screenshot of the error box
for easy retrieval if it is longer or has terms I can't remember.

Let me know if you have satisfied the above requirements and also I urge you
to put this problem on the Office Update group and setup groups where many
excellent people with expertise will be willing to help you--often from MSFT
who are Office udpate experts. I'll be happy to monitor this and help any
way I can.

I'd like to stress that so far I can find no SP2 specific issues with
respect to Office updates anywhere, but that doesn't mean they're not in
existence. However, by now there would probably be an MSKB and I don't find
any.

Good luck,

Chad Harris
__________________________________________




Chad I forgot to check the box to notify me of replies I did it in this
note.
Thanks.

Chad Harris said:
Casselp--

The short answer is no to the best of my knowledge. I based this on
Office
2003 but I don't know what version of Office you are updating.

There have been numerous problems with downloads/installs of different
Office updates, particularly SP1 for MOS 03 and other service packs for
other applications. Many have to do with the MSOCache folder being
deleted
or source files missing With respect to some updates, using the Full File
may help.

I'm not sure what version of Office you have or what particular updates
are
causing you a problem because you didn't say. That makes it difficult for
me to *guess which MSKBs might apply to you.* These issues have been
tracked
and covered well on the microsoft.public.office.update group and if you
scan
some of the posts, you'll see tips there and what I mean.

Also if you scan this \group, you will see some helpful hints about
overcoming some of the obstacles of installing MOS 03 SP1 in multiple
threads, including use of tools from the Resource Kit like LIS or use of
the
Windows Uninstall Utility. Sloan Crayton [MS] and others have posted a
number of helpful tips on getting updates in, and on explanations on how
to
use the tools like the local install source feature from the Office
Resource Kit for whichever version you have, and contexting problems with
the MSOCACHE folder or with source files missing.

To my knowledge, there haven't been any of the 190 plus MSKBs created for
XP
SP2 that have to do with Office update difficulty but I'll check again.
However, there have been a number of MKSBs issued in reference to
difficulty
updating Office, particularly with the last wave of SP1 updates for MOS 03
and related apps. I'll try to link a couple or more. One thing I have
noticed is that some but not all Office updates require the Office Source
Engine to be started in services or the installation will abort at setup.
Be sure before you try to download and install an Office update that you
go
to "services.msc" in your run box and start the Office Source Engine by
right clicking and setting to manual and automatic and then clicking the
start button. Chances are it will not stay on later, which is fine
because
it isn't needed until you install and it takes some CPU so you can
manually
restart it again.

Office 2003 Setup Resource Center: Highlights & Top Issues
http://support.microsoft.com/gp/off2003set

You cannot update your Office 2003 program to Service Pack 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;884298&Product=off2003

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

Repairing Office 2003 Installations
http://www.microsoft.com/office/ork/2003/five/ch19/MntB01.htm

Differences Between Repair and Reinstall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;298027

Office 2003 Service Pack 1 installs successfully but not all Office 2003
programs are updated
http://support.microsoft.com/default.aspx?scid=kb;en-us;884186

How to check the version of Office 2003 products
http://support.microsoft.com/kb/821549

Frequently asked questions about the local install source feature in
Office
2003
http://support.microsoft.com/default.aspx?kbid=830168

How to troubleshoot an update installation by using log files in Office
2003
http://support.microsoft.com/default.aspx?kbid=884290

A History of Office 2003 Updates
http://support.microsoft.com/default.aspx?scid=kb;en-us;883677

You receive the "A required installation file SKU0A4.CAB could not be
found"
error message when you try to update Office 2003 programs
http://support.microsoft.com/default.aspx?scid=kb;en-us;884824

If you're running from the update scanner, and it stops in the middle,
try
getting the update from here and if
the Client file doesn't install, try the FullFile.

History of Office 2003 updates
http://www.microsoft.com/downloads/...A6-7CB1-4F61-837E-5F938254FC47&displaylang=en

If that fails, go to "eventvwr.msc" by typing that without quotes in your
run box>application>any error message numbers and copy during the time of
install attempt from MsiInstaller as source?

Another issue I've found is that it may be necessary after an unsuccessful
install to use the Windows Installer Cleanup Utility:

Use the Windows Installer Cleanup Utility:

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

Here's a very clear explanation of the WICU from Sloan Crayton [MS]:

"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
____________________________________________________________

hth, and it might be easier if you said what version of Office you have
and
which particular updates you are trying to install.

Best,

Chad Harris

___________________________________________________________



I have had problems with downloading updates from the office web site
since
I
insstalled Windows XP sp2. The download process starts in the normal way
but
stops without completing the down load. I have to abort the process to
stop
it. I tried setting up the office update web site as a trusted web site
and
that helped with ine update but now the latest update won't down load
similar
to before. Has anyone else experienced this problem?
 

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