asked on

Eventlog service failed NT Server

I have an NT Server (4.0+SP3) which, on startup, says a service failed to start. When I try to check the eventlog, it says the eventlog service is not running. When I try to start the eventlog service manually, it says the eventlog file cannot be found and fails to start the eventlog service. The error code is Error 1501.

Anyone know how to cure the problem and get the eventlog service started?

gikam

U probably don't have these files:
appevent.evt
secevent.evt
sysevent.evt
in the \winnt\system32\config directory
if u don't, try creting them manually with 0 length

theh95

PSS ID Number: Q111720
Article last modified on 05-14-1997

3.1

WINDOWS

======================================================================
----------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
----------------------------------------------------------------------

SYMPTOMS
========

When you start Event Viewer, the following error appears:

The Eventlog service on the local machine is not started.

Then, after you start the Eventlog service from the Services section of
Control Panel the following error message appears:

Could not start the Eventlog service on \\<machine name>.
Error 1501: No event log file could be opened,
so the event logging service did not start.

CAUSE
=====

This error only occurs when the Windows NT system drive is formatted for
NTFS. When the Eventlog Service starts, it opens three log files in the
%SYSTEMROOT%\SYSTEM32\CONFIG directory. If the system does not have the
correct permissions, it cannot open and write the log files.

RESOLUTION
==========

For these files to be opened successfully, Read and Write permission in
this directory must be granted to the Administrators group, the System
account, or the Everyone group. Any one of these three enables the system
to function normally.

Additional query words: prodnt
======================================================================
Keywords : kbtool ntutil
Version : 3.1
Platform : WINDOWS
=============================================================================
Copyright Microsoft Corporation 1997.

argo

ASKER

This was odd!
Renaming the files didn't cure it.
Copying on a set of files from another server didn't cure it.
Deleting the files and rebooting cured it.

Since your (gikam) mention of the filenames was the clue I needed, resubmit your comment as an answer and I will accept it
Thanks

gikam

argo thanks, but first u have to reject theh95's answer

argo

ASKER

Sorry, your answer appears to be correct, but someone helped me cure the problem before I saw it.

ASKER CERTIFIED SOLUTION

gikam

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial