Hello,
we've currently got a rather odd problem with our Exchange 2010 Server (Sp3 RU8):
During business hours, the RPC Client Access Process (Microsoft.Exchange.RpcClientAccess.Service) hits 100% CPU load on the Exchange Server. No matter what we have tried, the problem has so far refused to go away.
Additional symptoms:
- The load is caused by few (3-5) Mailboxes at a given time
- The Mailboxes causing this vary each day, can hit any Mailbox with no pattern discernible
What we've tried so far without success:
- Stop/Rebuild Searchindex
- Move all Mailboxes, dropping bad items
- Move (sole) public folder database
- Migrate Public folder database
- Stop other client access methods (Active Sync)
- Ensure throttling is in place
- Ensure Public Folders are configured properly and that the current database is accepted as the default database
- Throw excessive hardware at it
- Build a new Exchange Server and move content over
- Rebuild Virtual Directories
- Maximized logging of all kind (logs say everything is great)
In the RPC Access logs, virtually all errors are generic as expected during daily operations:
AccessDenied, Collision, Object Changed, ...
The only clue I have left - but cannot find any information on - is this:
There is one kind of Operation that takes an incredible amount of time:
Disconnect
We have clients (All of them using Outlook 2010) that spend literally days disconnecting.
But what does that tell me? How can I dig deeper into this?
If that's not it: What else can I try?
Cheers and thanks in advance for any insights,
Fred
There's no place like 127.0.0.1