When you install a custom application, Windows Installer tries to repair SQL Server 2000 Desktop Engine (889289)


The information in this article applies to:

  • Microsoft SQL Server 2000 Desktop Engine (MSDE)
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

When you install a custom application, or when you uninstall a custom application, a problem occurs. The Microsoft Windows Installer service that is named Msiexec.exe tries to repair Microsoft SQL Server 2000 Desktop Engine. SQL Server 2000 Desktop Engine is also known as MSDE 2000. This problem only occurs if the custom application uses Msiexec.exe and tries to load the Active Template Library that is named Atl.dll.

Note This problem does not occur in non-desktop engine versions of Microsoft SQL Server 2000.

CAUSE

This problem occurs after SQL Server 2000 Desktop Engine is installed. The installation process creates a hook in the Atl.dll registry key that indicates that a resiliency check must occur the next time that an application tries to load Atl.dll. Therefore, when you install your custom application, the SQL Server 2000 Desktop Engine repair is started. This problem occurs when the installation process tries to load Atl.dll.

WORKAROUND

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 work around this problem, you can use one of the following methods:
  • Method 1

    This method requires that you remove the following registry data after you install SQL Server 2000 Desktop Engine:

    HKEY_CLASSES_ROOT\CLSID\{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InprocServer32\InprocServer32

    To do this, follow these steps:
    1. Click Start, click Run, type regedit, and then click OK.
    2. Locate the following registry key:

      HKEY_CLASSES_ROOT\CLSID\{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InprocServer32
    3. Click the registry key in step 2.
    4. On the Edit menu, click Delete.
    5. When you receive a message that prompts you to confirm the key deletion, click Yes.
    6. On the File menu, click Exit.
  • Method 2

    This method requires that you un-register and then re-register the Atl.dll file after you install SQL Server 2000 Desktop Engine.

    To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. Type the following line at the command prompt:

      regsvr32 /u Atl.dll
    3. Press ENTER to un-register the file.
    4. Type the following line at the command prompt:

      regsvr32 Atl.dll
    5. Press ENTER to register the file.
    6. Type exit, and then press ENTER.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

823519 Windows Installer starts in Repair mode when you try to remove an instance of SQL Server 2000 on a computer that has an instance of SQL Server Desktop Engine or SQL Server Desktop Engine (Windows)

Modification Type:MinorLast Reviewed:6/6/2005
Keywords:kbATL kbuninstall kbRegistry kbtshoot kbprb KB889289 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.