Microsoft KB Archive/829183

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:10, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 829183

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 #: 470288 (SQL Server 8.0)
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

Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes 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.

SUMMARY

This article describes the following about this hotfix release:

  • The issues that are fixed by this hotfix package.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart your computer after you install the hotfix package.
  • Whether the hotfix package is replaced by any other hotfix package.
  • Whether you must make any registry changes.
  • The files that are contained in the hotfix package.

back to the top

Introduction

Issues that are fixed by this hotfix package

The following issue is fixed in this SQL Server 2000 hotfix package:

  • In SQL Server 2000, when you send an e-mail message by using the xp_sendmail extended stored procedure, the attached result set column widths are incorrect.


Note This problem only occurs when you set the xp_sendmail@no_header argument to "TRUE".

For a list of previous hotfixes, see the "Microsoft SQL Server 2000 Post-Service Pack 3 or Microsoft SQL Server 2000 Post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:

290211 How to obtain the latest SQL Server 2000 service pack


back to the top

CAUSE

This problem occurs when data in any one of the result set columns contains double-byte character set (DBCS) characters and the procedure pads the column widths incorrectly.

back to the top

MORE INFORMATION

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


Prerequisites

This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). For additional information about how to obtain SQL Server 2000 Service Pack 3, 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


back to the top

Restart information

You do not have to restart your computer after you apply this hotfix.

back to the top

Registry information

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.

You must make changes to the registry after you apply this hotfix. This hotfix introduces a new registry entry that is used to indicate whether the xp_sendmail extended stored procedure should pad the column widths. Therefore, after you apply this hotfix, you can add the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\DoNotPadColumns


Note By default, if you do not add this registry entry, the xp_sendmail extended stored procedure continues to pad column widths.

To add the registry entry, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer

  3. On the Edit menu, click New, and then click DWORD Value.
  4. Type DoNotPadColumns, and then press ENTER.
  5. Right-click DoNotPadColumns, and then click Modify.
  6. In the Edit DWORD Value dialog box, either type 0 (zero) to enable the padding of column widths or type 1 to disable the padding of column widths, and then click OK.
  7. On the File menu, click Exit.

Note This registry entry only works when you set the xp_sendmail@no_header argument to "TRUE".

back to the top

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

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
   ------------------------------------------------------------------
   18-Sep-2003  16:05  8.0.21213.0      352,256  Msvcr71.dll      
   18-Sep-2003  16:05  2000.80.796.0     57,904  Osql.exe         
   18-Sep-2003  16:05  2000.80.534.0    127,548  Sqdedev.dll      
   18-Sep-2003  16:05  2000.80.194.0    180,290  Sqlunirl.dll     
   31-May-2003  18:45  2000.80.818.0     78,400  Console.exe      
   25-Jun-2003  01:01  2000.80.818.0     33,340  Dbmslpcn.dll     
   25-Apr-2003  02:12                   786,432  Distmdl.ldf
   25-Apr-2003  02:12                 2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                       180  Drop_repl_hotfix.sql
   12-Sep-2003  03:26  2000.80.859.0  1,905,216  Dtspkg.dll       
   26-Aug-2003  20:16  2000.80.854.0    528,960  Dtspump.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       
   24-Apr-2003  02:51                   747,927  Instdist.sql
   03-May-2003  01:56                     1,581  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0     90,692  Msgprox.dll      
   01-Apr-2003  02:07                     1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0     62,024  Odsole70.dll     
   07-May-2003  20:41  2000.80.819.0     25,144  Opends60.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     
   04-Aug-2003  18:17                   550,780  Procsyst.sql
   12-Sep-2003  00:37                    12,305  Qfe469315.sql
   22-May-2003  22:57                    19,195  Qfe469571.sql
   06-Sep-2003  01:36                 1,090,932  Replmerg.sql
   06-Sep-2003  07:18  2000.80.858.0    221,768  Replprov.dll     
   06-Sep-2003  07:18  2000.80.858.0    307,784  Replrec.dll      
   06-Sep-2003  00:00                 1,087,150  Replsys.sql
   13-Aug-2003  16:28                   986,603  Repltran.sql
   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
   05-Aug-2003  21:06                   127,884  Sp3_serv_uni.sql
   01-Jun-2003  01:01  2000.80.818.0  4,215,360  Sqldmo.dll       
   07-Apr-2003  17:44                    25,172  Sqldumper.exe    
   19-Mar-2003  18:20  2000.80.789.0     28,672  Sqlevn70.rll
   27-Sep-2003  04:42  2000.80.865.0    180,792  Sqlmap70.dll     
   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
   08-Feb-2003  06:40  2000.80.765.0     57,920  Sqlrepss.dll     
   27-Sep-2003  04:42  2000.80.865.0  7,606,353  Sqlservr.exe     
   25-Jul-2003  21:44  2000.80.845.0    590,396  Sqlsort.dll      
   08-Feb-2003  06:40  2000.80.765.0     45,644  Sqlvdi.dll       
   25-Jun-2003  01:01  2000.80.818.0     33,340  Ssmslpcn.dll     
   01-Jun-2003  01:01  2000.80.818.0     82,492  Ssnetlib.dll     
   01-Jun-2003  01:01  2000.80.818.0     25,148  Ssnmpn70.dll     
   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     
   30-Apr-2003  23:52  2000.80.816.0     45,132  Ums.dll          
   02-Jul-2003  00:19  2000.80.834.0     98,816  Xpweb70.dll      
   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.back to the top

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.

MORE INFORMATION

For more information about the xp_sendmail extended stored procedure, visit the following Microsoft Developer Network (MSDN) Web site:

For additional information about the naming schema for Microsoft SQL Server updates, 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


For additional information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


back to the top


Additional query words: SQL2000 DBCS

Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB829183