Before you apply SQL Server 2000 Service Pack 3 or SQL
Server 2000 Service Pack 3a to a cluster, or before you apply SQL Server 2000
Service Pack 3 or SQL Server 2000 Service Pack 3a with any unattended
installation, you must first verify that no SQL Server files are marked as
"read only." If any files are marked "read only", follow these steps:
Open a MS-DOS prompt, and then locate the C:\Program Files\Microsoft SQL Server folder.
At the command prompt, type Run ATTRIB /S
-R.
Repeat this on all the nodes.
The following information has changed since the publication of
SP3Readme.htm file:
Computers that are running Microsoft Windows XP will not be updated to Microsoft Data Access Components 2.7 (MDAC) Service Pack 1 (SP1).
When installing SQL Server 2000 SP3 on computers that
are running Windows XP, MDAC 2.7 will not be updated to MDAC 2.7 Service Pack 1
(SP1). If your system requires any of the fixes included in MDAC 2.7 SP1, you
must first apply Windows XP Service Pack 1 before you install SQL Server 2000
SP3.
Clarification to Section 3.7 - Install Desktop Engine
Section 3.7 of the SP3Readme.htm file states that SQL
Server 2000 SP3 for Desktop Engine (also known as MSDE 2000) is available from
the following sources:
The SQL Server 2000 Service Pack 3 CD-ROM.
Through SQL2KdeskSP3.exe. You can download this
self-extracting file from the Microsoft SQL Server Downloads Web
site.
SQL Server Service Pack 3 for Desktop Engine was not
originally included with SQL Server Service Pack 3. To download SQL Server
Service Pack 3 for Desktop Engine, visit the following Microsoft Web
site: Microsoft SQL
Server 2000 Service Pack 3
(http://www.microsoft.com/downloads/details.aspx?familyid=90DCD52C-0488-4E46-AFBF-ACACE5369FA3&displaylang=en)
Select the language you want to use
from the box located at the upper-right of the page.
Hotfix Required for Computers That Are Running Microsoft Windows NT Server 4.0 Service Pack 6a
If you are running Microsoft Windows NT Server 4.0
Service Pack 6a, you must apply the hotfix that is described in the following
Microsoft Knowledge Base article:
258437
(http://support.microsoft.com/kb/258437/EN-US/
)
FIX: GetEffectiveRightsFromAcl() Fails in Service Pack 6
Setup Runs in Single-User Mode
To install SQL Server 2000 SP3, SQL Server must be in
single-user mode. The Setup starts SQL Server in single-user mode. To prevent
any other application from having control of the first server process ID
(SPID), complete the following tasks:
Close all applications that are running, including
third-party monitoring tools on the computer that is running SQL
Server.
Disconnect or shut down all the application servers
that connect to the computer that is running SQL Server.
Disconnect the network cable, if you can.
You may also change any logon passwords for connected
application servers; however, you must remember to change them back to their
original password after the setup completes.
For additional
information about services and applications that may interfere with Setup, see
the following article in the Microsoft Knowledge Base:
183692
(http://support.microsoft.com/kb/183692/EN-US/
)
PRB: SQL Server Setup Appears to Stop Responding
SQL Server Agent Mail Requirements
With SQL Server 2000, you can configure SQL Server Agent
Mail to send e-mail messages by using a MAPI connection. However, you must use
extended MAPI on 32-bit operating systems. You can only use simple MAPI on
64-bit operating systems.
Service Packs Released Before SQL Server 2000 Service Pack 3a are Not Supported for SQL Server 2000 Enterprise Evaluation Edition
SQL Server 2000 service packs released before SQL Server
2000 Service Pack 3a are not supported for SQL Server 2000 Enterprise
Evaluation Edition. Service packs can be applied to all other versions of
Microsoft SQL Server 2000. If you try such an installation, you will receive
the following error message:
MSSQLSERVER is an Evaluation
version. Cannot upgrade an Evaluation version of SQL Server 2000. Setup will
now exit.
This error message is also described in the following
Microsoft Knowledge Base article:
315518
(http://support.microsoft.com/kb/315518/EN-US/
)
INF: Cannot Apply Service Pack to Evaluation Edition
For information about functionality changes to SQL
Server 2000 introduced in SQL Server 2000 SP3, see the SQL Server 2000 SP3
Readme file. The Readme file is available in your downloaded files.
Clarification to Section 3.10 - Installing on a Failover
Cluster
In section 3.10, under the title "If you need to rebuild
a node in the failover cluster, follow these steps", it should read as follows:
Rebuild the node in the failover cluster. For more
information about rebuilding a node, see the "How to recover from failover
cluster failure in Scenario 1" topic in SQL Server Books Online.
Run the original SQL Server 2000 Setup program to add
the node back to the failover cluster.
Run the SQL Server 2000 SP3 Setup program from the
newly added node. This will update the binaries only on the new node to the SQL
Server 2000 SP3 level.
Note If you run Setup from the node where the virtual server is
running, you must reapply SQL Server 2000 SP3 to all the nodes. You must also
rerun the database upgrade scripts.
Clarification to Section 5.3.17 - Change to Requirements for Attaching or Restoring a Replication Database
Section 5.3.17 "Change to Requirements for Attaching or
Restoring a Replication Database" in the SQL Server 2000 SP3 Readme file
incorrectly implies that enabling cross-database ownership chaining is a
requirement for attaching or restoring replication databases after SQL Server
2000 SP3 has been applied. The preferred method for attaching or restoring
databases after applying SQL Server 2000 SP3, is to have a member of the sysadmin fixed server role run the sp_changedbowner stored procedure to assign ownership of the database to the sa built-in administrator logon. For example:
EXEC sp_changedbowner 'sa'
Clarification to Section 5.1.8 - New SQLServerLIKE Provider Option
Section 5.1.8 discusses the new SQLServerLIKE Provider
option. This option is invoked with a registry entry, SQLServerLIKE. To add and enable the SQLServerLIKE registry entry, use Registry Editor and locate the following
registry key.
Under the <Provider>
key, add a DWORD value. Name it SQLServerLIKE, and then set its value data to
1.
Clarification for Section 3.0 - Service Pack Installation
In section 3.0, the following note is incomplete:
Note Because non-writable databases no longer cause the Setup to fail,
you do not have to remove log shipping before you upgrade to SQL Server 2000
SP3.
Although this may be true, if you are upgrading a server that is
involved in log shipping with a database that is also a publisher on another
server, the setup may fail and you receive the following error
message:
Error Running Script sp_vupgrade_replication
(1)
Currently, the replication upgrade process does not look for
read-only databases. To avoid this error, take the database offline before you
run the SQL Server 2000 SP3 Setup. This will cause the replication upgrade
process to skip upgrading the database.
After the upgrade completes,
bring the database online, and then run the sp_vupgrade_replication stored procedure to upgrade replication metadata.
Note The sp_vupgrade_replication stored procedure is installed in the master database during the upgrade to SQL Server 2000 SP3. To run this
stored procedure, start Query Analyzer, and then run the following:
Use master
Go
Exec sp_vupgrade_replication
Must Enable File and Print Sharing for a Successful MSDE Installation
Make sure that you have File and Print Sharing enabled
before you try to install MSDE. If you do not have File and Print Sharing for
Microsoft Networks enabled in the Network Connections property
box, the installation process may continue until it is almost finished and then
unexpectedly roll back. If this occurs, MSDE did not install successfully.
Back to the top
