In this article, we will see solution for “Windows could not start the Terminal Services Licensing on Local Computer”.
“Windows could not start the Terminal Services Licensing on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 31”
Noticed following event ids in the eventviewer.
Event id :44 Log Name: System Source: Microsoft-Windows-TerminalServices-Licensing Date: 2/9/2016 1:29:18 PM Event ID: 44 Task Category: None Level: Error Keywords: Classic User: N/A Computer: WPSERVER.Wedding.local Description: The description for Event ID 44 from source Microsoft-Windows-TerminalServices-Licensing cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event: Can't initialize ESE instance - error -1023 JET_errInvalidPath, Invalid file path
Resolution:
—————–
–Check the lserver folder permissions. Network Service,TermServLicensing and Administrator has full permissions.
–Take the backup of lserver folder( %WINDIR%\system32\Lserver)
–Rename the Lserver folder.
–Create the new Lserver folder.
–Add the lserver folder permissions. Network Service has full permissions.
–Start the Remote Desktop licensing service.