While to trying shedule a task in task sheduler I was informed a needed service was not running (Event log). Upon trying to start needed service (Event log) I received the following error message. {Could not start Event log service on Local Computer, Error 126 Specific module can not be found.} I have been online searching for solution with no real luck, would appreciate any and all assistance in solving this problem.1 person needs an answerI do too

While to trying shedule a task in task sheduler I was informed a needed service was not running (Event log). Upon trying to start needed service (Event log) I received the following error message. {Could not start Event log service on Local Computer, Error 126 Specific module can not be found.} I have been online searching for solution with no real luck, would appreciate any and all assistance in solving this problem. ==========================================Maybe the following articles will offer some ideas: (308588) How to troubleshoot scheduled tasks in Windows XP and in Windows Server 2003 http://support.microsoft.com/kb/308558 (915156) Error message when you try to start the Task Scheduler service in Windows XP: "Error 1717: The interface is unknown" http://support.microsoft.com/kb/915156 John Inzer - MS-MVP - Digital Media Experience - Notice_This is not tech support_I am a volunteer - Solutions that work for me may not work for you - Proceed at your own risk

It is I, George. I have solved my problem with a little help from Microsoft. The solution is simple for those of you with the same problem. Instead of searching the web and Microsoft's website, I simply clicked on my "Help and Support" icon on my desktop and entered the same query. This time I got an answer that actually addressed my problem even though it warned that it might apply to XP. It was for Windows2000, but I tried it anyway and it worked. The cause of the problem is a missing DLL file in Windows\system32 directory, a file named "eventlog.dll". It is still on your computer in a different directory, so all you have to do is a seach under the drive you have Windows installed on for that file and copy it to Windows\system32 directory and everything should be just fine. It is as simple as that.I hope this helps everybody who may be going through____ trying to correct what I have been trying to correct for the past three days. Good luck and may the force be with you.

Thanks John for reply. I do appreciate the time you took to address my issue, though it did not work, I a m truly thankful that you tried. Thanks again, hopefully I won't be needing help anytime soonGeorge

Thanks John for reply. I do appreciate the time you took to address my issue, though it did not work, I a m truly thankful that you tried. Thanks again, hopefully I won't be needing help anytime soonGeorge =================================Self help is always the most rewarding.Way-To-Go!Thanks for the update.John Inzer - MS-MVP - Digital Media Experience - Notice_This is not tech support_I am a volunteer - Solutions that work for me may not work for you - Proceed at your own risk

George - not sure if you will ever check back on this thread but THANK YOU very much for reporting back your solution. It resolved the same issue for me!!!Many thanks and take care.Mike

I had the same problem did a search for eventlog.dll copied the dll to system32 directory started the eventlog service and after forever had an event logs I could read thanx George I am disapointed no one from Microsoft figured this out sooner.