Thanks for the feedback RodrYguez, probably the server was busy at the time and later it all worked
out.
Kaylene

--
===========================
TaurArian [MS-MVP] 2005-2006
===========================


"RodrYguez" <rodryguez@free.po> wrote in message news:5279r1ppffkgu1tvhjbbq3vvntqih27rbh@4ax.com...
>
> had the same one time ago.
> it reworked by itself.
>
> On Thu, 29 Dec 2005 17:29:16 +1100, "TaurArian [MS-MVP]"
> <taurarianREMOVECAPS@gmail.com> wrote :
>
>>0x8007041D - 2147023843 - ERROR_SERVICE_REQUEST_TIMEOUT
>>The service did not respond to the start or control request in a timely fashion
>>
>>You receive a "0x8007041D" error when you visit the Windows Update Web site
>>http://support.microsoft.com/?scid=kb;en-us;902322
>>
>>If the above is not the case - this can happen when the server is extremely busy. Try again later.
>>
>>Other thoughts if the update fails when you try at a later date:
>>If this is not the case then check in the Event Viewer to see if there is any specific errors
>>regarding services
>>Start/Run/Eventvwr.msc
>>
>>
>>Posted by: Mila -
>><snip> In my case it was wups.dll in
>>C:\WINDOWS\system32\SoftwareDistribution\Setup\S erviceStartup\wups.dll\5.8.0.2469 folder. After
>>removing this file, windowsupdate works great.
>>Mila <snip>
>>
>>Some additional information on this error from Torgeir, Microsoft MVP
>>
>><snip>
>>
>>Hi,
>>
>>If the things in TaurArian's post didn't apply or work, it is most likely a COM+ issue.
>>
>>First, verify that the "COM+ Event System" service is not disabled or not functioning:
>>
>>Press Start and Run, and then run this command:
>>services.msc
>>
>>Locate the "COM+ Event System" entry, and double click on it. Startup type should be set to
>>"Manual", and if the service is not already running, press the Start button to see if it starts
>>successfully.
>>
>>If the steps above where ok, see if the steps in this previous post fixes the problem (applies to
>>WinXP as well):
>>
>>From: DBQ <DBQ@discussions.microsoft.com>
>>Subject: Re: 0x8007041D W2K Server Try All
>>Date: Fri, 23 Sep 2005 14:30:03 -0700
>>Message-ID: <B7B2BCF2-44EB-46AA-95B1-00A42DCB35E1@microsoft.com>
>>Newsgroups: microsoft.public.windowsupdate
>>
>><quote>
>>We with a little help from MS It is fixed.
>>
>>Two issued needed repairing.
>>
>>1. COM+,
>>This required cleaning up a damaged COM+ catalog details at:
>>http://support.microsoft.com/?id=315296
>>
>>2. Replacement of the HKEY_LOCAL_MACHINE\Software\Microsoft
>>\Windows NT\CurrentVersion\Svchost for another working machine.
>>
>></quote>
>>
>>--
>>torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
>><snip>
>