Article ID: 308305
Article Last Modified on 1/31/2007
APPLIES TO
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
This article was previously published under Q308305
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
The Terminal Server Licensing service may not start, and the Event log may contain an Event ID:43 with the following description:
The Debug log may contain the following error:
CAUSE
On a large database (larger than 80 megabytes), Jet transactions can take up more memory. The version store keeps a list of changes that are made to the database since the oldest transaction began. Having a transaction "hang" (run for a long time before it commits) or make a lot of modifications in one transaction, can cause Jet to run out of version store.
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.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Edit the registry to tune the memory resource that is needed for version store in Jet. To do so, start Registry Editor (Regedt32.exe), and then locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermServLicensing\Parameters.
Add the following registry value to this key:
Value name: MaxVerPages
Data type: REG_DWORD
Radix: Decimal
Value data: 1,024
Range is from a minimum of 256 to a maximum of 2,048.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
----------------------------------------------------------
28-Aug-2001 14:36 5.0.2195.3895 125,712 Icaapi.dll
19-Jul-2001 16:39 5.0.2195.3895 93,456 Licmgr.exe
28-Aug-2001 14:30 5.0.2195.4435 330,000 Lserver.exe
28-Aug-2001 14:36 5.0.2195.3895 26,384 Mstlsapi.dll
28-Aug-2001 14:36 5.0.2195.4307 100,112 Rdpwsx.dll
19-Jul-2001 16:39 5.0.2195.3895 141,584 Termsrv.exe
28-Aug-2001 14:36 5.0.2195.3895 23,312 Tls236.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.
MORE INFORMATION
A new registry key was added to tune the default memory resource that is needed for version store in Jet.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
Additional query words: kbTermServ
Keywords: kberrmsg kbbug kbfix kbwin2000presp3fix kbqfe kbwin2000sp3fix kbenv kbtermserv kbhotfixserver KB308305
