The Exchange RPC Client Access service crashes when you send an email message in an Exchange Server 2010 environment

Article ID: 2599663 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

Assume that you use a MAPI client such as Outlook 2003 in online mode in a Microsoft Exchange Server 2010 environment. When you send an email message, the Microsoft Exchange RPC Client Access service might crash on the Exchange Server 2010 Client Access server. Additionally, the following log is logged in the Application log:

Log Name: Application
Source: MSExchange Common
Date: Date
Event ID: 4999
Task Category: General
Level: Error
Keyword: Classic
User: N/A
Computer: Computer
Explanation:Watson report about to be sent for process id:Process ID, with parameters: E12, Build Type, Version Type,M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Parser, M.E.R.P.RecipientRow..ctor, System.ArgumentException, XXXX, Version Number, ErrorReportingEnabled: False

Note When the issue occurs, Outlook users in the domain are disconnected from the Exchange server.

CAUSE

This issue occurs because the RPC Client Access service does not validate the recipient data before the service processes the data.  Therefore, when the recipient data that is stored in an invalid format is processed, a System.ArgumentException exception occurs, and then the service crashes.

RESOLUTION

To resolve this issue, install the following update rollup:
2645995 Description of Update Rollup 1 for Exchange Server 2010 Service Pack 2

Properties

Article ID: 2599663 - Last Review: February 13, 2012 - Revision: 1.0
APPLIES TO
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2010 Service Pack 2
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseinter KB2599663

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