Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Outlook clients experience slow performance, and multiple event ID 12002 errors are logged in the application log


View products that this article applies to.

Symptoms

Microsoft Outlook clients may experience slow performance, and multiple event ID 12002 errors are logged in the application log. The event errors are similar to the following event error:

Event Type: Error
Event Source: MSExchangeIS
Event Category: Content Engine
Event ID: 12002
Date: Date
Time: Time
User: N/A
Computer: Computer Name
Description:
Error 8000FFFF-80000000 occurred while processing message <> from 'Sender'.

↑ Back to the top


Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. 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
--------------------------------------------------------------
22-Oct-2003  07:21  6.0.6524.0      3,915,776  Cdoex.dll        
22-Oct-2003  07:16  6.0.6524.0        851,968  Davex.dll        
22-Oct-2003  07:16  6.0.6524.0         53,248  Davexpc.dll      
22-Oct-2003  07:12  6.0.6524.0        131,072  Drviis.dll       
22-Oct-2003  07:12  6.0.6524.0        577,536  Dsaccess.dll     
22-Oct-2003  06:22  6.0.6524.0        184,320  Dscmsg.dll       
22-Oct-2003  06:22  6.0.6524.0        962,560  Emsmdb32.dll     
22-Oct-2003  07:15  6.0.6524.0      2,179,072  Ese.dll          
22-Oct-2003  07:15  6.0.6524.0         40,960  Eseperf.dll      
09-Sep-2003  02:18                      6,991  Eseperf.hxx
22-Oct-2003  07:15                    391,634  Eseperf.ini
22-Oct-2003  07:21  6.0.6524.0      3,575,808  Excdo.dll        
22-Oct-2003  07:12  6.0.6524.0        262,144  Exmime.dll       
22-Oct-2003  07:16  6.0.6524.0        143,360  Exodbesh.dll     
22-Oct-2003  07:16  6.0.6524.0         57,344  Exodbpc.dll      
22-Oct-2003  07:16  6.0.6524.0        200,704  Exodbprx.dll     
22-Oct-2003  07:16  6.0.6524.0      2,179,072  Exoledb.dll      
22-Oct-2003  07:10  6.0.6524.0         81,920  Exosal.dll       
22-Oct-2003  07:16  6.0.6524.0        307,200  Exprox.dll       
22-Oct-2003  06:25  6.0.6524.0        143,360  Exschema.exe     
22-Oct-2003  07:15  6.0.6524.0        315,392  Exsmtp.dll       
22-Oct-2003  06:27  6.0.6524.0        675,840  Exwform.dll      
22-Oct-2003  07:13  6.0.6524.0         40,960  Jcb.dll          
22-Oct-2003  06:02  6.0.6524.0         49,152  Mdbevent.dll     
22-Oct-2003  06:19  6.0.6524.0      2,285,568  Mdbmsg.dll       
22-Oct-2003  06:04  6.0.6524.0         32,768  Mdbrole.dll      
22-Oct-2003  07:13  6.0.6524.0         24,576  Mdbtask.dll      
22-Oct-2003  07:09  6.0.6524.0         94,208  Peexch50.dll     
22-Oct-2003  07:10  6.0.6524.0        397,312  Phatcat.dll      
22-Oct-2003  07:13  6.0.6524.0        532,480  Reapi.dll        
22-Oct-2003  07:15  6.0.6524.0        311,296  Resvc.dll        
22-Oct-2003  07:11  6.0.6524.0      4,657,152  Store.exe        
22-Oct-2003  06:27  6.0.6524.0      3,735,552  Wmtemplates.dll
Note Because of file dependencies, this hotfix 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� XGEN: How to obtain the latest Exchange 2000 server service pack

↑ Back to the top


More information

If Exchange 2000 Server is running in a clustered configuration, you must stop the Cluster Service before you install the hotfix. If you do not stop the Cluster Service, you receive the following error message:
Setup has detected that Cluster Service is running on this computer. You must manually shut down the dependent resources using the Cluster Administrator and stop the Cluster Service before continuing. You must manually restart them when finished.

To install the hotfix on a clustered Exchange Server computer, follow these steps.

Note These steps assume that you have two nodes in your Exchange Cluster and that they are named Node A and Node B. Node A is the active node.
  1. Click Start, point to Programs, point to Administrative Tools, and then click Cluster Administrator.
  2. Pause Node B. To do this, right-click Node B in the left pane of Cluster Administrator, and then click Stop Cluster Service.
  3. Install the hotfix on Node B, and then restart the computer.
  4. When Node B is finished restart, restart the Cluster Service. To do this, right-click Node B in the left pane of Cluster Administrator, and then click Start Cluster Service.
  5. To install the hotfix on Node A, you must initiate a failover. To do this, right-click Node A in Cluster Administrator, and then click Initiate Failure.
  6. Repeat steps 2 through 4 for Node A.
  7. Quit Cluster Administrator.

↑ 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.

↑ Back to the top


Keywords: KB829047, kbbug, kbexchange2000presp4fix, kbqfe, kbfix, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 829047
Revision : 8
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 207