Re: office update site/office 2003 sp 1 fails Go Here/TryThese/Post Errors!
anonymous_at_discussions.microsoft.com
Date: 08/02/04
- Next message: Chad Harris: "Re: office update site/office 2003 sp 1 fails Again Josh Go Here!!!"
- Previous message: Chad Harris: "Re: office update site/office 2003 sp 1 fails Go Here/TryThese/Post Errors!"
- In reply to: Chad Harris: "Re: office update site/office 2003 sp 1 fails Go Here/TryThese/Post Errors!"
- Next in thread: Chad Harris: "Re: office update site/office 2003 sp 1 fails Again Josh Go Here!!!"
- Reply: Chad Harris: "Re: office update site/office 2003 sp 1 fails Again Josh Go Here!!!"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 2 Aug 2004 09:30:19 -0700
I get the following from event viewer on my lastest
failed attempt to install sp1.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 8/2/2004
Time: 11:25:45
User: N/A
Computer: JROWLAND
Description:
Failed to connect to server. Error: 0x800401F0
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
>-----Original Message-----
>Josh--
>
>You should be able to go to the download for each update
you haven't
>installed that you need from this page. Just skip the
scanner or the
>update catalogue if it's not working for you. It
reminds me a lot of
>Windows Update V4 that's about to be replaced by V5.
>
>Downloads for Office 2003:
>http://office.microsoft.com/officeupdate/downloads.aspx?
CategoryID=CD010224941033&CTT=4&Origin=ES790020041033
>
>I know this will work. I don't know how to fix the
Office Update "scanner"
>problem that so many people are complaining about. But
MSFT Office
>personnel are monitoring the group, so hopefully they
can make that happen.
>
>If you will go to Event Viewer putting "eventvwr.msc" in
your run box, and
>stretch it out and click on Application, at the time of
your problem you
>will see errors (I mean if you try to install MOS 2003
SP1 or any other
>update from the link I gave you and can't.) If it
doesn't install, post up
>your errors that will be listed under source as MSI
Installer.
>
>That way, some of the Office experts either MVPs or MSFT
experts in Office
>setup like Sloan Crayton [MS] who are teaching me can
give you direction.
>Sometimes the errors refer you to the Hotfix Verbose
Logs in the O Hotfix
>folder in your (%Temp% in the run box) Temporary
folder. To interpret these
>logs takes special expertise/tools these people have
that I don't.
>
>Here is my work in progress list of some things that may
help you to do that
>are helping others if you get a problem installing.
Office 2003 SP1 is
>statistically the one that has had the most of the
September 27, 2004
>releases from the Office site. Your problem, of course
depends on specific
>error information from Event Viewer and/or the Verbose
Hotfix logs:
>
>*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/officeupdate/downloads.aspx?
CategoryID=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.ht
m.
>Change the Local Installation Source After the
Installation
>
>http://www.microsoft.com/office/ork/2003/two/ch3/DepC06.h
tmTaking
>Advantage of a Local Installation Source
>
>Other LIS Resources:
>
>http://www.microsoft.com/office/ork/2003/journ/LISupdt.ht
m
>
>http://www.microsoft.com/office/ork/2003/journ/LISTool.ht
m
>
>*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 the
>two
>entries for the Office Source Engine and the Windows
Installer 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.
If you find it
>necessary to uninstall the Web Add-Ins, just reinstall
them after the Update
>that was giving you a problem goes in.
>
>*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.h
tm
>
>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.
>
>
>Best,
>
>Chad Harris
>
>"Josh Rowland" <anonymous@discussions.microsoft.com>
wrote in message
>news:96c701c478a6$5f9ee690$a301280a@phx.gbl...
>> When I go to office update-check for updates I get:
>>
>> The Office Update site is unable to check for updates
on
>> this computer. This may be happening because of one of
>> the following reasons:
>>  You do not have administrative privileges for
>> this computer.
>>  There is a network problem and the detection
>> catalog used by the Office Update site failed to
>> download. Go back to the Downloads home page and try
>> running detection again.
>>  Windows Installer patch files (.MSP files) from
>> previously applied Office updates are missing from the
>> \Windows\Installer hidden directory on your computer.
MSP
>> files are stored on your computer after update
>> installation completes because they need to be
referenced
>> for future update operations. If the files are missing
>> you will not be able to apply Office updates. You may
>> also be unable to uninstall Office products as a result
>> of the same problem. Please contact Microsoft Product
>> Support Services for assistance.
>>  You installed Office updates in the past and then
>> upgraded from Windows Installer version 1.0 to Windows
>> Installer version 1.1. For more information see the KB
>> article Windows Installer May Prompt for Install Source
>> if Unavailable.
>>
>> When I download Sp1 directly I get:
>>
>> The update cannot be applied.
>>
>> Any help is appreciated.
>
>
>.
>
- Next message: Chad Harris: "Re: office update site/office 2003 sp 1 fails Again Josh Go Here!!!"
- Previous message: Chad Harris: "Re: office update site/office 2003 sp 1 fails Go Here/TryThese/Post Errors!"
- In reply to: Chad Harris: "Re: office update site/office 2003 sp 1 fails Go Here/TryThese/Post Errors!"
- Next in thread: Chad Harris: "Re: office update site/office 2003 sp 1 fails Again Josh Go Here!!!"
- Reply: Chad Harris: "Re: office update site/office 2003 sp 1 fails Again Josh Go Here!!!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
