Microsoft KB Archive/890096

= Information about the 32-bit hotfix installer tool in Microsoft Data Access Components 2.8 =

Article ID: 890096

Article Last Modified on 12/7/2004

-

APPLIES TO


 * Microsoft Data Access Components 2.8

-





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



SUMMARY
''This article describes the hotfix installer tool in Microsoft Data Access Components (MDAC) 2.8. The hotfix installer tool is used for installing hotfixes and security updates on a 32-bit operating system.''

CONTENTS

 * INTRODUCTION
 * Understand the hotfix installer executable file naming standard
 * Use the hotfix installer tool
 * View the list of files that are updated by the hotfix installer tool
 * Understand the permissions that are required by the hotfix installer tool
 * Understand how the hotfix installer tool works
 * Perform an unattended installation
 * Remove a hotfix installation
 * Understand the log files for the hotfix installer tool
 * View command line parameters for the hotfix installer tool
 * View command line syntax examples for the hotfix installer tool



INTRODUCTION
This article describes the hotfix installer tool that is used for installing MDAC 2.8 hotfixes on a 32-bit a operating system. The hotfix installer tool only runs on Microsoft Windows 2000 or later versions of the Microsoft Windows operating system. This article describes the following:
 * Functionality of the MDAC hotfix installer tool
 * Valid command line parameters
 * How to remove a hotfix

back to the top



Understand the hotfix installer executable file naming standard
A standardized naming schema is used for hotfix installer packages for MDAC. The name of the hotfix installer executable file includes the following information:
 * Product name
 * Microsoft Knowledge Base article number that describes the hotfix
 * Processor architecture that the hotfix is built for
 * Language that the hotfix is intended for

For example, a hotfix package that is named &quot;Mdac28-Kb887576-x86-Enu.exe&quot; denotes the following:
 * The hotfix package is designed to be applied to MDAC 2.8.
 * The hotfix package is described in Microsoft Knowledge Base article 887576.
 * The hotfix package is designed to run on a 32-bit x86 operating system.
 * The hotfix package is supposed to be applied to English systems.

back to the top

Use the hotfix installer tool
To start the hotfix installation process, you must log on to the computer with a user account that has local administrative credentials. Then, run the hotfix installation package. When you start the hotfix installation process, the Graphical User Interface-based (GUI-based) hotfix installer tool starts. The GUI-based hotfix installer tool guides you through the rest of the installation process. This article also describes other methods that you can use to start the GUI-based hotfix installer tool.

back to the top

View the list of files that are updated by the hotfix installer tool
The Microsoft Knowledge Base article that corresponds to the hotfix contains a list of the files that are updated by the hotfix. The Microsoft Knowledge Base article number is shown on the initial &quot;Welcome&quot; screen of the hotfix installer tool. The Microsoft Knowledge Base article number also appears in the hotfix installer package name.back to the top

Understand the permissions that are required by the hotfix installer tool
You must have administrative credentials to install a hotfix or to remove a hotfix. If the account that you use does not have administrative credentials, you may receive the following error message:

You do not have permission to update .

Please contact your system administrator.

back to the top

Understand how the hotfix installer tool works
When you run the hotfix installer tool, it performs the following operations:  Extracts files to a temporary folder

The hotfix installer tool extracts the files that are packaged in the self-extracting executable to the following temporary folder:

C:\

The file name of the temporary folder may be similar to the following:

C:\843cd3866db3890cb93fe431a1 Verifies the architecture of your computer

The hotfix installer tool verifies the architecture that your computer is built on. If the hotfix package is not intended for your architecture, you may receive the following error message.

Update.exe is not a valid Win32 application.

For example, on a computer with a 32-bit x86 architecture, you may receive a message that is similar to the previous error message. You may receive the previous error message when you try to install a hotfix package that is compiled to run on the 64-bit IA-64 architecture. Verifies the user account that you use to log on

The hotfix installer tool verifies that the user account that you use to log on to the computer has administrative credentials. Verifies the operating system

