T.Svcs stuck "Starting"

  • Thread starter Thread starter Bob Bell
  • Start date Start date
B

Bob Bell

Hello. I am co-oping at a company with a W2K domain
controller that has Terminal Services terminally
at "Starting". I can RDC to all the servers but the
Active Directory Server. Everything I have read says this
should be no problem for up to 2 sessions. We are not in
Application mode. I cannot find anything on the net about
this issue, although I may not be looking in the right
places.
Can anyone give any suggestions? I have reloaded
Terminal Services and rebooted the server. Checked all
the settings, and everything looks fine. TS is still
listed in the Services screen as "Starting" and never
kicks in.
Thanks, Bob
 
Thanks for the reply Vera.

The Event Log has 3 events that might be applicable to
this issue.
Event ID 41 occured when we restarted the server on
10/12. WMI ADAP was unable to create object index 7734
for Performance library Term Service because no value was
found in the 009 subkey.
Event ID 61 occured due to a time violation in the
open function. Would make sense because ther service
never starts...
Finally ID 47 WMI ADAP unable to retrieve data from
the Perflib subkey: SYSTEM\Current Cotrol
Set\Services\Term Service\Perfromance\Library. Error code
0x80041009.

I hope that helps. Even though all of the settings
in Term Services were correct, I still followed the
suggestions in the Event ID 52 bulletin that you directed
me to. I disabled and re-enabled the service and waited.
I deleted and recreated the RDP connection and waited. I
checked the Registry and it has the correct value of 2,
to start the service, etc. These suggestions did not work!

Thank You,
Bob
-----Original Message-----
Anything in the EventLog on the server?
Check the applicable troubleshooting steps here:

258021 - Event ID 52 When You Start Terminal Services
http://support.microsoft.com/?kbid=258021

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email -- -

"Bob Bell" <[email protected]> wrote
Click to expand...
Hello. I am co-oping at a company with a W2K domain
controller that has Terminal Services terminally
at "Starting". I can RDC to all the servers but the
Active Directory Server. Everything I have read says this
should be no problem for up to 2 sessions. We are not in
Application mode. I cannot find anything on the net about
this issue, although I may not be looking in the right
places.
Can anyone give any suggestions? I have reloaded
Terminal Services and rebooted the server. Checked all
the settings, and everything looks fine. TS is still
listed in the Services screen as "Starting" and never
kicks in.
Thanks, Bob
Click to expand...
.
[/QUOTE]
 
Mmmm, strange.
I don't have a fool-proof solution, but I guess what I would do
is:

1. uninstall TS once more
2. reboot
3. manually clean the registry from all trace of TS. I'm sure
there are quite some left after uninstallation.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService
is listed here:
http://www.eventid.net/display.asp?eventid=47&eventno=665
&source=WinMgmt&phase=1

4. reboot again
5. check the eventlog. It should not show any errors now.
6. install TS in Remote app mode again.
7. hold your breath :-)

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Thanks for the reply Vera.

The Event Log has 3 events that might be applicable to
this issue.
Event ID 41 occured when we restarted the server on
10/12. WMI ADAP was unable to create object index 7734
for Performance library Term Service because no value was
found in the 009 subkey.
Event ID 61 occured due to a time violation in the
open function. Would make sense because ther service
never starts...
Finally ID 47 WMI ADAP unable to retrieve data from
the Perflib subkey: SYSTEM\Current Cotrol
Set\Services\Term Service\Perfromance\Library. Error code
0x80041009.

I hope that helps. Even though all of the settings
in Term Services were correct, I still followed the
suggestions in the Event ID 52 bulletin that you directed
me to. I disabled and re-enabled the service and waited.
I deleted and recreated the RDP connection and waited. I
checked the Registry and it has the correct value of 2,
to start the service, etc. These suggestions did not work!

Thank You,
Bob
Click to expand...
[/QUOTE]
 
Thanks for the suggestions.
I will have to wait for the weekend to try them.
I'll re-post the results.
-Bob
 
Hi Vera.

Saturday I uninstalled Terminal Services and rebooted, then cleaned the
registry entries for TS. I made the newbie error of not making a registry
backup, although everything but TS is still working fine. The problem is that
after reinstalling TS and rebooting, not only does the service not start, but
it no longer even shows up in Services! There isn't an error or event
associated with TS when rebooting, which I did several times. TS also no
longer shows up in the registry at HKEY_LOCAL_MACHINE\ System\
CurrentControlSet\ Services\ TermService, although it does show in a couple
of Legacy Services registry keys. After 3 reboots I decided to use Add/Remove
to remove and reinstall it again, to no effect.

Besides any additional ideas, could you possibly post a correct Terminal
Services Registry Key for me? I'm not sure if that would help, but the key
only had a few entries to start with.

I appreciate the effort you are taking to help me.

One note that I just learned in talking to my supervisor, that he hadn't
informed me of previously, is that the server contains a mirror copy of
another server, acting as a failover server. (We have 4 total servers, as I
stated previously I can use Terminal Services to connect to the others with
no problems, including the mirrored server). I'm not sure whether this would
affect Terminal Services on this machine, but the Active Directory functions
work normally and this is the server we do all Active Directory/DNS work on.

-Bob
 
No sure if I can help you with the registry keys, Bob, we run NT
4.0 and 2003 Terminal Servers, no W2K. I'll have a look tomorrow
at the office and compare them.
Can't you get them from the other servers that you can connect to?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Yeah, I thought about that after I posted--duh. That also would have been a
good place for me to compare registry keys before deleting. Learning every
day . . .

thanks, Bob
 
Back
Top