Nobody likes red errors in the event log. They have a habit of worrying one
:-) So in a new build, we noticed the following error:

DCOM got error "The service cannot be started, either because it is disabled
or because it has no enabled devices associated with it. " attempting to
start the service SENS with arguments "" in order to run the server:
{D3938AB0-5B9D-11D1-8DD2-00AA004ABD5E}

Doing a search on Usenet, it appears that this error is due to the SENS
service been disabled - and it is indeed disabled. The posts suggest that it
was SCW that disabled it and this is probably the case.

The question is two fold - is there anyway to prevent this event in the log
from worrying us each time we look and secondly, why has SCW decided to
disable it? What is the risk of SENS been enabled?

That's the problem with SCW - I know it's trying to help but sometimes it
really confuses :-)

Thanks, Rob.

> The question is two fold - is there anyway to prevent this event in the
> log from worrying us each time we look and secondly, why has SCW decided
> to disable it? What is the risk of SENS been enabled?

Actually, it's three fold - what's the corresponding configuration entry in
SCW that is disabling the System Event Notification service? I've had a look
through and can't see any obvious SCW setting.

Cheers, Rob.

> Actually, it's three fold - what's the corresponding configuration entry
> in SCW that is disabling the System Event Notification service? I've had a
> look through and can't see any obvious SCW setting.

Manually setting the service to automatic gets rid of the event log but of
course, next time we run the SCW, it'll disable it again :-)

Cheers, Rob.