Additional Notes About Microsoft Exchange Server

WARNING: You must have previously installed Microsoft Exchange Server 5.5 
         Service Pack 2 in order to apply this patch.

This document contains information not available in the Microsoft Exchange
Server documentation, as well as information on changes that occurred after
publication.  If you enlarge the Write window to its maximum size, this document
will be easier to read. To do so, click the Maximize button in the
upper-right corner of the window.  To move through the document, press PAGE UP
or PAGE DOWN, or click the scroll bar along the right side of the Write window.
To print the document, choose Print from the File menu. For Help on using Write,
press F1.

Installing Microsoft Exchange Server 5.5 Post SP2 patch for the
Exchange Server database engine.

STEP TO INSTALL
==============

Download the compressed setup file appropriate for the server for your hardware
platform. Select the appropriate files as indicated by the following list:
		
		Alpha AXP(TM)		PSP2ESEA.EXE
		Intel(R)		PSP2ESEI.EXE
		

1.  Download appropriate file to a temporary location on the servers local hard 
    drive.
    Example: English version for the Intel platform will be located at :

    ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/ENG
    /Exchg5.5/PostSP2/ESE-fix/PSP2ESEI.EXE

2.  Unzip the file by typing the file name of the self-extracting archive
    at the command prompt.
    Example: The version for the Intel platform will be PSP2ESEI.
3.  Stop the Microsoft Exchange Directory Service.
4.  For Intel and Alpha archives, the Hotfix utility is included that helps automate the
    installation process of the hotfix.  It is recommended to consult HOTFIX.TXT in the          archive for more information.  If you prefer a manual installation, 
    continue following the remaining steps listed below.
5. Go to the Exchange servers Windows system32 directory Example: c:\Winnt\system32\.
6. Rename the old  file ESE.DLL to ESE.BAK. 
7. Copy the new ESE.DLL into the directory.
8. Go to the Exchange servers Windows system32 directory Example: c:\Winnt\system32\.
9. Rename the old file ESEPERF.DLL to ESEPERF.BAK. 
10. Copy the new ESEPERF.DLL into the directory.
11. Go to the Exchange servers Windows system32 directory Example: c:\Winnt\system32\.
12. Rename the old file EDBBCLI.DLL to EDBBCLI.BAK. 
13. Copy the new EDBBCLI.DLL into the directory.
14. Restart the Microsoft Exchange services.

If you have the Exchange symbols installed, replace the old DBG files
with the newer version in the <systemroot>\symbols\dll directory.

List of Bugs Fixed in Microsoft Exchange Server Post SP2 
update for the Exchange Server database engine.

Note: Use the Qxxxxxx number to query the Microsoft Knowledge Base for an 
article about that bug.

Article ID: 

197500	XADM: Tape Backup Program Hangs During Exchange Backup
214635	XADM: ESEUTIL /P Crashes on a Corrupt Database
214684	XADM: Information Store Crashes Due to Database Corruption Occurring after a Faulty Rollback Operation on a Transaction
216532	XADM: Exchange Server 5.5 Does Not Function Properly on DEC Alpha EV6 Computer
218439	XADM: PerfMon Counters for Monitoring Exchange DB Sessions
230215	XADM: Backup Checksuming Not Performed on Single Processor Computers
230691	XADM: Space Tree Fragmentation in Exchange Database Engine Can Degrade Server Performance
234432	XADM: Running Isinteg May Truncate Databases to 8 KB
234764	XADM: Eseutil Ends with -1808 (Jet_ErrDiskFull) on /P or /G
237422	XADM: ESEUTIL /P Aborts with -1605, JET_errKeyDuplicate
237953	XADM: Erroneous -1018 Error Returned During Online Backup

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT 
WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, 
INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN 
NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES 
WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS 
PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN 
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING 
LIMITATION MAY NOT APPLY. 

©1999 Microsoft Corporation