Error 126 Specified Module Could Not Be Found Event Viewer
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 10:39:40 GMT by s_ac15 (squid/3.5.20)
Gaming Smartphones Tablets Windows 8 PSUs Android Your question Get the answer Tom's Hardware>Forum>Windows XP>Event log service will not start - error 126> Closed Event log service will not start - error 126 Tags: Configuration Computers Windows XP Last response: 23 November 2011 error 126 the specified module could not be found windows xp 18:49 in Windows XP Share mctoshiba 22 October 2009 20:27:14 Hi All, I'm having a windows could not start the trustedinstaller service error 2 problem with my wireless networking on XP which i've narrowed down to a probable specific issue with something called the "event Log
Error 126 Itunes
Service". From browsing forums I think fixing this issue will fix my problem - either way it's an error message that sounds not nice! Under Computer Management - Services - The Event Log is set to Automatic, but http://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/task-scheduler-error-1717-event-log-error-126/f9b98257-501f-4aec-bd65-6a5c7b517011 is not running. I try to start it, it gives the following error: "Could not start the Event Log Service on Local Computer. Error 126: The specified module cannot be found". A similar error occurs with something called "Task Scheduler" in the same place - except this time the second part is "Error 1717: The interface is unknown". Does anyone have any ideas re how to reinstall these components or otherwise fix this computer? I do http://www.tomshardware.com/forum/241770-45-event-service-start-error not want to have to reinstall windows etc. Have tried finding an existing solution online but nothing works. More about : event log service start error 126 mctoshiba 24 October 2009 18:41:43 Sorry to be a pain but still hunting down a solution can anyone please help?????? mctoshiba 25 October 2009 09:06:23 Hi All, Wasn't getting any help from here unfortunately, but kept searching online and found an answer that worked and was quite simple. Thought i'd post it here incase anyone else with a similar problem comes across this thread. Basically as it turns out the file eventlog.dll had been quarantined by my virus scanner - not sure why but it had. I downloaded a new copy from here: http://www.driverskit.com/dll/eventlog.dll/769.html Then copied it into the C:\windows\system32\ folder. Someone on a site I found mentioned it would need to be "registered" but in my case I didn't need it. I then went into the Computer Management console (right click on My Computer, select Manage, Services & Applications, then Services. Found Event Service, right clicked and selected Start. It started this time. I then sorted by the Startup Type filed and right clicked to start every one that said it was Automatic but wasn't running. All now started except two (mostly unrelated issue i believe). Restarted the computer, and volia, all working again including my wi
List Welcome Guide More BleepingComputer.com → Microsoft Windows Support → Windows XP Home and Professional Javascript Disabled Detected You currently have javascript disabled. Several functions may not http://www.bleepingcomputer.com/forums/t/244891/terminal-services-wont-start-event-7023/ work. Please re-enable javascript to access full functionality. Register a free account to unlock additional features at BleepingComputer.com Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, could not but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Click here to Register a free account now! or read our Welcome Guide to learn how to use this site. specified module could Terminal Services Won't Start - Event 7023 Started by mattpeg , Jul 27 2009 02:38 PM Please log in to reply 3 replies to this topic #1 mattpeg mattpeg Members 2 posts OFFLINE Local time:02:17 AM Posted 27 July 2009 - 02:38 PM Alright. Here's what's going on:Fast User Switching Compatibility service won't start because it depends on the Terminal Services service. The terminal service will not start either. I am suspecting that these errors are also what is halting the explorer. The system regularly produces the following errors in the event viewer:Event Type: ErrorEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7023Date: 7/27/2009Time: 11:35:01 AMUser: N/AComputer: EEP_01Description:The Terminal Services service terminated with the following error:The specified module could not be found.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Event Type: ErrorEvent Source: Service Control ManagerEvent Category: NoneEvent ID: 7001Date: 7/27/2009Time: 10:55:00 AMUser: N/AComputer: EEP_01Description:The Fast User Switching Compatibility service depends on the Terminal Services service which failed to start because of the following error:The specified module could not be found.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/