The Windows Event Log Service manages a series of event logs that use the system, system components, and applications to log events. The service provides functions that allow programs to maintain and manage event logs and perform log operations, such as archiving and reconciliation. This allows administrators to keep event logs and perform administrative tasks that require administrative rights.
For some unknown reason, if you have difficulty starting the following, it is quite possible that one of the reasons why the Windows Event Log service does not work.
- Task Scheduler
- Windows Event Calendar
- Mail Sharing Folder
In such a scenario, error messages such as :
Event log service is not available. Check if the service is runningOnly admnistrator owned posts can execute the include me shortcode
Windows could not start the Windows event log service on the local computer
Restart your system first and see if it helps. Sometimes a simple restart helps to reset this service. If the Windows event log appears to have started, restart it from the Service Manager.
To check whether the Windows Event Log service is started or stopped, start services.msc and press Enter to open the Service Manager. Right-click Windows Event Log Service and check its properties.
Make sure the boot type is set to Automatic and the services Started; and that it is running in the Local Service account.
Also make sure that on the Restore tab the three drop-down boxes display the option’Restart service’ if an error occurs. Restart if necessary.
Sometimes the Windows event log service still doesn’t start and you get the following error message:
The system cannot find the specified file
In this case, open the following folder:
This folder contains event logs in .evtx format and can only be read with the Event Viewer. Give this log folder read/write access and see if it helps.
You can also do the following.
Open the registry editor and navigate to the next key:
Double-click ObjectName and make sure its value is NT AUTHORITYLocalService. If not, change it.
If this still does not help, run the system file checker and browse the logs.
Only admnistrator owned posts can execute the include me shortcode