Event ID - 44

Event Id44
SourceTermServLicensing
DescriptionGeneral database error occurred, Cant initialize ESE instance - <error>" -<error message>
Event InformationThe following information from a newsgroup post will be helpful to understand this event:


1) Error : 530 JET_errBadLogSignature and you can observe that Terminal service licensing service completely hang up and you will unable to anything with service and it will consume more memory. This problem caused by LSERVER.EXE didnt started due to corrupted database or log files. Resolution steps as follows.
a) kill the service force fully.
b) Rename the directory sysroot%winnt\system32\lserver to sysroot%winnt\system32\lserver-back
c
) Create an empty folder sysroot%winnt\system32\lserver
d) Start the Service.
2) If  Terminal services licensing on server is not activated, this event may generated. Terminal services licensing will issue only temporary license until the server activated.
3) Error -514 JET_errBadLogVersion. Version of log file is not compatible with Jet version. One reported solution for this problem is as follows. Delete the log files "edb.log" from \winnt\security with \winnt\ntfs\jet and \winnt\lserver. In this situation you may also observe an event id 7024 from service control manager.
4) The cause of this event you may able to find from ESENT event in application log (lserver, event: 3704," The database engine could not access the file called C:\WINNT\System32\LServer\LServer\edb.log").. In most cases its observed  that the corruption or deletion of License server log file would be the cause of this error (Sysroot%\WINNT\System32\LServer\LServer\edb.log).
5) Error 1032: "JET_errFileAccessDenied. This error may due to lack of SYSTEM accounts permission to root drive. Give "Full Control" permission  to this account to root drive may solve this problem.
Reference LinksThe Terminal Services Licensing Service Does Not Start

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.