Knowledge Base

FIX: Issues that are resolved in SQL Server 2000 build 8.00.0859

Article ID: 821334

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

BUG #: 469315 (SQL Server 8.0)
BUG # 470266 (SQL Server 8.0)
BUG#: 470299 (SQL Server 8.0)
BUG# 362394 (SQL Server 8.0)
BUG #469853 (SQL Server 8.0)

SYMPTOMS

The following issues are resolved in Microsoft SQL Server 2000 build 8.00.0859:

You create a SQL Server Agent job in the security context of system account (such as the NT Authority\Network Service account or the NT Authority\System account). When you run the job, the job may not be successful, and you may receive the following error message:

Msg 8198, Level 16, State 1, Line 1
Could not obtain information about Windows NT group/user 'NT AUTHORITY\NETWORK SERVICE'.
When you create a stored procedure that calls RAISERROR with a severity that is greater than 10, the stored procedure may run two times. This issue only occurs after you apply the hotfix in the following Microsoft Knowledge Base article:

815115 FIX: A DTS package that uses global variables ignores error message raised by RAISERROR
When you set an IDENTITY_INSERT value on a server table, it is may not be reflected on the client. Because of this issue, the ability to update a column may not be reported correctly.
The potential for inconsistency in the backup history tables backupset and backupmediafamily is resolved. This issue may cause the restore process to point to the wrong backup files.
Remote procedures that contain code that includes RAISERROR may return datasets that are not complete.

Note Microsoft SQL Server 2000 Service Pack 3 and SQL Server 2000 Service Pack 3a hotfixes are cumulative; each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.

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
   -------------------------------------------------------------
   12-Sep-2003  03:26  2000.80.859.0   1,905,216  Dtspkg.dll       
   23-Jun-2003  22:40  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  22:40  2000.80.837.0     639,552  Dtswiz.dll       
   02-Apr-2003  21:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  23:15  2000.80.797.0     279,104  Pfutil80.dll     
   29-Jul-2003  20:13  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  18:27  2000.80.818.0     172,032  Semobj.rll
   01-Jun-2003  01:01  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  17:44                     25,172  Sqldumper.exe    
   03-Sep-2003  02:56  2000.80.857.0     188,992  Sqlmmc.dll       
   02-Sep-2003  23:03  2000.80.857.0     479,232  Sqlmmc.rll
   01-Jun-2003  01:01  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  18:59  2000.80.818.0      76,416  Svrnetcn.exe

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.

REFERENCES

For additional information about the SQL Server Hotfix installer, click the following article number to view the article in the Microsoft Knowledge Base:

330391 SQL Server Hotfix installer

Keywords: kberrmsg kbdownload kbbug kbfix kbuser kbqfe kbsqlserv2000presp4fix atdownload KB821334

Microsoft KB Archive/821334

Contents