Re: office updates Error: 0x800401F0 and System Restore Problem
From: Chad Harris (ddram32_nospam_at_yahoo.com)
Date: 08/05/04
- Next message: Doug Gentile: "Office Update Link Appears in a Different Language"
- Previous message: Brian R: "Performance issue in Outlook after installing Office 2003 SP1"
- In reply to: Nova5: "Re: office updates Error: 0x800401F0 and System Restore Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Aug 2004 21:11:10 -0400
Nova 5--
Do you think unloading DesktopX would be enough, or it has to be installed?
I installed all of the Office SP1 Updates--the Office SP1 specifically was
giving me a tough time but I didn't understand the Windows Uninstall Utility
or LIS so they might have helped me, but the Full File went in--but Desktop
X was not loaded at the time--but I was using Window Blinds' skins because
it would get pretty boring without changing skins and using Stardocks, Style
XP or something similar.
Thanks,
Chad Harris
"Nova5" <anonymous@discussions.microsoft.com> wrote in message
news:02d601c47a6e$c3584630$a501280a@phx.gbl...
Fortuantly the "corruption" is not irreversible. just
undo the sysrestore and you get back the proper info for
the uninstall to work.
I've used the WinInstaller cleanup util before with
success. However this time it was useless, it didnt see
the Office install. Probably a sideeffect of the
corrupted info.
Anyhow i found the source of my problem. I use some of
the desktop skinning apps from Stardock. DesktopX caused
all of my problems. So any of you other folk
experienceing this problem IF you use SD's DesktopX
uninstall it and you should be good to go.
>-----Original Message-----
>Thanks for the link to that KB.
>
>Wow!!!--If I understand you correctly, this is one of
the most *surprising
>things about SR* since I learned that the SR team fixed
a problem in Windows
>XP that locked people away from their restore points
(rather than they had
>done something like a dirty shutdown or turning off SR
to corrupt or lose
>their points as a reason why SR wasn't working for a lot
of people prior to
>XP SP1. I haven't seen this anywhere and it should be
in SR articles and SR
>MSKBs, but whoever wrote them ommitted this.
>
> "System Restore will corrupt the Windows Installer
registry
>> information for Office (and other applications). "
>
>What *other applications* does System Restore corrupt
and how can this be
>prevented. You indicate that the release of MSI 3.0
will correct the
>Windows Installer Registry Problems for Office, but will
it correct it for
>other applications as well?
>
>I just want to make sure I understand this correctly
because this is an
>important thing to know about System Restore I haven't
seen mentioned on any
>XP site, or group and nothing in any article on SR
anywhere including MSFT's
>sites--MSDN--Technet--wherever they have info on SR--
certainly not in any
>MSKB. I haven't seen it in *any of the many articles*
they have released on
>SP2 at Technet, including the *revised two articles*
that came out 8/3:
>
>Changes to Functionality in Microsoft Windows XP Service
Pack 2
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=7bd948d7-b791-40b6-8364-
685b84158c78&DisplayLang=en
>
>and Troubleshooting Windows Firewall in Microsoft
Windows XP Service Pack 2
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=a7628646-131d-4617-bf68-
f0532d8db131&DisplayLang=en
>
>Appendix A has this information.
>July 21 2004
>Added new sections: Distributed Transaction Coordinator,
Internet
>Information Services.
>
>Revised sections: Windows Firewall, Setup, Resultant Set
of Policy, Windows
>Update, Internet Explorer Feature Control Settings in
Group Policy, Internet
>Explorer URLAction Security Settings in Group Policy,
Internet Explorer MIME
>Handling Enforcement, Internet Explorer Network Protocol
Lockdown, Internet
>Explorer Local Machine Lockdown.
>
>You're saying this happens if you *run* system restore,
or if you even turn
>it on??? that Windows System Restore will corrupt the
Windows Installer
>registry information for Office (and other applications)-
-in any MSI up to
>2.0??? So anyone using XP SP2 shouldn't have to worry
about this because
>they will be using something even later than Windows ®
Installer. V
>3.00.3790.2162 when it goes RTM in a couple weeks or so?
>
>>From this page on Kelly's XP Site whose first part has
the MSDN article by
>Bobbie Harder
>
>System Restore for Windows XP
>http://www.kellys-korner-xp.com/xp_restore.htm
>
>is this article from Anshul Rawat [MS] System Restore,
Windows XP
>
>Highlights of System Restore fixes included in SP1
>
>1. Fix for SR not launching due to the framedyn.dll
error you all have been
>reporting.
>
>2. No calendar availaible in the SR wizard to select
restore points due to
>the the .htc file association being knocked out in the
> registry has been fixed.
>
>3. A fix for SR failing restores. A lot of you were
seeing failed restores
>when restoring to any restore point. Although some of
> it was attributed to SR data store corruption, in
most cases it was
>possibly due to locked file issues causing the restore
> process to fail, especially in scenarios where fast
user switching was
>used. This was a known issue which is now fixed in in
> SP1.
>
> This will hopefully resolve all cases for failed
restores and it would
>be great if all of you running into this problem could
> upgrade to SP1 and provide us feedback on this
issue, whether it has
>resolved the problem for you or not.
>
>4. Fix for drive table inconsistency on a machine
causing SR to not create
>restore points.
>
>5. Security fixes for SR to keep away those terrible
hackers and viruses.
>
>So upgrade to SP1 and provide us with some feedback on
your issues with SR
>and whether they are now resolved, especially when
dealing with failed
>restores.
>
>Anshul Rawat [MS]
>System Restore, Windows XP
>
>Thanks,
>
>Chad Harris
>
>_________________________________________________________
_
>
>"Sloan Crayton [MS]" <sloanc@online.microsoft.com> wrote
in message
>news:upC52HeeEHA.724@TK2MSFTNGP10.phx.gbl...
>
>> Yes, Windows System Restore will corrupt the Windows
Installer registry
>> information for Office (and other applications).
Windows Installer 3.0
>> (included in Windows XP SP2 when it ships) will fix
this bug.
>>
>> Since this corruption breaks all Office Setup
operations, a simple
>> uninstall will not be possible. You will need to use
the Windows
>> Installer Cleanup Utility (available via the KB
article at
>> http://support.microsoft.com/default.aspx?scid=kb;en-
us;290301) to remove
>> that registry information. You can then install all
of your Office
>> applications, and then install the updates. We have
this documented in
>> the KB article at
>> http://support.microsoft.com/default.aspx?scid=kb;en-
us;304498.
>>
>> Sloan Crayton
>> Microsoft
>>
>> "Nova5" <anonymous@discussions.microsoft.com> wrote in
message
>> news:b10d01c47976$340214f0$a301280a@phx.gbl...
>>> Detect'n'Repair is busted due to the problem. I think
my
>>> only resolution is to uninstall and reload it. i
belive
>>> SysRestore nuked the install.
>>>>-----Original Message-----
>>>>I have seen this error frequently with my failed
install
>>> along with two
>>>>others, and succeeded with the full file and still got
>>> this error when I
>>>>succeeded. I was using the install wizard from the
>>> scanner when I got it
>>>>installed, but I got this error even after I tried
using
>>> the downloaded
>>>>executables, so it shouldn't have been and couldn't
have
>>> been referencing
>>>>MSFT servers then.
>>>>
>>>>I am trying to find out what this error means.
Googling
>>> it comes up with no
>>>>clear explanation, and I couldn't find any discussion
of
>>> it in a chapter on
>>>>Office setup errors.
>>>>
>>>>I wonder, though if trying to things might help you.
>>>>
>>>>1) Run detect and repair if and only if you are sure
you
>>> that all your
>>>>Office apps are the same version. By default, Office
>>> automatically attempts
>>>>to repair a damaged installation using Application
>>> Recovery. Detect and
>>>>Repair can help when it doesn't do the job. But to
use
>>> Detect and Repair
>>>>with success, your versions and service pack levels of
>>> all applications
>>>>should be the same. There is also a repair method
from
>>> the Setup CD that is
>>>>less user friendly using command switches that I have
no
>>> experience with.
>>>>
>>>>Detect and Repair from Help in Any Application or
>>> Add/Remove
>>>>
>>>>Repairing Office 2003 Installations
>>>>http://www.microsoft.com/office/ork/2003/five/ch19/Mnt
B01
>>> .htm
>>>>
>>>>Why not try the Windows Installer Cleanup Utility?
>>>>
>>>>http://support.microsoft.com/default.aspx?scid=kb;en-
>>> us;290301
>>>>
>>>>I am pasting the best explanation of it I've seen that
>>> Sloan Crayton[MS]
>>>>posted to help me understand it. It may do the trick
>>> for you. I hate
>>>>shotgunning at an error I don't understand, but this
may
>>> be worth trying.
>>>>Certainly Detect and Repair is not going to hurt you
and
>>> takes little time.
>>>>
>>>>__________________________________
>>>>"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."
>>>>
>>>> from
>>> Sloan
>>>>Crayton[Microsoft]
>>>>_____________________________________________________
>>>>
>>>>
>>>>I also wonder if the LIS tool might help this error,
and
>>> hope someone who
>>>>knows it well will comment and maybe explain this
error:
>>>>
>>>>Change the Local Installation Source After the
>>> Installation
>>>>http://www.microsoft.com/office/ork/2003/journ/LISTool
.ht
>>> m.
>>>>
>>>>http://www.microsoft.com/office/ork/2003/two/ch3/DepC0
6.h
>>> tmTaking
>>>>Advantage of a Local Installation Source
>>>>
>>>>http://www.microsoft.com/office/ork/2003/journ/LISupdt
.ht
>>> m
>>>>
>>>>http://www.microsoft.com/office/ork/2003/journ/LISTool
.ht
>>> m
>>>>
>>>>Chad Harris
>>>>
>>>>______________________________________________________
___
>>> _
>>>>
>>>>
>>>>
>>>>
>>>>
>>>><anonymous@discussions.microsoft.com> wrote in message
>>>>news:9b6b01c478dc$05c48540$a601280a@phx.gbl...
>>>>> It should be mentioned its a downloaded copy of
>>> Fullfile
>>>>> SP1 and also the latest Outlook 2003 Junkmail
filter,
>>>>> both files report the same errors.
>>>>>>-----Original Message-----
>>>>>>The Info he is pulling from Event Log -
Applications is
>>>>>>the same i am getting, just a generic "It Didnt
work"
>>>>>>error.
>>>>>>
>>>>>>I also am getting these Cannot Apply Patch errors. I
>>> may
>>>>>>have caused this problem myself however. I
installed a
>>>>>>application that replaced some file that Outlook
2003
>>>>>>needed with a older version. the older version
caused
>>>>>>Outlook 2003 to be Crash-Happy. I used System
Restore
>>> to
>>>>>>backstep to a functional point where outlook wasn't
>>>>>>crashing any longer. problem is that i updated
Office
>>>>>>2003 first to try and fix it. then i did the system
>>>>>>restore.. somthing got crosswise and now its having
a
>>>>>>issue.
>>>>>>
>>>>>>I do get the same error output in Eventlog - Apps.
>>>>>>Event Type: Warning
>>>>>>Event Source: MsiInstaller
>>>>>>Event Category: None
>>>>>>Event ID: 1015
>>>>>>Date: 8/2/2004
>>>>>>Time: 5:27:55 PM
>>>>>>User: N/A
>>>>>>Computer: DARKSTAR
>>>>>>Description:
>>>>>>Failed to connect to server. Error: 0x800401F0
>>>>>>
>>>>>>For more information, see Help and Support Center at
>>>>>>http://go.microsoft.com/fwlink/events.asp.
>>>>>>
>>>>>>Event Type: Warning
>>>>>>Event Source: MsiInstaller
>>>>>>Event Category: None
>>>>>>Event ID: 1015
>>>>>>Date: 8/2/2004
>>>>>>Time: 5:27:55 PM
>>>>>>User: N/A
>>>>>>Computer: DARKSTAR
>>>>>>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-----
>>>>>>>When I try to install the downloaded "fullfile" SP1
>>> the
>>>>>>>Event Viewer event ID is 1015 and a description of
>>>>>>>Event Type: Warning
>>>>>>>Event Source: MsiInstaller
>>>>>>>Event Category: None
>>>>>>>Event ID: 1015
>>>>>>>Date: 8/2/2004
>>>>>>>Time: 13:39:55
>>>>>>>User: N/A
>>>>>>>Computer: JROWLAND
>>>>>>>Description:
>>>>>>>Failed to connect to server. Error: 0x800401F0
>>>>>>>
>>>>>>>The OHotfix says:
>>>>>>>
>>>>>>>Starting the log on 08/02/2004 at 13:39:55...
>>>>>>>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:\DOCUME~1\jrowland\LOCALS~1
>>>>>>>\Temp\IXP000.TMP\MAINSP1ff.msp is needed...
>>>>>>>The update failed.
>>>>>>>Finished processing the update on 08/02/2004 at
>>>>> 13:39:56.
>>>>>>>Encountered error 1635 while updating.
>>>>>>>Launching Setup Watson...
>>>>>>>Could not find dw.exe.
>>>>>>>
>>>>>>>When I try to install the downloaded "client" SP1
the
>>>>>>>Event Viewer is the same as the fullfile failure
>>> event.
>>>>>>>
>>>>>>>The OHotfix says:
>>>>>>>
>>>>>>>Starting the log on 08/02/2004 at 13:45:30...
>>>>>>>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:\DOCUME~1\jrowland\LOCALS~1
>>>>>>>\Temp\IXP000.TMP\MAINSP1op.msp is needed...
>>>>>>>The update failed.
>>>>>>>Finished processing the update on 08/02/2004 at
>>>>> 13:45:31.
>>>>>>>Encountered error 1635 while updating.
>>>>>>>Launching Setup Watson...
>>>>>>>Could not find dw.exe.
>>>>>>>
>>>>>>>
>>>>>>>>-----Original Message-----
>>>>>>>>Josh--
>>>>>>>>
>>>>>>>>I feel your install pain. I also *know* that you
>>> have
>>>>>>>error information
>>>>>>>>that may be helpful at two locations. One is
*Event
>>>>>>>Viewer* as I say. If
>>>>>>>>those two downloads would not install, then you
have
>>>>>>>error messages with the
>>>>>>>>source tagged MSI installer that you can paste as
I
>>>>>>>encouraged you to. You
>>>>>>>>now have error messages in Event Viewer. I was
>>> hoping
>>>>>>>you could get them
>>>>>>>>in, but at least you know how to reach the.
>>>>>>>>
>>>>>>>>The second place you have error information that
I'm
>>>>>>not
>>>>>>>equipped to
>>>>>>>>interpret is in the *O Hotfix* files as I
described
>>>>>>>above in your "O Hotfix"
>>>>>>>>Temp folder. You can skim these threads and see
>>> many
>>>>>>>people have tried to
>>>>>>>>post some of that log up, but it can get pretty
long
>>> (
>>>>>>a
>>>>>>>few MB) and is
>>>>>>>>probably best transmitted to the appropriate
expert
>>> as
>>>>>>>an attachment Sloan
>>>>>>>>Crayton from MS who has considerable expertise in
>>> this
>>>>>>>area has been kind
>>>>>>>>enough to encourage people to post this verbose
log.
>>>>>>>It's in English, Josh,
>>>>>>>>but it has terminology that most of us can't
>>> translate
>>>>>>>and may actually
>>>>>>>>require a special tool as does Hex--I want to find
>>> out
>>>>>>>if it does to
>>>>>>>>translate.
>>>>>>>>
>>>>>>>>In the meantime, I encourage you to try some of
the
>>>>>>tips
>>>>>>>I've collected that
>>>>>>>>work from posters on this group and the other
Office
>>>>>>>groups. I know your
>>>>>>>>frustration, because I spent a couple days trying
>>>>>>>various ways to get it
>>>>>>>>installed. Also (in my steps) check those
entries in
>>>>>>>services, and try to
>>>>>>>>delete as much of your Temp file as will delete--
the
>>>>>>>Hotfix files aren't
>>>>>>>>going to let you delete them so don't worry about
>>>>>>them.
>>>>>>>Also clear TIFs.
>>>>>>>>Some people have gotten it in by just uninstalling
>>>>>>>Office Web plug ins and
>>>>>>>>then reinstalling. I think no matter how expert
the
>>>>>>>person is, though, they
>>>>>>>>are going to want to see your Error messages and
your
>>>>>>>Hotfix_MSI log which
>>>>>>>>will have a number in parentheses in front of it.
>>>>>>>>
>>>>>>>>Any way I could help I would. Take a look at my
>>> list.
>>>>>>>>
>>>>>>>>Chad Harris
>>>>>>>>
>>>>>>>><anonymous@discussions.microsoft.com> wrote in
>>> message
>>>>>>>>news:978201c478b8$8802b190$a601280a@phx.gbl...
>>>>>>>>>I downloaded both the client and fullfile SP1 and
>>> both
>>>>>>>>> fail when installing with the same "The update
>>>>> cannot
>>>>>>>be
>>>>>>>>> applied" message.
>>>>>>>>>
>>>>>>>>>>-----Original Message-----
>>>>>>>>>>Josh--
>>>>>>>>>>
>>>>>>>>>>Go to the link I gave you. Try downloading from
>>>>>>there.
>>>>>>>>> ***Then your
>>>>>>>>>>problem may be over.*** I'm looking ahead to a
>>>>> second
>>>>>>>>> problem. Whether you
>>>>>>>>>>can get the updates you choose installed.
Several
>>>>>>>>> people who have posted
>>>>>>>>>>your problem yesterday solved it with the link I
>>> gave
>>>>>>>>> them directly to
>>>>>>>>>>downloads.
>>>>>>>>>>
>>>>>>>>>>Again--click here and forget the Office Updater
for
>>>>>>>>> now. They need to fix
>>>>>>>>>>it and they know it. If you check the threads
on
>>>>> this
>>>>>>>>> group, you aren't the
>>>>>>>>>>Lone Ranger having Problem reaching the cute
little
>>>>>>>>> Office Update Scanner
>>>>>>>>>>and I suspect that may generate the simple error
>>> you
>>>>>>>>> got, because I have
>>>>>>>>>>seen that a lot and it had nothing to do with me
>>>>> using
>>>>>>>>> this link and getting
>>>>>>>>>>the updates in. The next thing I'm concerned
about
>>>>> is
>>>>>>>>> your getting them
>>>>>>>>>>installed once you reach them particularly MOS
2003
>>>>>>>>> which has been
>>>>>>>>>>problematic for quite a few people.
>>>>>>>>>>
>>>>>>>>>>Downloads for Office 2003:
>>>>>>>>>>http://office.microsoft.com/officeupdate/downloa
ds.
>>> as
>>>>> p
>>>>>>x
>>>>>>>?
>>>>>>>>>
>>> CategoryID=CD010224941033&CTT=4&Origin=ES790020041033
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>I think this will easily get you the downloads.
>>>>> Then
>>>>>>>>> if you can't get one
>>>>>>>>>>in follow my checklist. Go to the link, and
your
>>>>>>>>> problem may be solved
>>>>>>>>>>there if the updates install without a hitch.
>>>>>>>>>>
>>>>>>>>>>Take a look at Event Viewer again. You should
have
>>>>>>>some
>>>>>>>>> 4 digit errors like
>>>>>>>>>>say 15630 that might correspond to MSKBs. I'm
not
>>>>>>>>> talking about Event ID #
>>>>>>>>>>which won't help. I mean in the text of the
error
>>>>>>>>> message where your time
>>>>>>>>>>out error was you might see something similar to
>>> but
>>>>>>>>> with a different
>>>>>>>>>>error--take a look and see if you don't see a
list
>>> of
>>>>>>>>> MSIInstaller Errors.
>>>>>>>>>>
>>>>>>>>>> I'm not sure how to context that error, but
since
>>>>>>>it's
>>>>>>>>> often seen after a
>>>>>>>>>>download from the MSFT server (I see it often
when
>>> I
>>>>>>>>> install from my
>>>>>>>>>>download file), I don't think that one is
>>>>>>consequential
>>>>>>>>> and I think it
>>>>>>>>>>references a small timeout on your ISP server.
>>> I'll
>>>>>>>>> have to research that.
>>>>>>>>>>You can also copy the whole error each time to
the
>>>>>>>>> clipboard by hitting that
>>>>>>>>>>button under the down error in the box.
>>>>>>>>>>
>>>>>>>>>>See if you have any other errors like this 1336
>>> error
>>>>>>>>> with its explanation.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>try going down my checklist, particularly making
>>> sure
>>>>>>>>> those two services are
>>>>>>>>>>on. One of those hints may help you, and the
first
>>>>>>one
>>>>>>>>> I'd start with is
>>>>>>>>>>going to the downloads link I gave you that
>>> bypasses
>>>>>>>the
>>>>>>>>> Office Update
>>>>>>>>>>Scanner (which right now is on the blink for a
lot
>>> of
>>>>>>>>> people) and if you
>>>>>>>>>>can't get the client file of SP1 2003 to go in,
>>> then
>>>>>>>try
>>>>>>>>> the Full File.
>>>>>>>>>>That tip is working for some people. Then look
at
>>>>> the
>>>>>>>>> others. I gave you
>>>>>>>>>>an example of the type errors that'll provide
>>>>>>>meaningful
>>>>>>>>> information below.
>>>>>>>>>>Note--you are after this kind of info:
>>>>>>>>>>
>>>>>>>>>>Error 1336. There was an error creating a
temporary
>>>>>>>file
>>>>>>>>> that is needed to
>>>>>>>>>>complete this installation. Folder:
C:\Config.Msi\
>>>>>>>>>>
>>>>>>>>>>Event Type: Error
>>>>>>>>>>Event Source: MsiInstaller
>>>>>>>>>>Event Category: None
>>>>>>>>>>Event ID: 11336
>>>>>>>>>>Date: 7/28/2004
>>>>>>>>>>Time: 8:38:31 PM
>>>>>>>>>>
>>>>>>>>>>Description:
>>>>>>>>>>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
>>>>>>>>>>
>>>>>>>>>>Best,
>>>>>>>>>>
>>>>>>>>>>Chad Harris
>>>>>>>>>>
>>>>>>>>>>________________________________________________
___
>>> __
>>>>> _
>>>>>>_
>>>>>>>__
>>>>>>>>> _________
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>><anonymous@discussions.microsoft.com> wrote in
>>>>> message
>>>>>>>>>>news:981201c478ae$0049b690$a301280a@phx.gbl...
>>>>>>>>>>
>>>>>>>>>>>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/downl
oad
>>> s.
>>>>> a
>>>>>>s
>>>>>>>px
>>>>>>>>> ?
>>>>>>>>>>>
>>>>>>CategoryID=CD010224941033&CTT=4&Origin=ES79002004103
3
>>>>>>>>>>>>
>>>>>>>>>>>>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/downl
oad
>>> s.
>>>>> a
>>>>>>s
>>>>>>>px
>>>>>>>>> ?
>>>>>>>>>>>
>>>>>>CategoryID=CD010224941033&CTT=4&Origin=ES79002004103
3
>>>>>>>>>>>>
>>>>>>>>>>>>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
/LI
>>> ST
>>>>> o
>>>>>>o
>>>>>>>l.
>>>>>>>>> ht
>>>>>>>>>>> m.
>>>>>>>>>>>>Change the Local Installation Source After the
>>>>>>>>>>> Installation
>>>>>>>>>>>>
>>>>>>>>>>>>http://www.microsoft.com/office/ork/2003/two/c
h3/
>>> De
>>>>> p
>>>>>>C
>>>>>>>06
>>>>>>>>> .h
>>>>>>>>>>> tmTaking
>>>>>>>>>>>>Advantage of a Local Installation Source
>>>>>>>>>>>>
>>>>>>>>>>>>Other LIS Resources:
>>>>>>>>>>>>
>>>>>>>>>>>>http://www.microsoft.com/office/ork/2003/journ
/LI
>>> Su
>>>>> p
>>>>>>d
>>>>>>>t.
>>>>>>>>> ht
>>>>>>>>>>> m
>>>>>>>>>>>>
>>>>>>>>>>>>http://www.microsoft.com/office/ork/2003/journ
/LI
>>> ST
>>>>> o
>>>>>>o
>>>>>>>l.
>>>>>>>>> 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/c
h3/
>>> De
>>>>> p
>>>>>>A
>>>>>>>03
>>>>>>>>> .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: Doug Gentile: "Office Update Link Appears in a Different Language"
- Previous message: Brian R: "Performance issue in Outlook after installing Office 2003 SP1"
- In reply to: Nova5: "Re: office updates Error: 0x800401F0 and System Restore Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
