There is no option to turn off IMAIL exception handling in Exchange 2000 Server

Article translations Article translations
Article ID: 832174 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
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
Expand all | Collapse all

SYMPTOMS

In Microsoft Exchange 2000 Server, you may find that you cannot turn off IMAIL exception handling. In certain troubleshooting scenarios, you may want to turn off IMAIL exception handling, but there is no option to do so.

RESOLUTION

To resolve this problem, obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup


The English version of this hotfix 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
--------------------------------------------------------------
17-Dec-2003  03:11  6.0.6548.0        716,800  Cdo.dll          
17-Dec-2003  04:23  6.0.6548.0      3,919,872  Cdoex.dll        
17-Dec-2003  03:03  6.0.6548.0        561,152  Cdohtml.dll      
17-Dec-2003  04:18  6.0.6548.0        856,064  Davex.dll        
17-Dec-2003  04:18  6.0.6548.0         53,248  Davexpc.dll      
17-Dec-2003  04:14  6.0.6548.0        131,072  Drviis.dll       
17-Dec-2003  04:15  6.0.6548.0        577,536  Dsaccess.dll     
17-Dec-2003  03:24  6.0.6548.0        184,320  Dscmsg.dll       
17-Dec-2003  03:23  6.0.6548.0        962,560  Emsmdb32.dll     
17-Dec-2003  04:17  6.0.6548.0      2,179,072  Ese.dll          
17-Dec-2003  04:17  6.0.6548.0         40,960  Eseperf.dll      
17-Dec-2003  04:23  6.0.6548.0      3,575,808  Excdo.dll        
17-Dec-2003  04:14  6.0.6548.0         90,112  Eximap4.dll      
17-Dec-2003  04:15  6.0.6548.0        262,144  Exmime.dll       
17-Dec-2003  03:03  6.0.6548.0        176,128  Exnntp.dll       
17-Dec-2003  04:18  6.0.6548.0        143,360  Exodbesh.dll     
17-Dec-2003  04:18  6.0.6548.0         57,344  Exodbpc.dll      
17-Dec-2003  04:18  6.0.6548.0        200,704  Exodbprx.dll     
17-Dec-2003  04:18  6.0.6548.0      2,179,072  Exoledb.dll      
17-Dec-2003  04:12  6.0.6548.0         81,920  Exosal.dll       
17-Dec-2003  04:14  6.0.6548.0         32,768  Expop3.dll       
17-Dec-2003  04:15  6.0.6548.0         32,768  Exproto.dll      
17-Dec-2003  04:18  6.0.6548.0        307,200  Exprox.dll       
17-Dec-2003  04:18  6.0.6548.0        319,488  Exsmtp.dll       
17-Dec-2003  03:30  6.0.6548.0        675,840  Exwform.dll      
17-Dec-2003  03:04  6.0.6548.0        180,224  Exwin32.dll      
17-Dec-2003  03:27  6.0.6548.0         40,960  Febecfg.dll      
17-Dec-2003  04:14  6.0.6548.0         32,768  Iisif.dll        
17-Dec-2003  04:15  6.0.6548.0        135,168  Iisproto.dll     
17-Dec-2003  04:16  6.0.6548.0         61,440  Imap4be.dll      
17-Dec-2003  03:31  6.0.6548.0        319,488  Imap4evt.dll     
17-Dec-2003  03:29  6.0.6548.0        126,976  Imap4fe.dll      
17-Dec-2003  04:14  6.0.6548.0        126,976  Imap4svc.dll     
17-Dec-2003  04:15  6.0.6548.0         40,960  Jcb.dll          
17-Dec-2003  03:04  6.0.6548.0         49,152  Mdbevent.dll     
17-Dec-2003  03:21  6.0.6548.0      2,289,664  Mdbmsg.dll       
17-Dec-2003  03:06  6.0.6548.0         32,768  Mdbrole.dll      
17-Dec-2003  03:23  6.0.6548.0        909,312  Mdbsz.dll        
17-Dec-2003  04:15  6.0.6548.0         24,576  Mdbtask.dll      
17-Dec-2003  03:03  6.0.6548.0        151,552  Nntpex.dll       
17-Dec-2003  04:11  6.0.6548.0         94,208  Peexch50.dll     
17-Dec-2003  04:12  6.0.6548.0        397,312  Phatcat.dll      
17-Dec-2003  04:14  6.0.6548.0         36,864  Pop3be.dll       
17-Dec-2003  03:31  6.0.6548.0        303,104  Pop3evt.dll      
17-Dec-2003  03:29  6.0.6548.0         24,576  Pop3fe.dll       
17-Dec-2003  04:12  6.0.6548.0         73,728  Pop3svc.dll      
17-Dec-2003  03:31  6.0.6548.0        163,840  Protomsg.dll     
17-Dec-2003  04:15  6.0.6548.0        528,384  Reapi.dll        
17-Dec-2003  04:18  6.0.6548.0        311,296  Resvc.dll        
17-Dec-2003  03:30  6.0.6548.0      3,735,552  Wmtemplates.dll  
17-Dec-2003  03:04  6.0.6548.0         40,960  X400omv1.dll     
17-Dec-2003  03:14  6.0.6548.0      1,798,144  Emsmta.exe       
17-Dec-2003  03:28  6.0.6548.0        143,360  Exschema.exe     
17-Dec-2003  04:14  6.0.6548.0      4,669,440  Store.exe        
16-Dec-2003  01:01                     12,720  Ctrl_calendarview20.htc
16-Dec-2003  01:06                      6,991  Eseperf.hxx
17-Dec-2003  04:17                    391,634  Eseperf.ini
16-Dec-2003  01:01                     91,631  Ctrl_calendarview20.js
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

After you apply the hotfix that is described in this article, add the ExceptionHandling registry entry to the following registry key to configure IMAIL exception handling:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent
To do so:

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.
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate, and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type ExceptionHandling, and then press ENTER.
  6. On the Edit menu, click Modify.
  7. Do one of the following, depending on your situation:
    • To turn off IMAIL exception handling, in the Value data box, type 0.
    • To turn on IMAIL exception handling, in the Value data box, type 1.

      Note Exception handling is turned on if the ExceptionHandling registry entry is set a non-zero value or if the ExceptionHandling registry entry is not present.

Properties

Article ID: 832174 - Last Review: October 26, 2013 - Revision: 2.2
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Exchange 2000 Enterprise Server
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB832174

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com