The Terminal Services service failed to start

[Guest Daniel]

W2K3S - SP2. Terminal Services have never worked on this server yet. After

removing, rebooting, and reinstalling Terminal Services for Admin access

only, I get the following System Event ID: 7000 - "The Terminal Services

service failed to start due to the following error: The system cannot find

the file specified. "

 

When starting the Terminal Services Configuration snap-in I recieve the

following message: MMC could not create the snap-in.

 

 

This is not an AD controller. I have no problems on other W2K3 servers.

 

I searched around and didn't find anything relevant - yet.

[Guest jolteroli]

Re: The Terminal Services service failed to start

 

termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all the files

there?

 

-jolt

[Guest Daniel]

Re: The Terminal Services service failed to start

 

Those 5 are in the %windir%\system32\drivers folder... any other files to

consider?

 

"jolteroli" wrote:

> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all the files

> there?

>

> -jolt

>

>

[Guest jolteroli]

Re: The Terminal Services service failed to start

 

termsrv.dll is not a kernel mode driver, so it isn't in /drivers! checked?

seriously?

 

any import of termsrv.dll exising?

WS2HELP.dll

WS2_32.dll

NETAPI32.dll

ICAAPI.dll

mstlsapi.dll

MSASN1.dll

CRYPT32.dll

ATL.DLL

credui.dll

AUTHZ.dll

adsldpc.dll

ACTIVEDS.dll

WLDAP32.dll

Secur32.dll

C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

ole32.dll

REGAPI.dll

msvcrt.dll

GDI32.dll

RPCRT4.dll

OLEAUT32.dll

USER32.DLL

SHLWAPI.dll

ADVAPI32.dll

kernel32.dll

ntdll.dll

SHELL32.dll

 

registry values ok?

 

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

%SystemRoot%\System32\termsrv.dll

 

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

system32\DRIVERS\termdd.sys

 

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

system32\DRIVERS\rdpdr.sys

 

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

system32\DRIVERS\rdpcdd.sys

 

-jolt

 

"Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

> Those 5 are in the %windir%\system32\drivers folder... any other files to

> consider?

>

> "jolteroli" wrote:

>

>> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all the

>> files

>> there?

>>

>> -jolt

>>

>>

[Guest Daniel]

Re: The Terminal Services service failed to start

 

All files in place as you listed, but the registry entries are not.

 

 

"jolteroli" wrote:

> termsrv.dll is not a kernel mode driver, so it isn't in /drivers! checked?

> seriously?

>

> any import of termsrv.dll exising?

> WS2HELP.dll

> WS2_32.dll

> NETAPI32.dll

> ICAAPI.dll

> mstlsapi.dll

> MSASN1.dll

> CRYPT32.dll

> ATL.DLL

> credui.dll

> AUTHZ.dll

> adsldpc.dll

> ACTIVEDS.dll

> WLDAP32.dll

> Secur32.dll

> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

> ole32.dll

> REGAPI.dll

> msvcrt.dll

> GDI32.dll

> RPCRT4.dll

> OLEAUT32.dll

> USER32.DLL

> SHLWAPI.dll

> ADVAPI32.dll

> kernel32.dll

> ntdll.dll

> SHELL32.dll

>

> registry values ok?

>

> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

> %SystemRoot%\System32\termsrv.dll

>

> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

> system32\DRIVERS\termdd.sys

>

> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

> system32\DRIVERS\rdpdr.sys

>

> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

> system32\DRIVERS\rdpcdd.sys

>

> -jolt

>

> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

> news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

> > Those 5 are in the %windir%\system32\drivers folder... any other files to

> > consider?

> >

> > "jolteroli" wrote:

> >

> >> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all the

> >> files

> >> there?

> >>

> >> -jolt

> >>

> >>

>

>

[Guest Jeff Pitsch]

Re: The Terminal Services service failed to start

 

Something bothers me about what you said which is "After removeing rebooting

and reinstalling TS for admin access"....this is wrong. This is not what

you do for admin access. Admin access for a Win2k3 server is setup from

control panel/system/remote.

 

My guess is you need to rebuild this box because something is very wrong

with it.

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"Daniel" <Daniel@discussions.microsoft.com> wrote in message

news:D977A444-E9FE-409D-A2CE-A1FEC6B1845A@microsoft.com...

> W2K3S - SP2. Terminal Services have never worked on this server yet. After

> removing, rebooting, and reinstalling Terminal Services for Admin access

> only, I get the following System Event ID: 7000 - "The Terminal Services

> service failed to start due to the following error: The system cannot find

> the file specified. "

>

> When starting the Terminal Services Configuration snap-in I recieve the

> following message: MMC could not create the snap-in.

>

>

> This is not an AD controller. I have no problems on other W2K3 servers.

>

> I searched around and didn't find anything relevant - yet.

[Guest jolteroli]

Re: The Terminal Services service failed to start

 

what do u mean by "the registry entries are not"? the "ImagePath" is

missing? the whole service key is missing? u have no CurrentControlSet at

all? ur response is somewhat flimsy! *yawn* :)

 

either u export the missing entries from another vital server and import

them or u setup the server again and from scratch. i'd recommend the

latter...

 

-jolt

 

 

"Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

news:E6F0953F-7782-4FF9-A7D3-885C85574B73@microsoft.com...

> All files in place as you listed, but the registry entries are not.

>

>

> "jolteroli" wrote:

>

>> termsrv.dll is not a kernel mode driver, so it isn't in /drivers!

>> checked?

>> seriously?

>>

>> any import of termsrv.dll exising?

>> WS2HELP.dll

>> WS2_32.dll

>> NETAPI32.dll

>> ICAAPI.dll

>> mstlsapi.dll

>> MSASN1.dll

>> CRYPT32.dll

>> ATL.DLL

>> credui.dll

>> AUTHZ.dll

>> adsldpc.dll

>> ACTIVEDS.dll

>> WLDAP32.dll

>> Secur32.dll

>> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

>> ole32.dll

>> REGAPI.dll

>> msvcrt.dll

>> GDI32.dll

>> RPCRT4.dll

>> OLEAUT32.dll

>> USER32.DLL

>> SHLWAPI.dll

>> ADVAPI32.dll

>> kernel32.dll

>> ntdll.dll

>> SHELL32.dll

>>

>> registry values ok?

>>

>> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

>> %SystemRoot%\System32\termsrv.dll

>>

>> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

>> system32\DRIVERS\termdd.sys

>>

>> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

>> system32\DRIVERS\rdpdr.sys

>>

>> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

>> system32\DRIVERS\rdpcdd.sys

>>

>> -jolt

>>

>> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

>> news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

>> > Those 5 are in the %windir%\system32\drivers folder... any other files

>> > to

>> > consider?

>> >

>> > "jolteroli" wrote:

>> >

>> >> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all the

>> >> files

>> >> there?

>> >>

>> >> -jolt

>> >>

>> >>

>>

>>

[Guest Daniel]

Re: The Terminal Services service failed to start

 

There is no "Remote" tab in the System Properties - either under a local

administrator login or a Domain Admin login...

 

All that's there are "General", "Computer Name" "Hardware", "Advanced", and

"Automatic Updates".

 

"Jeff Pitsch" wrote:

> Something bothers me about what you said which is "After removeing rebooting

> and reinstalling TS for admin access"....this is wrong. This is not what

> you do for admin access. Admin access for a Win2k3 server is setup from

> control panel/system/remote.

>

> My guess is you need to rebuild this box because something is very wrong

> with it.

>

> --

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "Daniel" <Daniel@discussions.microsoft.com> wrote in message

> news:D977A444-E9FE-409D-A2CE-A1FEC6B1845A@microsoft.com...

> > W2K3S - SP2. Terminal Services have never worked on this server yet. After

> > removing, rebooting, and reinstalling Terminal Services for Admin access

> > only, I get the following System Event ID: 7000 - "The Terminal Services

> > service failed to start due to the following error: The system cannot find

> > the file specified. "

> >

> > When starting the Terminal Services Configuration snap-in I recieve the

> > following message: MMC could not create the snap-in.

> >

> >

> > This is not an AD controller. I have no problems on other W2K3 servers.

> >

> > I searched around and didn't find anything relevant - yet.

>

>

>

[Guest Daniel]

Re: The Terminal Services service failed to start

 

No rdprd key.

No rdpcdd key.

No "TermService/Parameters/ServiceDll=%SystemRoot%\System32\termsrv.dll"

value.

No "TermDD/ImagePath=system32\DRIVERS\termdd.sys" value.

The following files that you specified are in the System32 folder:

WS2HELP.dll

WS2_32.dll

NETAPI32.dll

ICAAPI.dll

mstlsapi.dll

MSASN1.dll

CRYPT32.dll

ATL.DLL

credui.dll

AUTHZ.dll

adsldpc.dll

ACTIVEDS.dll

WLDAP32.dll

Secur32.dll

ole32.dll

REGAPI.dll

msvcrt.dll

GDI32.dll

RPCRT4.dll

OLEAUT32.dll

USER32.DLL

SHLWAPI.dll

ADVAPI32.dll

kernel32.dll

ntdll.dll

SHELL32.dll

 

Comctl.dll appears in all

"C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????"

folders.

 

Setup from scratch is not an option.

 

 

"jolteroli" wrote:

> what do u mean by "the registry entries are not"? the "ImagePath" is

> missing? the whole service key is missing? u have no CurrentControlSet at

> all? ur response is somewhat flimsy! *yawn* :)

>

> either u export the missing entries from another vital server and import

> them or u setup the server again and from scratch. i'd recommend the

> latter...

>

> -jolt

>

>

> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

> news:E6F0953F-7782-4FF9-A7D3-885C85574B73@microsoft.com...

> > All files in place as you listed, but the registry entries are not.

> >

> >

> > "jolteroli" wrote:

> >

> >> termsrv.dll is not a kernel mode driver, so it isn't in /drivers!

> >> checked?

> >> seriously?

> >>

> >> any import of termsrv.dll exising?

> >> WS2HELP.dll

> >> WS2_32.dll

> >> NETAPI32.dll

> >> ICAAPI.dll

> >> mstlsapi.dll

> >> MSASN1.dll

> >> CRYPT32.dll

> >> ATL.DLL

> >> credui.dll

> >> AUTHZ.dll

> >> adsldpc.dll

> >> ACTIVEDS.dll

> >> WLDAP32.dll

> >> Secur32.dll

> >> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

> >> ole32.dll

> >> REGAPI.dll

> >> msvcrt.dll

> >> GDI32.dll

> >> RPCRT4.dll

> >> OLEAUT32.dll

> >> USER32.DLL

> >> SHLWAPI.dll

> >> ADVAPI32.dll

> >> kernel32.dll

> >> ntdll.dll

> >> SHELL32.dll

> >>

> >> registry values ok?

> >>

> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

> >> %SystemRoot%\System32\termsrv.dll

> >>

> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

> >> system32\DRIVERS\termdd.sys

> >>

> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

> >> system32\DRIVERS\rdpdr.sys

> >>

> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

> >> system32\DRIVERS\rdpcdd.sys

> >>

> >> -jolt

> >>

> >> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

> >> news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

> >> > Those 5 are in the %windir%\system32\drivers folder... any other files

> >> > to

> >> > consider?

> >> >

> >> > "jolteroli" wrote:

> >> >

> >> >> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all the

> >> >> files

> >> >> there?

> >> >>

> >> >> -jolt

> >> >>

> >> >>

> >>

> >>

>

>

[Guest jolteroli]

Re: The Terminal Services service failed to start

 

ok daniel, as I mentioned, you can reimport the keys from a vital W2K3

server. but, I would worry about the installation process at all. if the

terminal service related keys are missing, what is missing/corrupted else?

 

to not to run into more and more problems in due to a currupted installation

medium or server hardware, i'd suggest to completely setitup again from

scratch. fixing the registry is an option for a few entries. and again i

wouldn't put this server into a production environment. it is very likely

that you run into more and more problems...

 

-jolt

 

"Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

news:504B2282-1475-4160-B709-B035DE40AF0E@microsoft.com...

> No rdprd key.

> No rdpcdd key.

> No "TermService/Parameters/ServiceDll=%SystemRoot%\System32\termsrv.dll"

> value.

> No "TermDD/ImagePath=system32\DRIVERS\termdd.sys" value.

> The following files that you specified are in the System32 folder:

> WS2HELP.dll

> WS2_32.dll

> NETAPI32.dll

> ICAAPI.dll

> mstlsapi.dll

> MSASN1.dll

> CRYPT32.dll

> ATL.DLL

> credui.dll

> AUTHZ.dll

> adsldpc.dll

> ACTIVEDS.dll

> WLDAP32.dll

> Secur32.dll

> ole32.dll

> REGAPI.dll

> msvcrt.dll

> GDI32.dll

> RPCRT4.dll

> OLEAUT32.dll

> USER32.DLL

> SHLWAPI.dll

> ADVAPI32.dll

> kernel32.dll

> ntdll.dll

> SHELL32.dll

>

> Comctl.dll appears in all

> "C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????"

> folders.

>

> Setup from scratch is not an option.

>

>

> "jolteroli" wrote:

>

>> what do u mean by "the registry entries are not"? the "ImagePath" is

>> missing? the whole service key is missing? u have no CurrentControlSet at

>> all? ur response is somewhat flimsy! *yawn* :)

>>

>> either u export the missing entries from another vital server and import

>> them or u setup the server again and from scratch. i'd recommend the

>> latter...

>>

>> -jolt

>>

>>

>> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

>> news:E6F0953F-7782-4FF9-A7D3-885C85574B73@microsoft.com...

>> > All files in place as you listed, but the registry entries are not.

>> >

>> >

>> > "jolteroli" wrote:

>> >

>> >> termsrv.dll is not a kernel mode driver, so it isn't in /drivers!

>> >> checked?

>> >> seriously?

>> >>

>> >> any import of termsrv.dll exising?

>> >> WS2HELP.dll

>> >> WS2_32.dll

>> >> NETAPI32.dll

>> >> ICAAPI.dll

>> >> mstlsapi.dll

>> >> MSASN1.dll

>> >> CRYPT32.dll

>> >> ATL.DLL

>> >> credui.dll

>> >> AUTHZ.dll

>> >> adsldpc.dll

>> >> ACTIVEDS.dll

>> >> WLDAP32.dll

>> >> Secur32.dll

>> >> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

>> >> ole32.dll

>> >> REGAPI.dll

>> >> msvcrt.dll

>> >> GDI32.dll

>> >> RPCRT4.dll

>> >> OLEAUT32.dll

>> >> USER32.DLL

>> >> SHLWAPI.dll

>> >> ADVAPI32.dll

>> >> kernel32.dll

>> >> ntdll.dll

>> >> SHELL32.dll

>> >>

>> >> registry values ok?

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

>> >> %SystemRoot%\System32\termsrv.dll

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

>> >> system32\DRIVERS\termdd.sys

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

>> >> system32\DRIVERS\rdpdr.sys

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

>> >> system32\DRIVERS\rdpcdd.sys

>> >>

>> >> -jolt

>> >>

>> >> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

>> >> news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

>> >> > Those 5 are in the %windir%\system32\drivers folder... any other

>> >> > files

>> >> > to

>> >> > consider?

>> >> >

>> >> > "jolteroli" wrote:

>> >> >

>> >> >> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all

>> >> >> the

>> >> >> files

>> >> >> there?

>> >> >>

>> >> >> -jolt

>> >> >>

>> >> >>

>> >>

>> >>

>>

>>

[Guest jolteroli]

Re: The Terminal Services service failed to start

 

ok daniel, as I mentioned, you can reimport the keys from a vital W2K3

server. but, I would worry about the installation process at all. if the

terminal service related keys are missing, what is missing/corrupted else?

 