The hotfix installer tool verifies the operating system that is running on your computer. If the operating system does not qualify for the hotfix, you may receive an error message that is similar to the following:

The patch installer that you are running is meant for another operating system and is not supported on this operating system. To proceed, download the product patch for this operating system and retry the installation.

 Verifies the version of MDAC

The hotfix installer tool verifies that the hotfix that you are installing is supposed to be applied to the version of MDAC that is already installed on your system. If the hotfix installer tool detects an incompatible MDAC version, you receive the following error message:

The product version on the machine does not qualify for the hotfix.

Note: The Microsoft Knowledge Base article that describes the hotfix may contain more information about the requirements for applying this update, including any MDAC requirements.

</li> Checks for later hotfix versions

The hotfix installer tool verifies whether you have already installed a hotfix version that is later than the hotfix version that you are trying to install. If the hotfix installer tool detects that a later version is already installed, you receive the following error message:

Some of the files on the machine are already at a higher version than the one on the update. The installer cannot replace these files.

The message also contains a list of files that have the later version. For each file in the list, the version that you try to install is listed together with the version that is already on your computer.</li> Verifies whether the MDAC installation is consistent

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.

The hotfix installer tool examines approximately eight core MDAC files to verify whether they are from the same MDAC version. This verification lets the hotfix installer tool correct the version information in the registry. When the version information in the registry is set correctly before installing the files, the installation is successful. If the files are consistent with each other, but the version that is detected in the registry does not match the installed files, you are prompted to let the installer correct the registry. You receive the following error message:

The installer detected that some of the registry keys of the product are incorrect/corrupted.

Do you want the installer to repair the registry keys?

If you click &quot;Yes,&quot; the registry is updated with the correct version. The correct version is determined by the hotfix installer tool. The correct version is based on the files that the hotfix installer tool verified. The hotfix installation continues.

If you decide not to repair the registry, the installation is canceled. Additionally, the hotfix installer tool prevents the installation of the incorrect files for your version of MDAC.

Sometimes, the system may not have a consistent set of MDAC files because of previous problems. In this case, the hotfix installer tool cannot use the set of MDAC files to determine the correct version information for the registry. You may receive a message that states that an MDAC repair or an operating system repair is recommended. Additionally, the hotfix does not install. This behavior occurs because the system potentially can be made unusable if inconsistently matched files are used by the operating system. If inconsistently matched files are detected, you receive the following error message during the installation:

The installation failed. To proceed, check the log file in the Windows directory for details.

The following error message is logged in the installation log file:

Error : Could not determine version from core files

Before this error message is logged in the log file, the actual files that are being verified are also listed, together with the versions that are detected. Before you can install the hotfix, any inconsistencies must be corrected.

Note The MDAC version information is stored in the registry in the FullInstallVer entry in the following registry key:

</li> Verifies the hotfix language

The hotfix installer tool verifies whether the language of the hotfix matches the language of the existing MDAC installation. If the hotfix installer tool finds a mismatch, the hotfix installer tool reports an error that indicates the expected language. Then, you can overwrite the existing language with the version of the language that you want to install. This change is logged in the installation log file.</li> Checks for locked files

If the files that you want to update are locked by another service or by another process, the hotfix installer tool does not block the installation. If there are files that are locked, you are prompted to restart Windows at the end of the installation. The hotfix is not successfully installed until you restart Windows.</li> Backs up the current version of the files that are replaced

To enable removal of the hotfix, each file that is replaced is first backed up to an uninstall folder. The files that let you remove the hotfix installation are stored in the following folder:

%windir%\$SQLUninstall<packageName>$

For example, if you install a package with the file name &quot;MDAC28-KB887576-x86-ENU.exe,&quot; the uninstall folder is named as follows:

C:\WINNT\$SQLUninstallMDAC28-KB887576-x86-ENU.exe$</li> Updates the files

