Remote Desktop Licensing service crashing

Sean Kirk 11 Reputation points
2021-10-18T17:47:35.55+00:00

We have two Windows 2016 Servers, each running separate Remote Desktop Licensing servers. For about two weeks now, the RDS Licensing service on both servers will crash at the same time, and give the same error message.

Faulting application name: svchost.exe_TermServLicensing, version: 10.0.14393.0, time stamp: 0x57899b1c
Faulting module name: lserver.dll, version: 10.0.14393.4169, time stamp: 0x5ff78dd6
Exception code: 0xc0000005
Fault offset: 0x000000000002cb8d
Faulting process id: 0x136c
Faulting application start time: 0x01d7c43bea43e49f
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\lserver.dll
Report Id: 7d8889ac-49ae-4829-bfd4-78ba80f4fa27
Faulting package full name:
Faulting package-relative application ID:

When I say they crash at the same time, I mean I have compared the Application Event Logs on both servers, and they both report the same error at the same date/time.

These servers were initially setup to service two separate RDS environments, but for past 2+ years both been added as a secondary Licensing server to each environment.

I have ran SFC on both and on one server Rebuilt the license server database, but it continues to crash along side the other one.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
Windows for business | Windows Server | User experience | Other
{count} votes

3 answers

Sort by: Most helpful
  1. Sean Kirk 11 Reputation points
    2022-03-07T20:23:19.493+00:00

    Version Mismatch between Terminal server version and CAL version.

    The Licensing Server was Server 2016. When I stood up a new RDS Session Host on Server 2019, it caused an issue with the 2016 Licensing Server, which would crash the Licensing Service.

    Server 2019 is not Backwards compatible with 2016 CALs, and a 2016 Licensing Server won't accept 2019 CALs. The Solution was to stand up a new Licensing Server on Server 2019 with 2019 CALs.

    The 2019 CALs are backwards compatible with 2016 Terminal/RDS Servers, so it resolved the version mismatch with the 2019 Servers and supports the existing 2016 Servers.

    2 people found this answer helpful.
    0 comments No comments

  2. Sean Kirk 1 Reputation point
    2021-12-13T17:25:32.31+00:00

    Still have not been able to resolve the issue, but as a work around I changed the settings in the service to restart if it crashes. The services still crash, but they restart fast enough to not cause outages.

    0 comments No comments

  3. Jorge Daniel Propp Bordas 1 Reputation point
    2022-03-07T18:24:39.967+00:00

    Hi Any updates? This exact issue is happening to us as well.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.