Rollup1 ACCESS DENIED

I currently have a number of W2K SP4 servers that just won't take the
rollup. Here's the log output directly after it finished copying all
the various files:

99.860: Num Ticks for Copying files : 48438
100.641: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
ProductInstall.GlobalRegistryChanges.Install error: 0x5
100.641: INF_REGISTRY Failed
100.641: DoInstallationoRegistryUpdates failed
100.641: Failed Deleting C:\WINNT\system32\msiinst.tmp 2
100.657: VerifySize: Unable to verify size: Source = NULL:
c:\winnt\oem17.cat
100.938: Access is denied.

It naturally then displays and Access denied error...the strange thing
being I'm logged in as local admin. Any idea's guys?

So strange? Ill just work on anther computer first? Idon' know whats really
happening please? maybe there's HACKERS? Please Authorize .ALPHA, BLUE LEADER
RED LEADERS to overcome all BASES in the computer. JUST KIDDING THANK
U Though. BUY

"" wrote:

> I currently have a number of W2K SP4 servers that just won't take the
> rollup. Here's the log output directly after it finished copying all
> the various files:
>
> 99.860: Num Ticks for Copying files : 48438
> 100.641: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> ProductInstall.GlobalRegistryChanges.Install error: 0x5
> 100.641: INF_REGISTRY Failed
> 100.641: DoInstallationoRegistryUpdates failed
> 100.641: Failed Deleting C:\WINNT\system32\msiinst.tmp 2
> 100.657: VerifySize: Unable to verify size: Source = NULL:
> c:\winnt\oem17.cat
> 100.938: Access is denied.
>
> It naturally then displays and Access denied error...the strange thing
> being I'm logged in as local admin. Any idea's guys?
>
>

<> wrote in message news: ups.com...
>I currently have a number of W2K SP4 servers that just won't take the
> rollup. Here's the log output directly after it finished copying all
> the various files:
>
> 99.860: Num Ticks for Copying files : 48438
> 100.641: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> ProductInstall.GlobalRegistryChanges.Install error: 0x5
> 100.641: INF_REGISTRY Failed
> 100.641: DoInstallationoRegistryUpdates failed
> 100.641: Failed Deleting C:\WINNT\system32\msiinst.tmp 2
> 100.657: VerifySize: Unable to verify size: Source = NULL:
> c:\winnt\oem17.cat
> 100.938: Access is denied.
>
> It naturally then displays and Access denied error...the strange thing
> being I'm logged in as local admin. Any idea's guys?
>


I suspect this indicates a permissions problem with some registry keys.
Unfortunately, the log doesn't show you what they are.
One approach to solving this would be to run RegMon and FileMon
concurrently--FileMon just so you can get some timestamp information
to give you some context within the RegMon trace.

Here's an excerpt from a previous reply which contains more detail
about the procedure:

<excerpt>
Run RegMon with a fairly loose filter, e.g. perhaps just update.exe
would be a tight as you could go on that side. FileMon on the other hand
would be run just to try to get a more accurate timestamp for the above log
records; so it could be as tight as update.log for writes only. (The writes
will show you the length of the records being written so if there is a pattern
in the log based on the length of their records you can then map the timestamps
from the FileMon trace onto the less precise timestamps of the update's log
records and then from there find the precise set of RegMon trace records
which correspond with those intervening milleseconds.) Depending on how
many RegMon records you capture you might also be able to spot the
problem in it by eyeballing its trace only. E.g. it would probably be somewhere
near the bottom of that trace.
</excerpt>

The most important point about the idea is that both tools must be
recording accurate timestamps on each record and there are
non-default options which need to be set to do that.


Here's another excerpt (from a different issue) which mentions that:

<excerpt>
As for RegMon it's really pretty simple to use. Just download it
from SysInternals, install it and start it when you want to trace.
It always prompts you for an Include filter before starting.
As I said I think that wuauclt would be sufficient for this case.
If you want to use FileMon, same thing and the filter will be
WindowsUpdate.log Don't forget to check the Clock Time
and Milleseconds options on both. To capture their output
just select all records with a normal Windows keyboard
procedure such as Home, Shift-End,Ctrl-c (actually, I guess
if the selected line is already at the bottom that Shift-Home,
Ctrl-c would be more efficient <w>).
</excerpt>


