Remote Desktop Licensing Service may not start and event ID 623 may be logged
This article provides a solution to an issue where Remote Desktop Licensing Service fails to start with event ID 623.
Applies to: Windows Server 2012 R2
Original KB number: 3167312
Symptoms
Consider the following scenario:
- You have a Windows Server 2012 R2 with the Remote Desktop Licensing role installed.
- You restart your Windows Server 2012 R2 or restart the Remote Desktop Licensing Service.
In this scenario, the Remote Desktop Service may fail to start and event ID 623 similar to the below may be logged:
Name: Application Name: Application
Source: ESENT
Event ID: 623
Task Category: Transaction Manager
Level: Error
Keywords: Classic
User: N/A
Computer: COMPUTERNAME
Description:
svchost (PID) The version store for this instance (0) has reached its maximum size of 2 Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been committed or rolled back.
Cause
This issue may occur if there is a large internal table in the Remote Desktop Licensing Service (RDLS) database.
Resolution
Warning
If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Start Registry Editor (Regedt32.exe).
Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermServLicensing\Parameters
On the Edit menu, click Add Value, and then add the following registry value:
- Value name: MaxVerPages
- Data type: REG_DWORD
- Radix: Decimal
- Value data: 1024
Range is from minimum 256 to maximum 2048.
Quit Registry Editor.
Data collection
If you need assistance from Microsoft support, we recommend you collect the information by following the steps mentioned in Gather information by using TSS for User Experience issues.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for