Share via

Event ID 43: Work Manager error can't startup work scheduler, Error code -1072167891

  • Article
  • 10/08/2009

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Cause

This behavior occurs because Microsoft Jet database engine transactions can use a significant amount of memory on a large database (a database that is larger than 80 megabytes [MB] in size). If a transaction hangs (runs for a long time before committing) or performs many modifications, Jet might consume the available version store.

Solution

In Windows Server 2003, you can use a new registry key to tune the default memory resources that are necessary for version store in Jet transactions. The version store maintains list of changes that are made to the database since the latest transaction began.

To tune the memory resources that are necessary for version store in Jet

  1. On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.

  2. Locate, and then click, the following key in the registry:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermServLicensing\Parameters

  3. 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

    The valid range for Value is 256 to 2048

  4. Caution

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.