FIX: MDAC Installation Fails with Error 0x80070057 When Registry is at Size Limit (326842)



The information in this article applies to:

  • Microsoft Data Access Components 2.7, when used with:
    • the operating system: Microsoft Windows NT 4.0
    • the operating system: Microsoft Windows 2000
  • Microsoft Data Access Components 2.6, when used with:
    • the operating system: Microsoft Windows NT 4.0
    • the operating system: Microsoft Windows 2000

This article was previously published under Q326842

SYMPTOMS

When you install Microsoft Data Access Components (MDAC) versions 2.6 or 2.7 on a computer that is running Windows NT 4.0 or Windows 2000, you may receive the following error message:
0x80070057 "The parameter is incorrect."
The Dasetup.log shows that there are a few missing parameters for the ExecuteInstall() function.

CAUSE

The registry is at its size limit. During installation, a number of registry keys are created in the following folder:

HKLM\Software\Microsoft\dasetup

Some of these resistry keys contain a lot of data. If the registry is at its size limit, these large data entries are not written. You receive the errror message that is described in the "Symptoms" section, however, you should receive an error message from the MDAC installer that states that it cannot write to the registry.

RESOLUTION

To receive the correct error message from the installer, install MDAC 2.7 SP1. To download MDAC 2.7 SP1, visit the following Microsoft Web site: To resolve the size limit problem, increase the maximum registry size in Windows NT 4.0 and Windows 2000. To do this, follow these steps:
  1. In Control Panel, double-click System.
  2. Click the Advanced tab, and then click Performance Options.
  3. Under Virtual memory, click Change.
  4. In the Virtual Memory dialog box, change the registry size.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in MDAC 2.7 SP1.

Modification Type:MajorLast Reviewed:4/6/2004
Keywords:kbBug kbfix KB326842 kbAudDeveloper