Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Terminal Services Won't Start - Event 7023


  • Please log in to reply

#1
mattpeg

mattpeg

    New Member

  • Member
  • Pip
  • 1 posts
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: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 7/27/2009
Time: 11:35:01 AM
User: N/A
Computer: EEP_01
Description:
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....link/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/27/2009
Time: 10:55:00 AM
User: N/A
Computer: EEP_01
Description:
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....link/events.asp.


"The specified module could not be found." is sort of an ambiguous diagnosis. I've researched and attempted the following fixes:

  • I had an Ethernet card that was not operational because I couldn't find the correct drivers. I located and installed the drivers and it is now working properly in the device manager.
  • I turned on the Windows Firewall due to some related issues in SP2 where services would fail after disabling this service. I am currently using sp3 but I figure it couldn't hurt.
  • I have run sfc /scannow in the command prompt.
  • I have updated the registry entry via http://www.kellys-ko...m/xp_tweaks.htm. tip # 163
  • I have replaced termsrv.dll in C:\WINDOWS\system32 and C:\WINDOWS\system32\dllcache
  • Ran Combofix.exe

None of these fixes have repaired the problem. Any ideas?

Thanks,

Mattpeg
  • 0

Advertisements







Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP