Terminal Server Licensing Failed



On friday I had a crash of our PDC. Our Progress database engine had
actually stopped and I needed to reboot the server to restart it.
After rebooting the server I had the following errors listed below.
The server is a fully patched Windows 2000 Server Service Pack 4 Dell
Server.

The Terminal Services Licensing service terminated with
service-specific error 3221291009.

Can't start Terminal Services Licensing because of error 'Can't
initialize Cryptographic - error code 80090016.

Can't generate new public/private keys because of error 'Can't acquire
Crypt Context, error 80090016.

So now Terminal Services Licencing will not start. I have found the
Cryptography key listed in prior posts and removed all below it. I
have uninstalled TS and reinstalled it several times. Nothing works.
I even reinstalled Service Pack 4.

Any ideas?

'.

.



Relevant Pages

  • Re: Time zone redirection
    ... Administration and full-blown Terminal Services. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... client connections:-O. ... Well - obviously that does not work in Remote Desktop Admin mode ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP suddenly stops
    ... reboot the server once more. ... Services service doesn't work when the server is rebooted from ... recreate the rdp listener, in Terminal Services Configuration. ...
    (microsoft.public.windows.terminal_services)
  • Re: Restarting Windows 2003 server via terminal server connection
    ... otherwise it will reboot your local computer :-). ... Terminal Services Program Manager ... This issue started for me after I had been using the Remote Desktops MMC ... Servers reboots ok and the terminal server connection is fine. ...
    (microsoft.public.windows.terminal_services)
  • Re: Restarting Windows 2003 server via terminal server connection
    ... But occasionally this also fails so you have to reboot the server ... locally or in our case via the remote insight board. ... Servers reboots ok and the terminal server connection is fine. ... Your Terminal Services Security Website ...
    (microsoft.public.windows.terminal_services)
  • RE: Terminal Services
    ... I understand that you want to have staff log ... we cannot make SBS to work as terminal server. ... why you cannot find Terminal Services in Add/Remove Windows Components. ...
    (microsoft.public.windows.server.sbs)

Loading