Microsoft KB Archive/814894: Difference between revisions
(importing KB archive) |
m (Text replacement - ">" to ">") |
||
(One intermediate revision by the same user not shown) | |||
Line 106: | Line 106: | ||
<div class="indent"> | <div class="indent"> | ||
<code>HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\ | <code>HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer </code> | ||
Latest revision as of 10:20, 21 July 2020
Article ID: 814894
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
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
When the xp_readmail extended stored procedure saves an attachment of type "Message Format(*.msg)", only the body of the attached mail is saved as a text file.
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 fix has the file attributes (or later) 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 ------------------------------------------------------------------------- 08-Feb-2003 05:43 786,432 bytes Distmdl.ldf 08-Feb-2003 05:43 2,359,296 bytes Distmdl.mdf 30-Jan-2003 01:55 180 bytes Drop_repl_hotfix.sql 30-Jan-2003 05:18 746,470 bytes Instdist.sql 30-Jan-2003 01:55 1,402 bytes Inst_repl_hotfix.sql 08-Feb-2003 06:40 2000.80.765.0 90,692 bytes Msgprox.dll 08-Feb-2003 03:53 1,065,895 bytes Replmerg.sql 08-Feb-2003 06:40 2000.80.765.0 221,768 bytes Replprov.dll 08-Feb-2003 06:40 2000.80.765.0 307,784 bytes Replrec.dll 30-Jan-2003 05:18 1,084,318 bytes Replsys.sql 08-Feb-2003 06:40 2000.80.765.0 176,696 bytes Sqlmap70.dll 08-Feb-2003 06:40 2000.80.765.0 57,920 bytes Sqlrepss.dll 08-Feb-2003 06:41 2000.80.765.0 7,528,529 bytes Sqlservr.exe 08-Feb-2003 06:40 2000.80.765.0 45,644 bytes Sqlvdi.dll 08-Feb-2003 06:40 2000.80.765.0 82,492 bytes Ssnetlib.dll
Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
This fix works with a registry entry, PreserveAttachedMessageFileFormat. If you turn on PreserveAttachedMessageFileFormat, SQL Server will save the whole attachment as a "Message Format(*.msg)" file.
To add and to turn on the PreserveAttachedMessageFileFormat registry entry, use the Registry Editor and locate this registry key:
For a computer with a named instance of SQL Server:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer
For a computer with a default instance:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer
Under the MSSQLServer key, add a DWORD value, and then name it PreserveAttachedMessageFileFormat. Set its value data to 1.
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 kbhotfixserver KB814894