Article ID: 2514574 - Last Review: July 28, 2011 - Revision: 6.0

The Exchange RPC Client Access service crashes in an Exchange Server 2010 environment

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You have a Microsoft Exchange Server 2010 server that has a public folder store installed in an Exchange organization.
You connect to the public folder store by using Outlook 2003.
You create a meeting request, and then you try to view the free/busy information.

In this scenario, the Microsoft Exchange RPC Client Access service on the Exchange server crashes. Therefore, users are disconnected from the server. Additionally, the following event is logged in the Application log:

Source: MSExchange Common
Date: <date & time>
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: <computer name>
Description:
Watson report about to be sent for process id: <ID>, with parameters: E12, <build type>, <application version>, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.CustomAvailabilityQuery.Query, System.NullReferenceException, <call stack hash>, < assembly version>.

Back to the top

CAUSE

This issue occurs because the Microsoft Exchange RPC Client Access service does not verify whether a variable is NULL before it accesses the variable.

Back to the top