Microsoft KB Archive/816985: Difference between revisions
(importing KB archive) |
(No difference)
|
Latest revision as of 18:04, 18 July 2020
Article ID: 816985
Article Last Modified on 11/2/2007
APPLIES TO
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Personal Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Desktop Engine (Windows)
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
SYMPTOMS
When you apply Microsoft SQL Server 2000 Service Pack 3 (SP3) to an instance of the Korean version of SQL Server 2000 that has one or more read-only databases (log shipping is configured, for example), the installation is not successful. You receive the following error message in Korean:
Note This problem only occurs in the Korean version of SQL Server 2000 SP3.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
Hotfix information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------ 06-Mar-2003 01:23 26,539 _user1.cab 06-Mar-2003 01:23 5,309 _user1.hdr
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB816985