Good luck

Robert Aldwinckle
---

On my server the following keys were set to read only:


HKLM/Software/Microsoft/Works/6.0/Calendar &
HKLM/Software/Microsoft/Works/7.0/Calendar

Once I added administrators and gave the group full access, the Update
rollup worked. You may find the same is true on your systems.

"" wrote:

> I currently have a number of W2K SP4 servers that just won't take the
> rollup. Here's the log output directly after it finished copying all
> the various files:
>
> 99.860: Num Ticks for Copying files : 48438
> 100.641: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> ProductInstall.GlobalRegistryChanges.Install error: 0x5
> 100.641: INF_REGISTRY Failed
> 100.641: DoInstallationoRegistryUpdates failed
> 100.641: Failed Deleting C:\WINNT\system32\msiinst.tmp 2
> 100.657: VerifySize: Unable to verify size: Source = NULL:
> c:\winnt\oem17.cat
> 100.938: Access is denied.
>
> It naturally then displays and Access denied error...the strange thing
> being I'm logged in as local admin. Any idea's guys?
>
>

This post is possibly a bit old now, but I really wanted to highlight it as
I had similar issues since ages with a half broken machine that didn't want
to do the WMP10->11 upgrade on XP :

Thanks a lot to you Robert Aldwinckle :
Regmon.exe is definitely the ultimate troubleshooter when installers are
stuck with "Access denied" on dodgy registry key permissions.


"Robert Aldwinckle" wrote:

> <> wrote in message news: ups.com...
> >I currently have a number of W2K SP4 servers that just won't take the
> > rollup. Here's the log output directly after it finished copying all
> > the various files:
> >
> > 99.860: Num Ticks for Copying files : 48438
> > 100.641: DoRegistryUpdates:UpdSpInstallFromInfSection Failed for
> > ProductInstall.GlobalRegistryChanges.Install error: 0x5
> > 100.641: INF_REGISTRY Failed
> > 100.641: DoInstallationoRegistryUpdates failed
> > 100.641: Failed Deleting C:\WINNT\system32\msiinst.tmp 2
> > 100.657: VerifySize: Unable to verify size: Source = NULL:
> > c:\winnt\oem17.cat
> > 100.938: Access is denied.
> >
> > It naturally then displays and Access denied error...the strange thing
> > being I'm logged in as local admin. Any idea's guys?
> >
>
>
> I suspect this indicates a permissions problem with some registry keys.
> Unfortunately, the log doesn't show you what they are.
> One approach to solving this would be to run RegMon and FileMon
> concurrently--FileMon just so you can get some timestamp information
> to give you some context within the RegMon trace.
>
> Here's an excerpt from a previous reply which contains more detail
> about the procedure:
>
> <excerpt>
> Run RegMon with a fairly loose filter, e.g. perhaps just update.exe
> would be a tight as you could go on that side. FileMon on the other hand
> would be run just to try to get a more accurate timestamp for the above log
> records; so it could be as tight as update.log for writes only. (The writes
> will show you the length of the records being written so if there is a pattern
> in the log based on the length of their records you can then map the timestamps
> from the FileMon trace onto the less precise timestamps of the update's log
> records and then from there find the precise set of RegMon trace records
> which correspond with those intervening milleseconds.) Depending on how
> many RegMon records you capture you might also be able to spot the
> problem in it by eyeballing its trace only. E.g. it would probably be somewhere
> near the bottom of that trace.
> </excerpt>
>
> The most important point about the idea is that both tools must be
> recording accurate timestamps on each record and there are
> non-default options which need to be set to do that.
>
>
> Here's another excerpt (from a different issue) which mentions that:
>
> <excerpt>
> As for RegMon it's really pretty simple to use. Just download it
> from SysInternals, install it and start it when you want to trace.
> It always prompts you for an Include filter before starting.
> As I said I think that wuauclt would be sufficient for this case.
> If you want to use FileMon, same thing and the filter will be
> WindowsUpdate.log Don't forget to check the Clock Time
> and Milleseconds options on both. To capture their output
> just select all records with a normal Windows keyboard
> procedure such as Home, Shift-End,Ctrl-c (actually, I guess
> if the selected line is already at the bottom that Shift-Home,
> Ctrl-c would be more efficient <w>).
> </excerpt>
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>