Re: 0x8024D007, automatic update service starting, REGSVR32 wuauen
- From: mentalmidget99 <mentalmidget99@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Mar 2007 12:06:16 -0800
Robert,
Thank you for responding!
Are you using auditing to try to diagnose this? Are there any results from that?
What do you mean by auditing?
Same failure as the regsvr32 wuaueng is getting?
Yes, when I try to register wuaueng.dll, I get the same error (Invalid
access to memory location) as when I try to start the BITS service.
I would try using bitsadmin to get more info and possibly repair BITS.
E.g. using the XPsp2 version of it enter (in a cmd window):
bitsadmin /util /version /verbose
I will look into what bitsadmin is. I'm running Win server 2003, and I'm
assuming by your comment I can use the XPsp2 repair BITS command on this
server?
Thank you again.
Kathy
"Robert Aldwinckle" wrote:
"mentalmidget99" <mentalmidget99@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message.
news:1FBA5226-F226-459E-9160-0B3B10D32696@xxxxxxxxxxxxxxxx
Server Stats:
Windows Server 2003 R2, Enterprise Edition with SP1 installed
On an ADS domain however not a domain controller
The problem I'm having:
Cannot update Windows either by going to update.microsoft.com nor by using
automatic windows update
Symptoms:
1. Automatic update service won't start - sits in 'starting' mode and I'm
unable to stop it. (BITS service will run fine)
2. When I try to register wuaueng.dll by using the command REGSVR32
wuaueng.dll I get this error message "LoadLibrary("wuaueng.dll") failed -
Invalid access to memory location
My guess is that a dependent module is missing or corrupt.
Normally should at least get a non-zero return code if DllRegisterServer fails.
You could try using DependencyWalker's Profiler feature
to execute the regsvr32 command with a trace of its calls.
That would hopefully expose the source of the failure.
Another tool which might help by showing you the stack at the time of failure
is ProcMon. However, it looks as if it is a recoverable failure so it might not
be exposed enough for ProcMon to see it.
3. When I try to install windows updates by going to
http://update.microsoft.com/microsoftupdate/v6/ I get this message "The
website has encountered a problem and cannot display the page you are trying
to view. The options provided below might help you solve the problem." Error
number: 0x8024D007
That code isn't even documented by the standard list.
http://docxp.mvps.org/WU5-ERR.htm
E.g. 0x8024D006 is the last one in that series and just looks like
some unknown error in WU Setup.
What I've tried:
1. Rebooting
2. Items listed in KB909444
http://support.microsoft.com/default.aspx/kb/909444/en-us
In the advanced security properties of the .clb files in the%windir%/registration folder, made sure that the Allow inheritable auditing
entries from the parent to propagate to this object and all objects. Include
these with entries explicitly defined here option is selected.
Are you using auditing to try to diagnose this?
Are there any results from that?
....Gave Everyone group the following permission: Traverse permissions (“List Folder Contentsâ€) on %windir%3. Gave Everyone group read permissions on HKEY_CLASSES_ROOT in regedit
Gave Everyone group the following permission: Traverse permissions (“List Folder Contentsâ€) on %windir%\Windows
Here is a piece of the c:\windows\windowsupdate.log
Some System Events:
Event ID: 7023 - The Background Intelligent Transfer Service service
terminated with the following error: Invalid access to memory location.
Event ID: 10010 - The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not
register with DCOM within the required timeout.
Same failure as the regsvr32 wuaueng is getting?
The last patches installed were on 10/15/06:
KB924496, KB923191, KB922819, KB924191, KB923414
I'm afraid to try KB555336
http://support.microsoft.com/default.aspx?scid=kb;en-us;555336 because this
is a productions server and I'm not exactly sure what this procedure will do.
Any information would be most appreciated!
I would try using bitsadmin to get more info and possibly repair BITS.
E.g. using the XPsp2 version of it enter (in a cmd window):
bitsadmin /util /version /verbose
Good luck
Robert Aldwinckle
---
- References:
- Re: 0x8024D007, automatic update service starting, REGSVR32 wuaueng.dl
- From: Robert Aldwinckle
- Re: 0x8024D007, automatic update service starting, REGSVR32 wuaueng.dl
- Prev by Date: Re: MSXML 4.0 SP Security Update (KB927978) in Vista
- Next by Date: Re: WGAN seems to have returned
- Previous by thread: Re: 0x8024D007, automatic update service starting, REGSVR32 wuaueng.dl
- Next by thread: Re: Error Code 0x633
- Index(es):
Relevant Pages
|