Re: KB956572 fails to install on SBS 2003 server
- From: "Robert Aldwinckle" <robald@xxxxxxxxxxxxx>
- Date: Tue, 21 Apr 2009 12:37:38 -0400
"David Sherman" <dshermin@xxxxxxxxxxxxx> wrote in message news:eacru4phocvipbuv10nkcmhi2iteuqrusn@xxxxxxxxxx
It was appeended to the same log. I just copied the new information.
I'm pretty sure that you should be looking for another file...
http://support.microsoft.com/kb/262841
(Microsoft Support search for
prefer:verbose intitle:update
)
<quote>
/verbose Enable verbose logging.
Creates %Windir%\CabBuild.log upon install that details files to be copied.
Using this switch may cause the installation to occur much slower.
Version 5.3.24.3 and later versions support the /verbose switch.
For compatibility with older versions, the /v switch can be used.
</quote>
More generally I was suggesting you *search* for any and all files
which the update may have created or changed to be sure that you
were looking at *all* diagnostics available to you.
BTW it was Process Monitor (ProcMon) which I was suggesting
you could use to supplement any diagnostics that you do get.
Typically log messages are written one line at a time with varying
lengths and ProcMon shows these writes. So you can infer which
write you are looking at from the length given by each record
and by the pattern of lengths that you see in the log the write
is for.
Also, using Process Explorer only will essentially give you
just a GUI way of doing the tasklist /fi command I suggested
you could use. And again, because the module is so highly used
the only value that either list can have is through a comparison
of otherwise identical machines where one allows the update
and the other doesn't.
For example, if one has the problem system support software
for a device that the other doesn't that could be a good clue
to prevent that from happening--e.g. apply the update in safe mode
from only a command prompt if necessary. Etc.
Good luck
Robert
---
I will try your suggestions that next time I do to the site which will
be inthe 2nd tuesday of May.
On Tue, 21 Apr 2009 01:39:54 -0400, "Robert Aldwinckle"
<robald@xxxxxxxxxxxxx> wrote:
"David Sherman" <dshermin@xxxxxxxxxxxxx> wrote in message news:4nppu4tm1219bnirdveqgned95eh460q8g@xxxxxxxxxx
using verbose command, here is the log file:
That looks like the same log file.
I think /verbose is supposed to create a different one.
Have you tried a search to find out if there are any other
diagnostic files being created?
...
3.844: Enumerating Devices of computer, GUID
{4d36e966-e325-11ce-bfc1-08002be10318}
4.297: OEM file scan used 469 ticks
8.047: Message displayed to the user: The file
c:\windows\system32\ntdll.dll is open or in use by another
application.
Since the error appears after "Enumerating Devices"
one hopeful guess would be that the program which
is the problem is related to a device. Is there such a program
in that list you gave us above? I don't run SBS so I don't know
how much of what you listed is necessary or standard.
BTW have you tried doing the update in safe mode to try to eliminate
such extraneous sources of interference as drivers and services
that you shouldn't need to achieve the install? E.g. if you have the update
to install manually you might even be able to do it in safe mode
with command only. (I bet your tasklist /fi command lists a lot fewer
tasks then. <eg>) Alternatively, start in normal safe mode and then
just stop or kill whatever is running that isn't needed to do the install.
Good luck
Robert
---
.
- References:
- KB956572 fails to install on SBS 2003 server
- From: David Sherman
- Re: KB956572 fails to install on SBS 2003 server
- From: Susan Bradley
- Re: KB956572 fails to install on SBS 2003 server
- From: David Sherman
- Re: KB956572 fails to install on SBS 2003 server
- From: Robert Aldwinckle
- Re: KB956572 fails to install on SBS 2003 server
- From: David Sherman
- Re: KB956572 fails to install on SBS 2003 server
- From: Robert Aldwinckle
- Re: KB956572 fails to install on SBS 2003 server
- From: David Sherman
- KB956572 fails to install on SBS 2003 server
- Prev by Date: Re: Windows Update won't load (error number 0x80072EFD)
- Next by Date: Re: kb956572 installs succesfully, then repeats
- Previous by thread: Re: KB956572 fails to install on SBS 2003 server
- Next by thread: Automatic updates is causing a fault in NTdll.dll
- Index(es):
Relevant Pages
|