Re: Cannot Install Updates

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.

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

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.
:-(


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.


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. 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.




"Roughneck" wrote:

> Robert,
>
> Thanks for your help!
>
> Comparing the log files is a great idea -- I should have thought of that.
> :-| I bought the laptop for my wife and she's been pretty busy with it, so
> it may not be home/available for a day or two. But IIRC, I uninstalled the
> update on the laptop when I determined it didn't result in any speed
> improvement -- guess I'll have to check to see if the log file was deleted as
> part of the uninstall, and re-install the update if the log file is gone.
>
> I'm not familiar with FileMon -- I'll check it out though and see if it can
> help shed any light on the issue. Ditto for /verbose. Finally, I did
> consider the possibility of having to do a reboot after disabling the 1394
> Host Controller, but didn't pursue that for two reasons: 1. Device Manager
> changed the status of the controller in the device list immediately after my
> request to disable it. 2. Right after disabling it (and without rebooting),
> I connected an external drive via a FW port and the device was "not"
> recgognized/acknowledge. I then enabled the controller again (without
> rebooting) and XP recognized the drive immediately afterward. Even so, it
> was still on the back of my mind -- guess it's always better to error on the
> side of caution. :-)
>
> PS: Is there a way to edit/make corrections to a post after it's been
> submitted? Some forums offer that option, but I'm not seeing it here.
> --
> So much to learn... So little time ;-)
>
>
> "Robert Aldwinckle" wrote:
>
> > "Roughneck" <Roughneck@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:CABB331D-70E9-412D-BFBA-E986BDA7C275@xxxxxxxxxxxxxxxx
> > > This is my first time to visit one of the forums, so please let me know if I
> > > break any of the rules. :-)
> > >
> > > I was able to install KB885222 without a hitch on my laptop, but I get the
> > > same error messages as Drew when trying to install the update on my desktop
> > > -- i.e. "Cannot create a file when that file already exists" AND "KB885222
> > > installation did not complete") .
> >
> > How do the two logs compare? You won't be able to do a diff on them
> > because of timestamps etc. but there may be missing or extra messages
> > which could be important clues. Sometimes when there are a lot of
> > significant differences I go so far as to create separate copies of the logs
> > with extraneous difference such as timestamps etc. edited out so the compare
> > is more informative. I have found that at least some comparison is useful
> > because it is easy to be misled by recoverable errors when you aren't familiar
> > with the logic of the install.
> >
> >
> > >
> > > Before attempting to install the patch on either of my machines, I did a
> > > system search and also searched the registry, looking for any occurrence of
> > > kb885222 -- I didn't find anything on either machine. I also checked the
> > > registries for any occurrence of the parm "SidSpeed". Again, nothing showed
> > > up in either registry. So I installed the update on the laptop. After the
> > > install, I checked the registry, and found several entries related to my 1394
> > > Host Controller had been added -- each entry had a "SidSpeed" parm that had
> > > been set to a value of "2", indicating a 1394 speed/rate of S400. Great sof
> > > far -- then I hit the problem on the desktop.
> > >
> > > Based on the suggestions/comments in this topic, I ran SIGVERIF per the
> > > instructions given. Two folder names were listed, so I removed (i.e. I
> > > moved the folders to a different path). Based on other comments in previous
> > > posts, I also disabled my 1394 Controller -- just in case the update saw it
> > > as busy. When I ran the update, it failed again, but this time with a
> > > different message -- "The system cannot find the path specified".
> >
> > I'm wondering if you need a boot in between disabling and moving the file
> > and retrying the update?
> >
> > BTW I would try using FileMon to monitor at least the suspect modules
> > in case that adds to your understanding of what is going on.
> > Include enough pattern also to filter in writes to the log file so you can see
> > if there is any correlation between accesses to the modules (especially
> > failed accesses) and writes to the log. You may be able to use the record
> > length to complete the inference of which write to log is being done when.
> > Unfortunately usually there isn't sufficient granularity in the timestamps
> > especially in the log to correlate records and trace entries that way.
> >
> >
> > > Soooo, I
> > > moved the folders back, but removed all the files within them (again, moved
> > > them to a different path). The update failed again, but this time with the
> > > message "The system cannot find the file specified". Bottome line is, if
> > > even one of the files from the folder are present, I get the error about the
> > > file already existing -- but if I remove them all, I get the error about not
> > > being able to find the file specified. I checked the KB885222 log file, but
> > > the only times entries were made were the times I got the message that the
> > > install could not create a file when that file already exists. The other
> > > errors did not generate errors in the log. All the log entries that were
> > > generated looked like the example below. The only thing that changed from
> > > one entry (failed install) to the next, was the beginning of the path name
> > > in the 2nd text line. i.e. it would read:
> > > c:\"some value"\update\update.exe (version 6.1.22.4)
> > >
> > > ================================================================================
> > > 3.516: 2005/08/08 09:38:46.578 (local)
> > > 3.516: c:\16f228652539418a2cc58627508533\update\update.exe (version 6.1.22.4)
> > > 3.531: DoInstallation: GetProcAddress(InitializeCustomizationDLL) Returned:
> > > 0x7f
> > > 3.531: Hotfix started with following command line:
> > > 3.578: CreateUserInterface: GetProcAddress for DefineInstallCustomUI
> > > failed: 0x7f
> > > 3.672: DoInstallation: CustomizeCall Failed: 0xb7
> > > 3.672: Cannot create a file when that file already exists.
> > > 7.078: Message displayed to the user: Cannot create a file when that file
> > > already exists.
> > > 7.078: User Input: OK
> > > 7.078: KB885222 installation did not complete.
> > > 7.969: Message displayed to the user: KB885222 installation did not complete.
> > > 7.969: User Input: OK
> > > 7.969: Update.exe extended error code = 0xb7
> > > 7.969: Update.exe return code was masked to 0x643 for MSI custom action
> > > compliance.
> > > 0.812:
> > > ================================================================================
> > >
> > > Any ideas/thoughts would be greatly appreciated.
> >
> >
> > As an alternative (or in addition to) the other diagnostics I have suggested
> > you could try using the /verbose option on the install (e.g. when executed
> > manually from a commad line). As above take care that there is no possibility
> > that the modules are still in use. I'm not sure where the /verbose log goes.
> > You may have to hunt for files which are changed by the update (e.g. search
> > for files changed on that day and then sort them by Date Modified, etc.)
> >
> >
> > Good luck
> >
> > Robert
> > ---
> >
> >
> > > --
> > > So much to learn... So little time ;-)
> > >
> > >
> > > "Robert Aldwinckle" wrote:
> > >
> > >> "Drew" <Drew@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > >> news:79EEF3CC-2D30-433A-B716-7F9EC3D0D829@xxxxxxxxxxxxxxxx
> > >> > When I try to install KB885222 I get the following error messages -
> > >> >
> > >> > "cannot create a file when that file already exists
> > >> >
> > >> > kb885222 installation did not complete"
> > >> >
> > >> > This happens whether I try to install from the web or from my temp file.
> > >> >
> > >> > I know that the SP2 version of ohci1394.sys is installed in win/sys32/ &
> > >> > loaded but I would have thought that on the reboot it would be overwritten?
> > >>
> > >> It may be in use? Find out which device is using that module and if possible
> > >> stop it before trying to install that patch. Alternatively try using a safe mode boot
> > >>
> > >> Hmm... if that is your primary harddrive that might be a bit difficult!
> > >> I agree that the update should be handling this for you but what it should be doing
> > >> is installing the driver file(s) with alias(es) and then renaming them during a boot.
> > >>
> > >> However, depending on what exactly the message is referring to the problem
> > >> may be occurring long before that eventuality.
> > >>
> > >> If you have a KB885222.log created by the install attempt (or find any other diagnostic
> > >> files which have modification times at the same time as the install attempt) use them
> > >> to look for clues which refine your symptom description.
> > >>
> > >> Another possibility that I would look at would be to check if the message
> > >> is erroneous or misleading. E.g. which file? what version is being installed?
> > >> what version already exists? Etc. Use the "File Information" in the KB article
> > >> as a guide for some modules you could start such checking with.
> > >>
> > >>
> > >> Good luck
> > >>
> > >> Robert Aldwinckle
> > >> ---
> > >>
> > >>
> > >> >
> > >> > No probs with .cat files
> > >> >
> > >> > "HNG" wrote:
> > >> >
> > >> >> There might be unsigned secure catalog (.cat) files. Need to remove them.
> > >> >> Try this -
> > >> >> 1: Run SIGVERIF.exe
> > >> >> 2: Click Advanced button
> > >> >> 3: Select Look for other files that are not digitally signed
> > >> >> 4: In the Look in this folder box type in C:\WINDOWS\SYSTEM32\CATROOT
> > >> >> (Edit path a necessary depending on where Windows is installed)
> > >> >> 5: Check Include Subfolders
> > >> >> 6: Click OK, then click Start
> > >> >>
> > >> >> When the report completes it should list any unsigned files.
> > >> >>
> > >> >> Look for .CAT files. If there are any .CAT files, find them and move them
> > >> >> out of the CATROOT folder. Try installing the update now.
> > >> >>
> > >> >> Alternately, you can close Sigverif.exe tool and review the Sigverif.txt
> > >> >> report.
> > >> >>
> > >> >> ---------
> > >> >>
> > >> >>
> > >> >> "Johnny Boy" wrote:
> > >> >>
> > >> >> > I get the same error trying to download and install KB885222-x86-ENU.exe
> > >> >> >
> > >> >> > "Scott Reading" wrote:
> > >> >> >
> > >> >> > > Hi
> > >> >> > >
> > >> >> > > When downloading updates off the update site, it downloads them fine, but
> > >> >> > > doesnt install them. The site just says unbale to install. I have gone to my
> > >> >> > > D:\Wutemp\ folder and the updates sit in there. When I individually run them,
> > >> >> > > I get a setup error, "The Data is Invalid".
> > >> >> > >
> > >> >> > > Any ideas?
> > >> >> > >
> > >> >> > > Kind regards
> > >> >> > >
> > >> >> > > Scott Reading
> > >>
> > >>
> > >>
> >
> >
> >
.

Loading