to not to run into more and more problems in due to a currupted installation

medium or server hardware, i'd suggest to completely setitup again from

scratch. fixing the registry is an option for a few entries. and again i

wouldn't put this server into a production environment. it is very likely

that things go more odd.

 

are there server editions out without the terminal service? sbs? wrong cd

grabbed?

 

-jolt

 

 

"Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

news:504B2282-1475-4160-B709-B035DE40AF0E@microsoft.com...

> No rdprd key.

> No rdpcdd key.

> No "TermService/Parameters/ServiceDll=%SystemRoot%\System32\termsrv.dll"

> value.

> No "TermDD/ImagePath=system32\DRIVERS\termdd.sys" value.

> The following files that you specified are in the System32 folder:

> WS2HELP.dll

> WS2_32.dll

> NETAPI32.dll

> ICAAPI.dll

> mstlsapi.dll

> MSASN1.dll

> CRYPT32.dll

> ATL.DLL

> credui.dll

> AUTHZ.dll

> adsldpc.dll

> ACTIVEDS.dll

> WLDAP32.dll

> Secur32.dll

> ole32.dll

> REGAPI.dll

> msvcrt.dll

> GDI32.dll

> RPCRT4.dll

> OLEAUT32.dll

> USER32.DLL

> SHLWAPI.dll

> ADVAPI32.dll

> kernel32.dll

> ntdll.dll

> SHELL32.dll

>

> Comctl.dll appears in all

> "C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????"

> folders.

>

> Setup from scratch is not an option.

>

>

> "jolteroli" wrote:

>

>> what do u mean by "the registry entries are not"? the "ImagePath" is

>> missing? the whole service key is missing? u have no CurrentControlSet at

>> all? ur response is somewhat flimsy! *yawn* :)

>>

>> either u export the missing entries from another vital server and import

>> them or u setup the server again and from scratch. i'd recommend the

>> latter...

>>

>> -jolt

>>

>>

>> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

>> news:E6F0953F-7782-4FF9-A7D3-885C85574B73@microsoft.com...

>> > All files in place as you listed, but the registry entries are not.

>> >

>> >

>> > "jolteroli" wrote:

>> >

>> >> termsrv.dll is not a kernel mode driver, so it isn't in /drivers!

>> >> checked?

>> >> seriously?

>> >>

>> >> any import of termsrv.dll exising?

>> >> WS2HELP.dll

>> >> WS2_32.dll

>> >> NETAPI32.dll

>> >> ICAAPI.dll

>> >> mstlsapi.dll

>> >> MSASN1.dll

>> >> CRYPT32.dll

>> >> ATL.DLL

>> >> credui.dll

>> >> AUTHZ.dll

>> >> adsldpc.dll

>> >> ACTIVEDS.dll

>> >> WLDAP32.dll

>> >> Secur32.dll

>> >> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

>> >> ole32.dll

>> >> REGAPI.dll

>> >> msvcrt.dll

>> >> GDI32.dll

>> >> RPCRT4.dll

>> >> OLEAUT32.dll

>> >> USER32.DLL

>> >> SHLWAPI.dll

>> >> ADVAPI32.dll

>> >> kernel32.dll

>> >> ntdll.dll

>> >> SHELL32.dll

>> >>

>> >> registry values ok?

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

>> >> %SystemRoot%\System32\termsrv.dll

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

>> >> system32\DRIVERS\termdd.sys

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

>> >> system32\DRIVERS\rdpdr.sys

>> >>

>> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

>> >> system32\DRIVERS\rdpcdd.sys

>> >>

>> >> -jolt

>> >>

>> >> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

>> >> news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

>> >> > Those 5 are in the %windir%\system32\drivers folder... any other

>> >> > files

>> >> > to

>> >> > consider?

>> >> >

>> >> > "jolteroli" wrote:

>> >> >

>> >> >> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all

>> >> >> the

>> >> >> files

>> >> >> there?

>> >> >>

>> >> >> -jolt

>> >> >>

>> >> >>

>> >>

>> >>

>>

>>

[Guest Daniel]

