Anyone seen THESE errors?

[Paul]

Hi all,
Here is my problem:

We have Windows 2000 Server with 6 terminal licenses and 4
computers logging into it. I installed the new windows SP
and Windows updates on the weekend. Everything worked
perfect on Monday, but on Tuesday I believe one of our
client machines got their terminal license corrupt. It
has not been able to log on since. (It gives the
message "The Terminal Server Ended the Connection")

I remove the MSlicensing key from the client's registry.
It should be refreshed when the client logs on to the
server again. The key appeared again, but I was still not
able to log onto the server.

I checked the server's 'event viewer' and it says, "The
terminal server cannot issue a client license." So now I
look at the services that are running and noticed that
the 'Terminal Services Licensing" was not running. Bingo!
I thought.

I opened up its properties and tried to start
the 'Terminal Services Licensing" but now get and errors
saying windows can not start the service and to check the
event log. Checking the event log it has two errors:

EventID: 44
General database error occurred, Can't initialize ESE
instance - error -514 JET_errBadLogVersion, Version of log
file is not compatible with Jet version.
...
AND

The Terminal Services licensing service terminated with
service-specific error 31.


Now I'm stumped. What do these errors mean? Is it
related to the SP and updates I did? Most importantly,
How do I fix it???


Thanks in advance!

Paul

 

[David Bullock [MSFT]]

Hi Paul,
Please post this question to microsoft.public.windows.terminal_services.

--

David Bullock, MCSE, MCSA, A+
Windows NT/2000/2003 Setup Support

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.