SEN service won't start

[Guest]

I have 35 PCs that won't start System Event Notification service, all get
"Error 1083: The executable program that this service is configured to run in
does not implement the service."

910337 is the only KB article I can find, and it addresses BITS, not SENS.
(BITS won't start either, because it depends on SENS, but SENS is the root
problem here.)

I've re-reg'd a bunch of dlls, no no avail.

Anyone encounter this before?

 

[Guest]

Hi AG,

Ensure that sens.dll is in the System32 folder. Open the registry editor.
Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SENS\Parameters
In the right-hand pane, ensure that the Value data for ServiceDll points to
the location of the sens.dll file (i.e., %SystemRoot%\system32\sens.dll)
Now, navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost
In the right-hand pane, locate and double-click on netsvc
In the Value data field, scroll down and ensure that SENS is listed
somewhere in the listing of services. If not, manually add it, click on OK
and then close the Registry editor.

Restart the computer. Check the Services to see if System Event Notification
has been started, if Startup type was set to Automatic. If not, see if you
can now Start the service successfully.



Regards,

 

[Guest]

Thanks for the quick reply, Patti. In the Value field for netsvcs is
"EventSystem." Is that it, or should I add "SENS?"

 

[Guest]

You're welcome for the quick reply

No, EventSystem refers to the COM+ Event System in the Services console. Add
SENS to the Value data field.



Regards,

 

[Guest]

It looks like that might do it! (One of my bench PCs happens to be one
having the problem. It is now installing WUs, which is what clued me into
the problem here.) I've applied your suggestion to two production PCs, and
will let you know after I can reboot them.

Incidentally, EventSystem was the only entry in the netsvcs key. Is that
unusual? I'm wondering where this problem originated...?

 

[Guest]

Great! I hope it works for all the PCs

Your entries in the Value data field in the netsvcs key does seem kind of
slim.....mine contains these entries (currently on a standalone laptop
running XP Home):

6to4
AppMgmt
AudioSrv
Browser
CryptSvc
DMServer
DHCP
ERSvc
EventSystem
FastUserSwitchingCompatibility
HidServ
Ias
Iprip
Irmon
LanmanServer
LanmanWorkstation
Messenger
Netman
Nla
Ntmssvc
NWCWorkstation
Nwsapagent
Rasauto
Rasman
Remoteaccess
Schedule
Seclogon
SENS
Sharedaccess
SRService
Tapisrv
Themes
TrkWks
W32Time
WZCSVC
Wmi
WmdmPmSp
winmgmt
TermService
wuauserv
BITS
ShellHWDetection
helpsvc
WmdmPmSN
xmlprov
wscsvc

Researching values in the registry, following the information in this MSKB
article....
A description of Svchost.exe in Windows XP Pro
http://support.microsoft.com/kb/314056/EN-US/
....I find that all the services listed under
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
whose Parameters key contains a ServiceDLL value (eg., AppMgmt has a
Parameters key with a ServiceDLL value of %SystemRoot%\System32\appmgmts.dll)
appear in the ValueData field for the netsvcs key at
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Svchost



Regards,

 

[Guest]

Patti,

The other two PCs are resolved. Thanks for your quick and exactly correct
solution! Now I'm off to 33 other registries...

 

[Guest]

You're welcome, and that's good to hear!!

I hope the 33 other registries fare as well as the first three



Regards,

 

[Guest]

Would that it were so...

Most are now working, but there are some still not starting SENS. I copied
the contents of a working device's netsvc (below) to all the 35 previously,
and it did the trick for most. What do you suggest I look at next?

EventSystem
Ias
Iprip
Irmon
Netman
Nwsapagent
Rasauto
Rasman
Remoteaccess
SENS
Sharedaccess
Tapisrv
Ntmssvc
wzcsvc

 

[Guest]

Do they return the same error message (i.e., "Error 1083: The executable
program....")?



Regards,

 

[Guest]

yes, everything is the same.

 

[Guest]

Unfortunately, I haven't come up with anything to try next.......I tried
experimenting with numerous possibilities to see if they returned the same
error message when trying to start SENS and none of the things that I tried
returned the same error.
If I do come up with a possible solution, I'll be sure to post it for
you.....if you find something in the meantime, please post back and let me
know.

I'm sorry that I wasn't able to help you get all your rigs back in order :-(



Regards,