Re: The Terminal Services service failed to start

 

It's a server that is accessed 24/7 and is not easily restorable, so

reinstallation of the OS is a last resort. I've exported your referenced

registry keys from another server and imported them with no change, however,

I haven't yet restarted the server...

 

"jolteroli" wrote:

> ok daniel, as I mentioned, you can reimport the keys from a vital W2K3

> server. but, I would worry about the installation process at all. if the

> terminal service related keys are missing, what is missing/corrupted else?

>

> to not to run into more and more problems in due to a currupted installation

> medium or server hardware, i'd suggest to completely setitup again from

> scratch. fixing the registry is an option for a few entries. and again i

> wouldn't put this server into a production environment. it is very likely

> that things go more odd.

>

> are there server editions out without the terminal service? sbs? wrong cd

> grabbed?

>

> -jolt

>

>

> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

> news:504B2282-1475-4160-B709-B035DE40AF0E@microsoft.com...

> > No rdprd key.

> > No rdpcdd key.

> > No "TermService/Parameters/ServiceDll=%SystemRoot%\System32\termsrv.dll"

> > value.

> > No "TermDD/ImagePath=system32\DRIVERS\termdd.sys" value.

> > The following files that you specified are in the System32 folder:

> > WS2HELP.dll

> > WS2_32.dll

> > NETAPI32.dll

> > ICAAPI.dll

> > mstlsapi.dll

> > MSASN1.dll

> > CRYPT32.dll

> > ATL.DLL

> > credui.dll

> > AUTHZ.dll

> > adsldpc.dll

> > ACTIVEDS.dll

> > WLDAP32.dll

> > Secur32.dll

> > ole32.dll

> > REGAPI.dll

> > msvcrt.dll

> > GDI32.dll

> > RPCRT4.dll

> > OLEAUT32.dll

> > USER32.DLL

> > SHLWAPI.dll

> > ADVAPI32.dll

> > kernel32.dll

> > ntdll.dll

> > SHELL32.dll

> >

> > Comctl.dll appears in all

> > "C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????"

> > folders.

> >

> > Setup from scratch is not an option.

> >

> >

> > "jolteroli" wrote:

> >

> >> what do u mean by "the registry entries are not"? the "ImagePath" is

> >> missing? the whole service key is missing? u have no CurrentControlSet at

> >> all? ur response is somewhat flimsy! *yawn* :)

> >>

> >> either u export the missing entries from another vital server and import

> >> them or u setup the server again and from scratch. i'd recommend the

> >> latter...

> >>

> >> -jolt

> >>

> >>

> >> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

> >> news:E6F0953F-7782-4FF9-A7D3-885C85574B73@microsoft.com...

> >> > All files in place as you listed, but the registry entries are not.

> >> >

> >> >

> >> > "jolteroli" wrote:

> >> >

> >> >> termsrv.dll is not a kernel mode driver, so it isn't in /drivers!

> >> >> checked?

> >> >> seriously?

> >> >>

> >> >> any import of termsrv.dll exising?

> >> >> WS2HELP.dll

> >> >> WS2_32.dll

> >> >> NETAPI32.dll

> >> >> ICAAPI.dll

> >> >> mstlsapi.dll

> >> >> MSASN1.dll

> >> >> CRYPT32.dll

> >> >> ATL.DLL

> >> >> credui.dll

> >> >> AUTHZ.dll

> >> >> adsldpc.dll

> >> >> ACTIVEDS.dll

> >> >> WLDAP32.dll

> >> >> Secur32.dll

> >> >> C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_???????????????????\comctl32.dll

> >> >> ole32.dll

> >> >> REGAPI.dll

> >> >> msvcrt.dll

> >> >> GDI32.dll

> >> >> RPCRT4.dll

> >> >> OLEAUT32.dll

> >> >> USER32.DLL

> >> >> SHLWAPI.dll

> >> >> ADVAPI32.dll

> >> >> kernel32.dll

> >> >> ntdll.dll

> >> >> SHELL32.dll

> >> >>

> >> >> registry values ok?

> >> >>

