Re: Cannot Install Updates
- From: Roughneck <Roughneck@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 Aug 2005 08:20:20 -0700
Robert, first of all, thanks again for your time and interest. In this
reply, I'll repost an example of the log file from a failed desktop install,
followed by the log file from the successful laptop install. I'll then do a
follow-up post to address your other thought/comments.
LOG FILE from FAILED DESKTOP INSTALL
================================================================================
4.094: 2005/08/10 15:31:28.546 (local)
4.094: c:\928415903098f230c4a0b3\update\update.exe (version 6.1.22.4)
4.125: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned:
0x7f
4.125: Hotfix started with following command line:
4.234: CreateUserInterface: GetProcAddress for DefineInstallCustomUI
failed: 0x7f
4.297: DoInstallation: CustomizeCall Failed: 0xb7
4.328: Cannot create a file when that file already exists.
9.344: Message displayed to the user: Cannot create a file when that file
already exists.
9.344: User Input: OK
9.344: KB885222 installation did not complete.
10.828: Message displayed to the user: KB885222 installation did not complete.
10.828: User Input: OK
10.828: Update.exe extended error code = 0xb7
10.828: Update.exe return code was masked to 0x643 for MSI custom action
compliance.
================================================================================
LOG FILE from SUCCESSFUL LAPTOP INSTALL
================================================================================
3.375: 2005/08/10 10:28:45.129 (local)
3.375: c:\8a8d6f9c5f57249c08d0d3\update\update.exe (version 6.1.22.4)
3.406: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned:
0x7f
3.422: Hotfix started with following command line:
3.437: CreateUserInterface: GetProcAddress for DefineInstallCustomUI
failed: 0x7f
5.172: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
error 0x2
5.172: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
error 0x2
5.172: ---- Old Information In The Registry ------
5.172: Source:C:\Program Files\HPQ\Shared\hpqwmi.events
5.172: Destination:
5.172: ---- New Information In The Registry ------
5.172: Source:C:\Program Files\HPQ\Shared\hpqwmi.events
5.172: Destination:
5.234: SetProductTypes: InfProductBuildType=BuildType.IC
5.234: SetAltOsLoaderPath: No section uses DirId 65701; done.
5.297: DoInstallation: FetchSourceURL for
c:\8a8d6f9c5f57249c08d0d3\update\update_SP2QFE.inf failed
5.297: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
5.297: BuildCabinetManifest: update.url absent
5.297: Starting AnalyzeComponents
5.297: AnalyzePhaseZero used 0 ticks
5.297: No c:\windows\INF\updtblk.inf file.
5.297: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
5.297: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
5.297: Enumerating Devices of 1394, GUID
{6bdd1fc1-810f-11d0-bec7-08002be2092f}
5.781: OEM file scan used 484 ticks
5.812: AnalyzePhaseOne: used 515 ticks
5.812: AnalyzeComponents: Hotpatch analysis disabled; skipping.
5.812: AnalyzeComponents: Hotpatching is disabled.
5.812: FindFirstFile c:\windows\$hf_mig$\*.*
6.547: AnalyzeForBranching used 16 ticks.
6.578: AnalyzePhaseTwo used 31 ticks
6.578: AnalyzePhaseThree used 0 ticks
6.578: AnalyzePhaseFive used 0 ticks
6.578: AnalyzePhaseSix used 0 ticks
14.453: AnalyzeComponents used 9156 ticks
14.453: Downloading 0 files
14.453: bPatchMode = FALSE
14.453: Inventory complete: ReturnStatus=0, 9156 ticks
16.516: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB885222$
16.516: Num Ticks for invent : 11219
16.547: VerifySize: Unable to verify size: Source = NULL:
c:\windows\inf\HFX6.tmp
16.594: Copied file: c:\windows\inf\branches.inf
21.187: Allocation size of drive C: is 4096 bytes, free space = 44901535744
bytes
21.187: AnalyzeDiskUsage: Skipping EstimateDiskUsageForUninstall.
21.187: Drive C: free 42821MB req: 6MB w/uninstall: NOT CALCULATED.
21.187: CabinetBuild complete
21.187: Num Ticks for Cabinet build : 4671
21.187: DynamicStrings section not defined or empty.
21.187: FileInUse:: need to restart already, turn off
22.187: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
22.312: Num Ticks for Backup : 1125
22.453: Num Ticks for creating uninst inf : 141
22.469: Registering Uninstall Program for -> KB885222, KB885222 , 0x0
22.469: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
28.359: System Restore Point set.
28.687: Copied file: C:\WINDOWS\system32\spmsg.dll
28.844: PFE2: Not avoiding Per File Exceptions.
29.000: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB885222.cat with error 0x57
30.594: Copied file: C:\WINDOWS\system32\DRIVERS\ohci1394.sys
30.594: Copied file: C:\WINDOWS\Driver Cache\i386\ohci1394.sys
30.844: DoInstallation: Installing assemblies with source root path:
c:\8a8d6f9c5f57249c08d0d3\
30.844: Num Ticks for Copying files : 8391
30.859: Num Ticks for Reg update and deleting 0 size files : 15
30.859: DoInstallation: ApplyAdminSystemAclsRecursive for
c:\windows\$hf_mig$\KB885222 failed; error=0x00000003
30.953: ---- Old Information In The Registry ------
30.953: Source:C:\Program Files\HPQ\Shared\hpqwmi.events
30.953: Destination:
30.953: ---- New Information In The Registry ------
30.953: Source:C:\Program Files\HPQ\Shared\hpqwmi.events
30.953: Destination:
38.687: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
38.687: IsRebootRequiredForFileQueue:
c:\windows\system32\drivers\ohci1394.sys was no-delay replaced; reboot is
required.
38.687: DoInstallation: A reboot is required to complete the installation of
one or more files.
38.687: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
error 0x2
38.687: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
error 0x2
38.687: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
46.453: RebootNecessary = 1,WizardInput = 1 , DontReboot = 0, ForceRestart = 0
Shutdown Initiated in Self Extractor
***
================================================================================
--
So much to learn... So little time.
"Robert Aldwinckle" wrote:
> "Roughneck" <Roughneck@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:5D34AE8C-0E45-449F-B193-F52B62ACA37E@xxxxxxxxxxxxxxxx
> > COMPARE THE LOGS
> > -------------------------------
> > As suggested, I compared the KB885222 log files from the laptop and desktop.
> > While it's easy to see where they begin to differ, there's nothing that
> > gives me a clue as to why they take a different path where they do. i.e.
> > They both start off the same and list the same instructions, processes, and
> > return codes for the first five lines -- then they differ.
> >
> > Lines 6 and 7 of the desktop's log read:
> > * DoInstallation: CustomizeCall Failed: 0xb7
> > * Cannot create a file when that file already exists.
>
> Shouldn't FileMon show you an access here which does not happen
> in the clean install? Unless you already know which file this message
> is referring to but you're not telling us?
>
>
> >
> > Lines 6 and 7 of the laptop's log read:
> > * In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with error
> > 0x2
> > * In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with error
> > 0x2
>
>
> That's interesting. This perhaps gives some hope that the /verbose
> option would differentiate what key is being accessed (attempted to be
> accessed) in each case. Alternatively, you could try running RegMon
> again with both a clean and problem install, trying to identify this difference.
> Of course if it turns out to be the same key but at different locations in the
> script you will be no further ahead on this tack. It would be nice to know
> what file "line 11660" is referring to. Then you could browse the damn
> thing and see exactly what each line would be doing. FileMon might
> help with that goal too, depending on your filter of course. For example,
> if you are running with the filter that I suggested which includes ;Update;
> and the program doing the install was called update.exe I expect that
> that you could be seeing all Reads that the program is doing such as
> whatever Reads are necessary to interpret the script. Etc.
>
>
> >
> > The desktop's log ends soon afterward (see the example in my initial post).
> > The laptop's log is much longer -- probably more than anyone would care to
> > read through, so I won't post it unless someone wants to see it. Bottom line
> > is, I can see where the two logs diverge, but don't know what to make of it.
> > :-(
>
>
> If you can't find the /verbose log post both regular install logs here inline
> or E-mail them to my reply address as attachments.
>
>
> >
> >
> > RUNNING the UPDATE with the /VERBOSE parm
> > -----------------------------------------------------------
> > Again, as suggested, I gave this a whirl and it ran fine (even showed up in
> > the KB885222 log file), but I haven't been able to determine what output, if
> > any, was generated. After running the update with this parm, I did browse
> > the root folder of my C: drive, as well as several windows folders with the
> > files arranged by date created, date modified, etc. -- but didn't see
> > anything I could identify as meaningful/useful.
>
>
> Did you miss the idea of "searching"? In XP I use Search Companion.
> However, in NT4 I would have used the equivalent File Find tool.
> Both allow you to specify you want to find all files which changed
> on a particular day and then sort the results by the Date Modified column.
> Doing that gives you a list in timestamp order (e.g. down to a minute)
> of files which were written that day. Hence any files which were written
> by the update should be grouped together within the small range of minutes
> that it took to run the update. I have never used your OS but hopefully
> it has an equivalent tool? Alternatively, you could use dir/a/od/s/tw *
> at your directory root and, depending on how your dates show, you could
> pipe that through a find filter to list just files which changed on that day
> and a sort filter to just limit your attention to the filenames which changed
> in that short period. E.g. if I was doing this today and since my date format
> is YYYY-MM-DD in a cmd window I would enter:
>
> <example>
> cd /d %SystemDrive%\
> dir/a/od/s/tw * | find "2005-08-11" | sort >chgfiles.txt
> notepad chgfiles.txt
> </example>
>
> In fact, since I probably would know at least the hour and perhaps
> even the tens digit of the minutes value as common factors
> for what I was really interested in I would probably make that find
> argument even more precise than just a specification of a particular
> day. Etc.
>
> Note that an advantage of the Search Companion/File Find
> technique is that you can sort by details without losing track
> of which directory the file comes from. With the dir/s approach
> the directory information would be lost by the find and the sort
> filters so you would have to do subsequent finds of some kind
> based on filename to find out where it was actually located.
>
>
> >
> >
> > RUNNING FILEMON during the UPDATE
> > -----------------------------------------------
> > Finally, as suggested, I found/installed Filemon and had that running during
> > the update attempt on the desktop. I found several error messages that I
> > thought might be relevant at first, so I uninstalled the update from the
> > laptop, installed Filemon there, and re-ran the update on the laptop while
> > Filemon was running. But on the laptop, I saw the same errors reported by
> > Filemon that I saw for the desktop -- so again, I wasn't able to identify
> > anything specific/unique to the failed attempt on the desktop.
> >
> >
> > OTHER THINGS I DID
> > ------------------------------
> > * Disabled the firewire controller, rebooted, ran the update.
> > RESULT -- NO CHANGE.
> > * Removed the PCI card with the firwire ports (eliminating the firewire
> > controller completely). Rebooted, ran the update.
> > RESULT -- NO CHANGE.
> > * Reinstalled the PCI card with the firewire ports (reinstalling the
> > firewire controller). Booted from a hard drive that I had cloned months ago
> > with Norton Ghost. Ran the update.
> > RESULT -- SUCCESS.
> >
> > So.... that tells me it's not a hardware related problem. I am wondering
> > about one thing though. When I ran Windows Update a week or so ago, the
> > update process told me I had to download a new/updated version of the Windows
> > Update software. After doing that, it checked my system to verify I had a
> > legit copy of Windows. It acknowleded I did, but said it detected changes to
> > my system configuration -- I don't remember the exact message, but I
> > understood it to mean hardware changes. It indicated this would not prevent
> > me from applying the updates available at the time, but that it "might" cause
> > problems in the future. There was no further explanation given.
>
>
> See WGA FAQ which Carey (e.g.) has been posting recently?
>
> <quote>
> Q: What is activation?
>
> A: Activation reduces piracy by associating your Windows Product Key
> —the 25-character security code located on your Certificate of Authenticity
> (usually affixed to your software package, PC, or laptop)
> —to a PC hardware key. Microsoft stores this information in a database
> so that no one else can use your Product Key on another PC.
>
>
> </quote>
>
> Hmm... That's less informative than it might be I think.
> Let's look at the Activation FAQ instead:
>
> http://www.microsoft.com/piracy/activation_faq.mspx
>
> (MSN search for
> activation site:microsoft.com
> )
>
> <quote>
> Can hardware components be changed and upgraded?
>
> Product Activation is able to tolerate a certain degree of change
> in a hardware configuration by allowing a current hash value
> to have a degree of difference from the hash value that was
> originally activated. As a result, users can change their hardware
> without the product believing it is on a different PC than the one
> it was activated on. If the user completely overhauls the hardware
> making substantial hardware changes (even over long periods of time),
> reactivation may be required. In that case, users may need to contact
> a Microsoft customer service representative by telephone to reactivate.
> </quote>
>
>
> > I'm still
> > able to run Windows Update and install the critical updates listed -- in
> > fact, I just did that again today. This KB885222 is the only download I'm
> > having (have ever had) trouble with. I don't know what to make of it. The
> > error messages given during the update attempt are worthless in the sense
> > they don't identify what file(s) the process is having trouble with. Ditto
> > for the update's log file, as far as I can tell. Very frustrating.
>
>
> Hang in there. I think you're getting closer to a clear diagnosis. <eg>
>
>
> HTH
>
> Robert
> ---
>
>
>
.
- References:
- Re: Cannot Install Updates
- From: Roughneck
- Re: Cannot Install Updates
- From: Robert Aldwinckle
- Re: Cannot Install Updates
- From: Roughneck
- Re: Cannot Install Updates
- From: Roughneck
- Re: Cannot Install Updates
- From: Robert Aldwinckle
- Re: Cannot Install Updates
- Prev by Date: RE: Windows Update Fails...
- Next by Date: Re: Cannot install updates on server
- Previous by thread: Re: Cannot Install Updates
- Next by thread: Re: Cannot Install Updates
- Index(es):
Relevant Pages
|
