Jim,
From :
http://support.microsoft.com/?id=249873
" Dllname was loaded, but the DllRegisterServer or
DllUnregisterServer entry point was not found.
Dllname may not be exported, or a corrupted version of Dllname may
be in memory. Consider using Pview to detect the file and remove it"
If you have slipstreamed SP2 with your original XP CD than you can
choose to use sfc /scannow to replace the files.
IF NOT, take a look in WINDOWS\ServicePackFiles\i386 . On my system,
SP2's files are backed up here. If you find this folder is present
on your system, then take a look in the WINDOWS\system32 folder for
iuengine.dll and wuaserv.dll . Right click them, choose Properties,
click the Version tab. Both file's version number MUST be the same
as those in WINDOWS\ServicePackFiles\i386. If not, then SP2 did not
install fully.
You can rename the files in WINDOWS\system32 by right clicking them,
choosing Rename, change the .dll extension to .old, and then copy
the correct version files from WINDOWS\ServicePackFiles\i386
and then register the .dll's.
Otherwise you will have to uninstall SP2 and then reinstall it.
Please let me know if this worked for you or not.
MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============
Jim wrote:
> MowGreen,
>
> Errors-a-plenty..............
>
> My first reply to your suggestion went to error so I will try again.
>
> After following your suggestion and that of one other the problem was
> corrected even thought the two listed dll's would not register.
>
> wuauserv.dll was loaded, but the DllRegisterServer entry point was not
> found. This file can not be registered.
>
> iuengine.dll was loaded, but the DllRegisterServer entry point was not
> found. This file can not be registered.
>
> Thanks for your help.
>
>
>
>
> "MowGreen [MVP]" wrote:
>
>
>>Well Jim you're the proud owner of a new error message. Google now
>>shows you as the only hit on this specific error message. 
>>
>>First check that the date and time of the system are accurate.
>>If you're running a 3rd party firewall ( ZoneAlarm, NIS, etc. )
>>make sure that it's not blocking ports 80 or 443 .
>>Also, try temporarily disabling your antivirus program and any
>>script blocking component of it prior to accessing WU.
>>
>>If no joy :
>>Go to Start, Run, type in
>>net.exe stop wuauserv
>>Click OK or press Enter
>>
>>Reregister these files from Start, Run, type these in and
>>click OK or press Enter after each one :
>>
>>regsvr32.exe wuapi.dll
>>regsvr32.exe wuaueng.dll
>>regsvr32.exe wuaueng1.dll
>>regsvr32.exe wuauserv.dll
>>regsvr32.exe wucltui.dll
>>regsvr32.exe wups.dll
>>regsvr32.exe wuweb.dll
>>regsvr32.exe MSXML3.dll
>>
>>net.exe start wuauserv
>>
>>If the above does not resolve the issue follow the steps
>>here :
>>http://v5.windowsupdate.microsoft.co...cleid=21&ln=en
>>
>>
>>MowGreen [MVP]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>
>>Jim wrote:
>>
>>
>>>MowGreen
>>>
>>>Here is the info from WINDOWS directory as of this morning;
>>>
>>>https://v5.windowsupdate.microsoft.c...ce/client.asmx
>>>2004-10-16 05:07:11-0700 1540 6b0 URL for server is
>>>http://v5stats.windowsupdate.microso...ebService.asmx
>>>2004-10-16 05:07:11-0700 1540 6b0 Trying to upload 1 events using cached
>>>cookie.
>>>2004-10-16 05:07:11-0700 3024 bd4 Operation completed due to earlier error.
>>>(hr=8024402B)
>>>2004-10-16 05:07:11-0700 3024 bd4 Unable to complete asynchronous search
>>>successfully. (hr=8024402B)
>>>2004-10-16 05:07:16-0700 1540 6b0 DetectCompressionType returning type 0,
>>>hr=0x1
>>>2004-10-16 05:07:16-0700 1540 6b0 Successfully uploaded 1 events.
>>>2004-10-16 05:07:16-0700 1540 6b0 Deleted event cache file at
>>>C:\WINDOWS\SoftwareDistribution\EventCache\{418 F2D0F-313C-4E55-A475-A5D7CECD72D5}.bin.
>>>2004-10-16 05:07:16-0700 1540 6b0 REPORT EVENT:
>>>{6276E661-9240-4E0F-A3BA-C98167DEE5DE} 94 2004-10-16
>>>05:07:11-0700 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024402b WindowsUpdate Failure Software
>>>Synchronization Error: Agent failed detecting with reason: 0x8024402b
>>>
>>>
>>>
>>>"MowGreen [MVP]" wrote:
>>>
>>>
>>>
>>>>Jim
>>>>
>>>>Open the WindowsUpdate.log found in the WINDOWS directory. Scroll
>>>>down to the bottom for the "real" error code. I believe that
>>>>0x8024402B is a generic error. Google returns absoulutely nothing on
>>>>it. Then go back to the Windows Update Troubleshooter and see if
>>>>that specific error code is listed. If not, post it here.
>>>>
>>>>MowGreen [MVP]
>>>>===============
>>>> *-343-* FDNY
>>>>Never FOrgotten
>>>>===============
>>>>
>>>>Jim wrote:
>>>>
>>>>
>>>>
>>>>>[Error number: 0x8024402B]
>>>>> Windows Update has encountered an error and cannot display the requested
>>>>>page.
>>>>>I have checked the troublshooting section but this error is not listed.
>>>>>
>>>>>I previously used Windows Update on Oct 6th and had no problem.
>>>>>
>>>>>Any suggestion,
>>>>
>>>>
>>