> >> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermService/Parameters/ServiceDll=

> >> >> %SystemRoot%\System32\termsrv.dll

> >> >>

> >> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TermDD/ImagePath=

> >> >> system32\DRIVERS\termdd.sys

> >> >>

> >> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/rdprd/ImagePath=

> >> >> system32\DRIVERS\rdpdr.sys

> >> >>

> >> >> HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/RDPCDD/ImagePath=

> >> >> system32\DRIVERS\rdpcdd.sys

> >> >>

> >> >> -jolt

> >> >>

> >> >> "Daniel" <Daniel@discussions.microsoft.com> schrieb im Newsbeitrag

> >> >> news:B2BB5FFA-4C99-48C0-920E-3795D2A1F7A3@microsoft.com...

> >> >> > Those 5 are in the %windir%\system32\drivers folder... any other

> >> >> > files

> >> >> > to

> >> >> > consider?

> >> >> >

> >> >> > "jolteroli" wrote:

> >> >> >

> >> >> >> termsrv.dll, rdpwd.sys, rdpdr.sys, termdd.sys, tdtcp.sys ... all

> >> >> >> the

> >> >> >> files

> >> >> >> there?

> >> >> >>

> >> >> >> -jolt

> >> >> >>

> >> >> >>

> >> >>

> >> >>

> >>

> >>

>

>

[Guest Jeff Pitsch]

Re: The Terminal Services service failed to start

 

And this is windows 2003 we're talking about? Are you sure it's not Windows

2000?

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"Daniel" <Daniel@discussions.microsoft.com> wrote in message

news:8291594D-DD58-4B23-A0F8-31EFFAB272B7@microsoft.com...

> There is no "Remote" tab in the System Properties - either under a local

> administrator login or a Domain Admin login...

>

> All that's there are "General", "Computer Name" "Hardware", "Advanced",

> and

> "Automatic Updates".

>

> "Jeff Pitsch" wrote:

>

>> Something bothers me about what you said which is "After removeing

>> rebooting

>> and reinstalling TS for admin access"....this is wrong. This is not what

>> you do for admin access. Admin access for a Win2k3 server is setup from

>> control panel/system/remote.

>>

>> My guess is you need to rebuild this box because something is very wrong

>> with it.

>>

>> --

>> Jeff Pitsch

>> Microsoft MVP - Terminal Services

>>

>> "Daniel" <Daniel@discussions.microsoft.com> wrote in message

>> news:D977A444-E9FE-409D-A2CE-A1FEC6B1845A@microsoft.com...

>> > W2K3S - SP2. Terminal Services have never worked on this server yet.

>> > After

>> > removing, rebooting, and reinstalling Terminal Services for Admin

>> > access

>> > only, I get the following System Event ID: 7000 - "The Terminal

>> > Services

>> > service failed to start due to the following error: The system cannot

>> > find

>> > the file specified. "

>> >

>> > When starting the Terminal Services Configuration snap-in I recieve the

>> > following message: MMC could not create the snap-in.

>> >

>> >

>> > This is not an AD controller. I have no problems on other W2K3 servers.

>> >

>> > I searched around and didn't find anything relevant - yet.

>>

>>

>>

[Guest Daniel]

Re: The Terminal Services service failed to start

 

It's 2003 Standard ("R1" - not R2). However, it was upgraded from 2000 Server.

 

"Jeff Pitsch" wrote:

> And this is windows 2003 we're talking about? Are you sure it's not Windows

> 2000?

>

> --

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "Daniel" <Daniel@discussions.microsoft.com> wrote in message

> news:8291594D-DD58-4B23-A0F8-31EFFAB272B7@microsoft.com...

> > There is no "Remote" tab in the System Properties - either under a local

> > administrator login or a Domain Admin login...

> >

> > All that's there are "General", "Computer Name" "Hardware", "Advanced",

> > and

> > "Automatic Updates".

> >

> > "Jeff Pitsch" wrote:

> >

> >> Something bothers me about what you said which is "After removeing

> >> rebooting