The hotfix installer tool replaces the files that are included in the hotfix. Then, the hotfix installer tool prompts for a restart if any one of those files are being used. The hotfix installer tool does not replace a file that has a later version with a file that has an earlier version.</li></ul>

back to the top

Perform an unattended installation
You can use one of the following command line parameters to install the hotfix. No user interaction is required.
 * /quiet

This command line parameter causes the hotfix installation to run in silent mode. No GUI windows appear.
 * /passive

This command line parameter causes the hotfix installation to run without user interaction. However, GUI windows do appear.

Note By default, the installer automatically forces a restart of the computer if a restart is required because of an unattended installation. To prevent this, use the /norestart command line parameter. For additional information, see the &quot;View command line parameters for the hotfix installer tool&quot; section.

back to the top

Remove a hotfix installation
The hotfix that is installed on your computer can be removed. This is a new feature of the hotfix installer tool. For every hotfix installation, an entry point is created in Control Panel. The entry point can be used for removing the hotfix installation. In Control Panel, &quot;Add/Remove Programs&quot; lists the hotfix instance that is installed on your computer. In &quot;Add/Remove Programs,&quot; you can click Remove, or you can click Change/Remove to remove a hotfix installation. A hotfix installation rollback is initiated when you try to remove the installation.

Starting with the MDAC 2.8 hotfix installer tool, installations can be rolled back in reverse order. You want to roll back in the reverse order if you installed multiple successive MDAC hotfix installations. If you try to remove a hotfix version after you apply a later hotfix version, the following error message is logged in the uninstall log file:

Uninstall detected that the product is patched with more recent updates. You must uninstall the more recent updates before uninstalling this patch.

When you perform a hotfix rollback, your computer is restored to the state that existed before you installed the hotfix. During rollback, the uninstaller reinstalls the backed-up files. Then, any registry key changes that were made during installation are reversed. You are prompted to restart if a restart is required to successfully complete removal of the hotfix.

Note If the package is installed with the &quot;/nobackup&quot; command line parameter, you receive the following error message when you try to remove the package:

You cannot uninstall, since an uninstall for <KB article number> has not been created.

back to the top

Understand the log files for the hotfix installer tool
Log files are created during installation of the hotfix and removal of a hotfix. The log files contain information about each action that is taken at each stage of the installation. The log files also contain the specific operation that is performed on each file.

The log files are saved in the %windir% folder. The log files are named as follows:
 * For installation, the log file is named .log.
 * For removal, the log file is named .-uninstall.log.

The placeholder  is the name of the self-extracting package that corresponds to the hotfix.

For example, log files for installation and for removal of the &quot;MDAC28-KB887576-x86-ENU.exe&quot; package are named as follows:
 * For installation, the log file is named MDAC28-KB887576-x86-ENU.log.
 * For removal, the log file is named MDAC28-KB887576-x86-ENU.-uninstall.log.

back to the top

View command line parameters for the hotfix installer tool
Note When the hotfix package is run with the &quot;/help&quot; command line parameter, the &quot;/overwriteoem&quot; command line parameter and the &quot;/integrate: &quot; command line parameter may be listed in addition to the command line parameters that are listed in the previous table. These two command line parameters are not implemented. These two command line parameters do not apply to the MDAC hotfix installer.

back to the top

View command line syntax examples for the hotfix installer tool

 * The command line syntax for an unattended installation of a hotfix without GUI windows follows:

MDAC28-KB887576-x86-ENU.exe /quiet
 * The command line syntax for an unattended installation of a hotfix without GUI windows and with a suppressed system restart follows:

MDAC28-KB887576-x86-ENU.exe /quiet /norestart
 * The command line syntax for the GUI-based removal of a hotfix follows:

MDAC28-KB887576-x86-ENU.exe /uninstall
 * The command line syntax for an unattended removal of a hotfix without a forced system restart follows:

MDAC28-KB887576-x86-ENU.exe /uninstall /quiet /norestart

back to the top

Keywords: kbhowto kbinfo kbtshoot KB890096

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.