|
|
Hi, I have 12 PCs, XP and 2K, getting this error. I've tried solutions in
910337, but the PCs in question all fail to start System Event Notification
Service with
"Error 1083: The executable program that this service is configured to run in
does not implement the service. (0x8007043B)."
The listed regsvr32 commands did not solve the problem, as well as regsvr32
wuapi.dll, wups.dll, wuaueng.dll, wuaueng1.dll, wuweb.dll, jscript.dll,
wucltui.dll, msxml3.dll, softpub.dll, atl.dll.
A manual attempt at Windows Update has the same result. Virus scan reports
no trojans.
Thanks
|
|
"AG" <AG[ at ]discussions.microsoft.com> wrote in message
news:BF95B074-A1C7-4A15-823A-80C626BEC996[ at ]microsoft.com...
[Quoted Text] > Hi, I have 12 PCs, XP and 2K, getting this error. I've tried solutions in
> 910337, but the PCs in question all fail to start System Event
> Notification
> Service with
> "Error 1083: The executable program that this service is configured to run
> in
> does not implement the service. (0x8007043B)."
This is an OS configuration issue, possibly caused by a policy configuration
issue, and really has nothing at all to do with Windows Server Update
Services, unless the specific issue is that the Background Intelligent
Transfer Service is not properly starting, which may or may not be directly
a result of any failure in the System Event Notification Service.
A quick check of my system shows that there are no direct dependencies
between BITS and SENS; however, both services are dependent on RPC, and SENS
is also dependent on the COM+ Event System, which in turn is also dependent
on RPC.
I'd start by verifying that the RPC subsystems on these machines are
configured correctly.
> The listed regsvr32 commands did not solve the problem, as well as
> regsvr32
> wuapi.dll, wups.dll, wuaueng.dll, wuaueng1.dll, wuweb.dll, jscript.dll,
> wucltui.dll, msxml3.dll, softpub.dll, atl.dll.
That's because these DLLs have absolutely nothing to do with the [System
Event Notification Service].
> A manual attempt at Windows Update has the same result. Virus scan
> reports
> no trojans.
You'll want to fix the [System Event Notification Service], [Background
Intelligent Transfer Service], [COM+ Event System], and/or the [Remote
Procedure Call] services.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|