> >> and reinstalling TS for admin access"....this is wrong. This is not what

> >> you do for admin access. Admin access for a Win2k3 server is setup from

> >> control panel/system/remote.

> >>

> >> My guess is you need to rebuild this box because something is very wrong

> >> with it.

> >>

> >> --

> >> Jeff Pitsch

> >> Microsoft MVP - Terminal Services

> >>

> >> "Daniel" <Daniel@discussions.microsoft.com> wrote in message

> >> news:D977A444-E9FE-409D-A2CE-A1FEC6B1845A@microsoft.com...

> >> > W2K3S - SP2. Terminal Services have never worked on this server yet.

> >> > After

> >> > removing, rebooting, and reinstalling Terminal Services for Admin

> >> > access

> >> > only, I get the following System Event ID: 7000 - "The Terminal

> >> > Services

> >> > service failed to start due to the following error: The system cannot

> >> > find

> >> > the file specified. "

> >> >

> >> > When starting the Terminal Services Configuration snap-in I recieve the

> >> > following message: MMC could not create the snap-in.

> >> >

> >> >

> >> > This is not an AD controller. I have no problems on other W2K3 servers.

> >> >

> >> > I searched around and didn't find anything relevant - yet.

> >>

> >>

> >>

>

>

>

[Guest Jeff Pitsch]

Re: The Terminal Services service failed to start

 

I would seriously rebuild that box. Something is not right if your still

getting remote admin choices int he add/remove wizard.

 

--

Jeff Pitsch

Microsoft MVP - Terminal Services

 

"Daniel" <Daniel@discussions.microsoft.com> wrote in message

news:CD851F9C-4379-436D-88F3-80C12C0001D8@microsoft.com...

> It's 2003 Standard ("R1" - not R2). However, it was upgraded from 2000

> Server.

>

> "Jeff Pitsch" wrote:

>

>> And this is windows 2003 we're talking about? Are you sure it's not

>> Windows

>> 2000?

>>

>> --

>> Jeff Pitsch

>> Microsoft MVP - Terminal Services

>>

>> "Daniel" <Daniel@discussions.microsoft.com> wrote in message

>> news:8291594D-DD58-4B23-A0F8-31EFFAB272B7@microsoft.com...

>> > There is no "Remote" tab in the System Properties - either under a

>> > local

>> > administrator login or a Domain Admin login...

>> >

>> > All that's there are "General", "Computer Name" "Hardware", "Advanced",

>> > and

>> > "Automatic Updates".

>> >

>> > "Jeff Pitsch" wrote:

>> >

>> >> Something bothers me about what you said which is "After removeing

>> >> rebooting

>> >> and reinstalling TS for admin access"....this is wrong. This is not

>> >> what

>> >> you do for admin access. Admin access for a Win2k3 server is setup

>> >> from

>> >> control panel/system/remote.

>> >>

>> >> My guess is you need to rebuild this box because something is very

>> >> wrong

>> >> with it.

>> >>

>> >> --

>> >> Jeff Pitsch

>> >> Microsoft MVP - Terminal Services

>> >>

>> >> "Daniel" <Daniel@discussions.microsoft.com> wrote in message

>> >> news:D977A444-E9FE-409D-A2CE-A1FEC6B1845A@microsoft.com...

>> >> > W2K3S - SP2. Terminal Services have never worked on this server yet.

>> >> > After

>> >> > removing, rebooting, and reinstalling Terminal Services for Admin

>> >> > access

>> >> > only, I get the following System Event ID: 7000 - "The Terminal

>> >> > Services

>> >> > service failed to start due to the following error: The system

>> >> > cannot

>> >> > find

>> >> > the file specified. "

>> >> >

>> >> > When starting the Terminal Services Configuration snap-in I recieve

>> >> > the

>> >> > following message: MMC could not create the snap-in.

>> >> >

>> >> >

>> >> > This is not an AD controller. I have no problems on other W2K3

>> >> > servers.

>> >> >

>> >> > I searched around and didn't find anything relevant - yet.

>> >>

>> >>

>> >>

>>

>>

>>