Microsoft.Exchange.RpcClientAccess.Service.exe process cause excessive CPU usage on Client Access servers in an Exchange Server 2010 environment

On Microsoft Support website you can find article about high CPU usage on Client Access Server.

 

CPU_usage

 

 

 

This issue can occur in following scenario:

  • You deploy some public folder databases in a Microsoft Exchange Server 2010 environment that has Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2 (SP2) or a later-version update rollup installed.
  • The environment contains multiple Active Directory sites.
  • The default public folder server is unavailable. So, the Microsoft Exchange RPC Client Access service tries to connect to other public folder servers.

 

In this scenario, the Microsoft.Exchange.RpcClientAccess.Service.exe process consumes excessive CPU resources on one or more Client Access servers in the site. Additionally, Microsoft Outlook clients cannot connect to Exchange servers, or they encounter slow performance when they connect to Exchange servers.

To resolve this issue, install the following update rollup:

2866475 Description of Update Rollup 2 for Exchange Server 2010 SP3

More information you can find here…

 

Exchange 2010 SP3 RU2 and Exchange 2010 SP2 RU7 released

Microsoft released Rollups for Exchange 2010 SP3 and Exchange 2010 SP2.

Exchange 2010 SP3 Rollup 2 can be downloaded here:

Update Rollup 2 For Exchange 2010 SP3 (KB2866475)

and list of changes can be found here:

KB2866475

After installation of this rolllup you will get Exchange system version 14.03.158.1

Following fixes are included in this release:

  • 2861118 W3wp.exe process for the MSExchangeSyncAppPool application pool crashes in an Exchange Server 2010 SP2 or SP3 environment
  • 2851419 Slow performance in some databases after Exchange Server 2010 is running continuously for at least 23 days
  • 2859596 Event ID 4999 when you use a disclaimer transport rule in an environment that has Update Rollup 1 for Exchange Server 2010 SP3 installed
  • 2873477 All messages are stamped by MRM if a deletion tag in a retention policy is configured in an Exchange Server 2010 environment
  • 2860037 iOS devices cannot synchronize mailboxes in an Exchange Server 2010 environment
  • 2854564 Messaging Records Management 2.0 policy can’t be applied in an Exchange Server 2010 environment

 

Also Microsoft released RU7 for Exchange 2010 SP2 which can be downloaded here:

Update Rollup 7 for Exchange Server 2010 Service Pack 2 (KB2874216)

Description of RU7 for Exchange 2010 SP2 can be found here:

KB2874216

After installation of this rolllup you will get Exchange system version 14.02.375.0

Exchange Support – only one year left

Those of you, who still use belows following system, should know that all of those products reach end of their  extended support window next year at April 8th 2014

Also Windows Server 2003 will reach end of support at April 14th 2015.

Make sure that you are able to migrate to a supported product prior to the support expiration date.  Security updates willnot be provided for products that are not supported.

 

 

Exchange 2010 SP2 Rollup 5-v2 installation error 80070643

 

If during installation of Rollup 5-v2 for Microsoft Exchange Server 2010 SP2 you receive error 80070643, it’s caused by WMF 3.0 (Windows Management Framework 3.0).

Windows Management Framework 3.0 is installed with following windows updates for Microsoft Windows 2008 or Windows 7  (KB2506146 and KB2506143)

So before installation of Rollup 5-v2 check and uninstall these KB2506146 and KB2506143 and WMF 3.0

 

Also remember to run installation of any Rollup with  elevated privileges Run as Administrator