If you have a regular backup on tape, you could try to reinstall
from there. Check the item under "How to move a licensing server"
in the Microsofts Terminal Services FAQ at
http://www.microsoft.com/windowsserv.../centers/termi
nal/terminal_faq.asp
If you don't have a recent tape backup, your only choice is to
reinstall the LS. The Clearinghouse will need the same information
that you provided when you first activated the LS (organisation
name, possibly also licensing information for the server / TS
CALs).
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---
"Paul" <(E-Mail Removed)> wrote in news:064501c39d98
$d9f640d0$(E-Mail Removed):
> I'm not sure how I can restore from the backup. In the %
> windir%\system32\lserver directory there are two files:
>
> edb.log
> TLSLic.edb
>
> The 'TLSlic.edb' is 1Mb. The 'edb.log' file is 5.1Mb but
> is completly blank in notepad, which kind of worries me.
>
> If I have to re-install my LS, what information will
> Microsoft need?
>
> Any other things I could try?
>
> Thanks so much for your responce!
>
> Paul
>
>>-----Original Message-----
>>It sounds as if your licensing database has been
> corrupted. Can
>>you restore from the backup in the %windir%\system32
> \lserver
>>directory?
>>You could also try to reinstall the latest SP, which just
> *might*
>>help if it is only a version mismatch.
>>
>>If none of this helps, you might have to uninstall and
> reinstall
>>the LS, but that also means phoning the Clearinghouse to
> get your
>>licenses re-issued.
>>
>> --
>>Vera Noest
>>MCSE, CCEA, Microsoft MVP - Terminal Server
>>http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup ---
>>
>>"Paul" <(E-Mail Removed)> wrote in news:0e5e01c39d68
>>$4c798da0$(E-Mail Removed):
>>
>>> 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
Similar Threads
