Article ID: 310122 - Last Review: March 1, 2007 - Revision: 3.3 Terminal Services Licensing Service May Not Start and Event ID 43 May Be LoggedThis article was previously published under Q310122 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
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SYMPTOMS The Terminal Services Licensing service may not start on
large databases and event ID 43 may be logged with the following description:
Work Manager error Can't Startup work scheduler, Error
code -1072167891 CAUSE This behavior occurs because the Microsoft Jet database
engine transactions can use a lot of memory on a large database (a database
that is larger than 80 megabytes [MB] in size). Having a transaction hang (run
for a long time before committing) or perform many modifications can cause Jet
to consume the available version store.
MORE INFORMATIONWARNING: 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. A new registry key is included in Windows Server 2003 to tune the default memory resources that are necessary for version store in Jet transactions. The version store keeps a list of changes that are made to the database since the latest transaction began. To tune memory resource that is necessary for version store in Jet:
| Article Translations
|
Back to the top
