Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 44 Source: TermServLicensing
General database error occurred, Can't initialize ESE instance - '<error>" -'<error message>'
|English: Request a translation of the event description in plain English.|
- Error: -1023 = JET_errInvalidPath - I fixed this problem by creating a Lserver folder in Windows's System32 folder. In Windows Server 2003, the path would by default be "C:\Windows\System32\Lserver". Also, encountered a corresponding event ID 7024, from Service Control Manager: "The Terminal Server Licensing service terminated with service-specific error 31 (0x1F).". This was fixed once the above was done.
- Error: -1811 = JET_errFileNotFound - As per Microsoft: "Incorrectly configured NTFS permissions for logical drives can cause problems with system services and programs. This issue can occur if an administrator modifies permissions in an attempt to strengthen the default Windows 2000 security, but does not set the proper permissions at all levels". See ME273566 and ME302427 for details.
It it possible that the terminal services licensing on server has not been activated. Terminal services licensing will only issue temporary licenses until the server is activated.
Error -514 JET_errBadLogVersion, Version of log file is not compatible with Jet version. - After I have deleted log files actually ebd.log files from these locations \winnt\security with \winnt\ntfs\jet and \winnt\lserver everything came to normal. This message come together with Service Control Manager 7024 "The Terminal Services Licensing service terminated with service-specific error 31.
Woodrow Wayne Collins
Check the Microsoft Terminal Server Licensing link for more information.
Computer Business Consultants Inc
Check the Application Event Log for ESENT errors. This will usually lead to the cause of the error. The most likely cause is the License server log file is either removed or corrupt. The default install Directory is C:\WINNT\System32\LServer\LServer\edb.log.
Most common error in Application Event Log for ESENT is: lserver (3704) The database engine could not access the file called C:\WINNT\System32\LServer\LServer\edb.log.
Error 1032: "JET_errFileAccessDenied, Cannot access file, the file is locked or in use." System Account needs full control to root drive before TermServicesLicensing starts.
Error: "-530 JET_errBadLogSignature" Symptom: Terminal Services Licensing Service won''t stop/start/restart and/or is utilizing an abnormally large amount of memory.
Cause: LSERVER.EXE won''t start due to corrupt database and/or log files.
1 - If the service is hung or started, kill the process ID
2 - Rename X:\WINNT\SYSTEM32\LSERVER to X:\WINNT\SYSTEM32\LSERVER-OLD
3 - Create an empty X:\WINNT\SYSTEM32\LSERVER folder
4 - Start the Terminal Services Licensing Service
Apparently, this happens with MS Exchange Server Directory too - see the link below.
|Private comment: Subscribers only. See example of private comment|
|Links: Error code 1811, JET_errBadLogSignature, Microsoft Terminal Server Licensing, Event ID 7024 from source Service Control Manager|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated