Description of the 64-bit SQL Server 2000 hotfix installer (872912)
The information in this article applies to:
- Microsoft SQL Server 2000 64 bit (all editions)
SUMMARYThis article describes a Microsoft SQL Server hotfix installer that is used to apply 64-bit hotfixes on an instance of SQL Server 2000. This article discusses the following topics: - How the hotfix installer files are named
- How to use the hotfix installer
- How the hotfix installer works
- How to perform an unattended installation
- Log file for the hotfix installer
- How to remove a hotfix
installation
INTRODUCTIONThis article describes the 64-bit SQL Server hotfix
installer that is used to apply SQL Server 2000 64-bit
hotfixes on stand-alone instances and clustered instances of SQL Server 2000
(64-bit). SQL Server 2000 (64-bit) hotfixes are created as
Microsoft Windows Installer patches that are packaged and delivered to users as
self-extracting executable files. The hotfix installer can also run
in unattended mode to automate the hotfix installation process across your
whole organization. If you have to apply a hotfix to an instance of
SQL Server 2000 32-bit, see following Microsoft Knowledge Base article: 842960 Description of the 32-bit SQL Server 7.0 and SQL Server 2000 hotfix installer
back to the topHow the hotfix installer files are namedMicrosoft has adopted a standardized naming schema for the
hotfix installer packages in SQL Server.
For additional information about the new naming
schema for Microsoft SQL Server software update packages, click the following article number to view the article in the Microsoft Knowledge Base:
822499
New naming schema for Microsoft SQL Server software update packages
back to the topHow to use the hotfix installerTo start the hotfix installation process, you must log on to
the computer by using a user account that has local administrative credentials, and
then run the self-extracting executable file. When you run the self-extracting
executable file, the files that are related to the hotfix are extracted from
the hotfix package and stored on the computer. If you experience disk space
errors when you run the self-extracting executable file, see the following Microsoft Knowledge Base article: 301913 BUG: Error message: "There is not enough space on drive" occurs when you extract SQL Server 2000 downloads
When you start the hotfix installation
process, a GUI-based hotfix installer tool
starts, and the GUI guides you through the rest of the installation process.
back to the topHow the hotfix installer worksWhen you run a hotfix installer that is packaged as a
self-extracting executable file, the hotfix installer performs the following
operations:
- The hotfix installer extracts the files that are
packaged in the self-extracting executable file to a temporary folder that is
similar to the following:
%windir%\GUID - The hotfix installer verifies the architecture of your
computer. If the architecture of your computer does not qualify for
the hotfix to be installed, you may receive a message that the hotfix
installer is not valid. For example, when you try to run a hotfix installer that is compiled to run on the IA-64
architecture on a computer with the x86 architecture, you may receive a message that is similar to the
following:
Hotfix.exe is not a valid Win32
application. - The hotfix installer makes sure that the user account that
you used to log on to the computer has administrative credentials. If the
user account does not have administrative credentials, you may receive a
message that is similar to the following:
In order to
run this update, you must logon to this computer with an account that has
administrator privileges. - The hotfix installer verifies the operating system that
is running on your computer. If the operating system does not qualify for the
hotfix, you may receive a 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 operation system and retry the
installation. - The hotfix installer automatically detects all the
instances of SQL Server and enumerates the list of the instances that
qualify for the hotfix. You may see that all the instances of SQL Server that
are running on the computer appear in the GUI of the Setup program. From the
list, you can select a subset of instances where you want the hotfix to be
applied. In the GUI of the Setup program, the instances of SQL Server that
do not qualify for the hotfix are not available. You cannot select those instances of SQL Server.
To
qualify for the hotfix, the SQL Server installation must meet certain
requirements. For example, if the hotfix requires the installation of SQL Server 2000 Service Pack 3 (SP3), you must install SQL Server 2000
SP3 before you run the hotfix.
If the instances of SQL
Server do not qualify for the hotfix because the hotfix does
not qualify, you may receive messages that are similar to the
following:Due to SQL Server service pack
requirements, this machine does not have a product that matches this
installation package. To proceed, refer to installation package requirements in
the release notes, install the required SQL Server service pack, and then run
the installation again. Due to SQL Server
language compatibility requirements, this machine does not have a product that
matches this installation package. To proceed, you must download and run the
installation package that matches the locale setting of your
computer. Due to SQL Server edition
requirements, this computer does not have a product that matches this
installation package. To proceed, refer to the release notes for this
installation. You must run an installation package that is compatible with the
SQL Server instance to be updated. Note The Microsoft Knowledge Base article for each hotfix
contains more information about the requirements for applying the hotfix.
The hotfix installer can detect instances of SQL Server that
are clustered and determine whether the computer where the hotfix
installer is being run is the active node. - The hotfix installer prompts you for the authentication
information that you used to connect to the instance of SQL Server. For example,
the hotfix installer prompts you for SQL Server authentication information or Windows
authentication information. If you use SQL Server authentication, you must provide the
password for the system administrator (sa) user account. If you want to use SQL
Server authentication, you must make sure that the instance of SQL Server is
configured for Mixed Mode security.
If you use Windows
authentication, you must be logged on to the computer by using an account that
is a part of the System Administrators server role for the instance of SQL
Server that you are upgrading. If the authentication information is not correct, you
may receive a message that is similar to the following:Your account information could not be verified for one or
more instances.
Ensure that you can connect to all the selected
instances using the account information provided.
To proceed further
deselect the instances to which connectivity cannot be
established. If you selected an instance of SQL Server that
is clustered, and the instance is an active node, the hotfix installer prompts
you for remote logon information after you are prompted for the authentication
information that is used to connect to the instance of SQL
Server. - The hotfix installer stops both the MSSQLSERVER service
and the SQL Server Agent services for the instance that is being upgraded. If
you are updating SQL Server 2000 Analysis Services, the
MSSQLServerOLAPService service is stopped.
- If the files that are to be replaced by the hotfix
installer are locked by another service or process, you may receive an error
message that is similar to the following:
The
following files are currently locked.
In order to prevent a necessary
reboot at the end of the patch install process, close down all other
applications before
proceeding.
PathToFileName1\FileName1 PathToFileName2\FileName1 If you click
Cancel in the message box, the hotfix installation stops. You can close the program that causes a lock on the files, and then click Try
Again to continue the hotfix installation. If you do not know
the program that is causing the lock, click Continue to continue the hotfix installation. After the hotfix is successfully installed, you are
prompted to restart the computer.
Note You do not always receive this error message because some
files may not be locked when the check is made. The files may
be locked when the hotfix installer tries to update the files
that correspond to the hotfix or in the future.
If the hotfix
installer determines that the files that must be replaced by the hotfix
installer are locked, the hotfix installer cannot replace these files.
Therefore, the hotfix installer adds these files to the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\PendingFileRenames registry key. When this situation occurs, you
receive a warning message that is similar to the following:Pending file operations exist on the
computer.
Though these do not impact the files patched by this
installation, it is recommended that you reboot the computer. If
you receive this message, the hotfix installation is not complete until
you restart your computer. After you restart your computer, the operating
system replaces the files that are added to the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\PendingFileRenames registry key on your computer, and
then clears this registry key.
If
you receive a warning to restart your computer at the end of the hotfix installation, we recommend that you restart
your computer so that all applications function correctly. - The hotfix installer updates the
existing files with the hotfix files. To do
this, the program searches the destination computer to make sure that the files
are present. If the files exist on the destination computer, the files can be replaced. After a file passes this check, the file version is compared
with the source file. If the version of the source file is later than the
version of the file that is being installed by the hotfix installer, the hotfix
installer does not replace the file. For files that do not have a version number, the
program uses the time and date information to create a list of files to install.
- After all the required files are updated successfully, the
hotfix installer runs the scripts against the system databases.
back to the topHow to apply a hotfix on a clusterIf you select an instance of SQL Server that is clustered
and the instance is an active node, the hotfix installer prompts you for your
remote logon information. The remote logon information is used to connect to
the remote nodes and to run the remote processes. The hotfix installer takes the
SQL Server cluster group offline and updates the binaries on all the passive
nodes of the cluster. The remote processes are used to update the passive nodes
of the cluster. Note If you run the hotfix installer on a node that is not the
active node, the Details pane displays a message that is similar to the
following: This installation must be run from the
active node. You are running it from a passive node. To proceed, cancel the
installation and run it again from the active node. back to the topHow to perform an unattended installation An unattended installation is similar to the interactive
installation that is described in the "How to use the hotfix installer" section. To start an unattended installation of
a hotfix, you can use the command-line parameters and the self-extracting
executable file that corresponds to the hotfix. When you run the self-extracting
executable file that corresponds to the hotfix at a command prompt, you can
use the following command-line parameters:
- /?: This command-line parameter causes the hotfix installation to
display the details about the command-line switches that are
available.
- /quiet: This command-line parameter causes the hotfix installation to
run in silent mode.
- /reportonly: This command-line parameter can be used to provide a snapshot of
all the instances of SQL Server 2000 (64-bit), including the version number, the service pack
level, the language, and the hotfix level, before the hotfix is installed.
- /allinstances: This command-line parameter is used if you want to apply the
hotfix on all the instances of SQL Server that qualify for the
hotfix.
- /INSTANCENAME: This command-line parameter is used to specify the instances of SQL Server where you want the hotfix applied (/INSTANCENAME=YourInstanceName, for example). If you want to apply the
hotfix on multiple instances, you can use a comma delimiter to separate the instance names (/INSTANCENAME=InstanceName1,
InstanceName2, InstanceName3, for example). If one or more of the
instances in the list do not exist or do not qualify for the hotfix, the
hotfix installer only installs the hotfix on instances that qualify for the
hotfix.
- /USER: This command-line parameter is used to specify the user account
that is used to connect to all nodes of a cluster. This account must be a local
administrator account an all nodes.
- /PASSWORD: This command-line parameter is used to specify the password of
the user account that is specified for the /USER parameter.
- /SAPWD: This command-line parameter is used to specify the password
that is used to connect to the instance of SQL Server to run the SQL scripts. If the switch
is not specified, the hotfix installer automatically uses Windows
authentication. If the password for the user sa is blank, you only have to specify /SAPWD in the command line.
Command-line examplesback to the topLog file for the hotfix installerThe actions that are performed by the hotfix installation
process are recorded in the log file that corresponds to the hotfix
installation. The hotfix installer log files are saved in the %windir%\Hotfix folder. The Hotfix.log file is the current log file and contains
the general status of the hotfix installation. Depending on whether you
are running a hotfix installer for SQL Server 2000 (64-bit) or a
hotfix installer for Analysis Services (64-bit), you
may see any one of the following in the same location:
- If you
are running a hotfix installer for SQL Server 2000 (64-bit), a folder named SQL64 contains the following three types of log files:
- SQL64_Hotfix_KBnumber_.log: This log file includes the
specific details of the hotfix that was applied. For example, this file includes information about the
instance of SQL Server that where the hotfix was installed, the command line that was used to
install the hotfix, and the result of the hotfix installation.
- SQL64_Hotfix_KBnumber_sqlrun.msp.log: This log file includes
the log output of the Windows installer.
- SQL64_Hotfix_KBnumber_script name.log: This log file includes the output log of the script that was executed as part of the hotfix
installation. Each script that is executed as part of a hotfix installation has a script output log.
- If you
are running a hotfix installer for Analysis Services (64-bit), a folder named OLAP64 contains the following three types of log files:
- OLAP64_Hotfix_KBnumber_.log: This log file includes
the specific details of the hotfix that was applied. For example, this file includes information about the
instance of SQL Server where the hotfix was installed, the command line that was used to
install the hotfix, and the result of the hotfix installation.
- OLAP64_Hotfix_KBnumber_sqlrun.msp.log: This log file includes
the log output of the Windows Installer.
- OLAP64_Hotfix_KBnumber_script name.log: This log file includes the output log of the script that was executed as part of the hotfix
application. Each script that is executed as part of a hotfix installation has
a script output log.
back to the topHow to remove a hotfix
installationThe hotfix that is being installed on the
instance of SQL Server can be removed from the computer. For every hotfix
installation, an entry point is created in Control Panel that can be used to remove the hotfix. The Add or Remove Programs window in Control Panel displays the hotfixes that are installed on the computer. To remove a hotfix installation, click Remove or Change/Remove for the hotfix installation in the Add or Remove Programs window. A hotfix
rollback is initiated when you try to remove the installation. Because SQL Server 2000 hotfix build 977 is used as the baseline, you can rollback any hotfix
when a hotfix build that is later than build 977 is installed on your computer. You can remove each hotfix build that is later than build 977 in reverse order back to hotfix build 977. Note You cannot remove a hotfix installation from a computer if the
computer does not have Windows Installer version 3.0 runtime installed on
it. When you perform a hotfix rollback, the computer is restored
to the state that existed before you installed the hotfix. During rollback, the
installer reinstalls the backed up files, reverses the registry key operations,
runs the reverse scripts that correspond to the SQL scripts that were used
during installation, and runs the reverse processes to reverse the changes that
were made during installation. The user account that you used to log
on to the computer must have the administrative credentials to remove a hotfix. If you try to remove a version of a hotfix that is earlier than the current version that is
installed on the instance of SQL Server, the rollback is not
initiated. Rollback and removal in a clusterOn a clustered instance, the hotfix installer determines whether
the instance is an active node, and then removes the hotfix from the cluster. Note You cannot initiate the removal of hotfix from a passive node of
the cluster. back to the top
Modification Type: | Minor | Last Reviewed: | 3/18/2006 |
---|
Keywords: | kbPackage kbsetup kbpatch kbuninstall kbUnattended kbClustering kbinfo kbhowto KB872912 kbAudDeveloper kbAudITPRO |
---|
|
|
©2004 Microsoft Corporation. All rights reserved.
|
|