Outlook 2003 Performance issues with Exchange Server 2010 RTM
Dear Experts,
We recently migrated one of our customers to Exchange Server 2010 from Exchange Server 2003 SP2 and our customer is reporting slow response from Outlook when mailboxes are being accessed; the clients are all Outlook 2003 SP2 running in cached mode, the server is a multi-role Exchange 2010 box running Mailbox, Hub Transport and CAS roles.
I know the obvious suggestion would be to upgrade the clients to Outlook 2010 but our customer is not in a position to do so just yet so we have to find a solution to this issue if we can.
The detail in the server logs suggests the issue is something to do with the RPC Client access Service. I've provided an extract below:
>>
RpcDispatch: Client is being backed off -> Backend reported that it is too busy -> The process failed to get the correct properties. -> MapiExceptionRpcServerTooB
<<
Any help would be greatly appreciated.
Regards,
Mark
We recently migrated one of our customers to Exchange Server 2010 from Exchange Server 2003 SP2 and our customer is reporting slow response from Outlook when mailboxes are being accessed; the clients are all Outlook 2003 SP2 running in cached mode, the server is a multi-role Exchange 2010 box running Mailbox, Hub Transport and CAS roles.
I know the obvious suggestion would be to upgrade the clients to Outlook 2010 but our customer is not in a position to do so just yet so we have to find a solution to this issue if we can.
The detail in the server logs suggests the issue is something to do with the RPC Client access Service. I've provided an extract below:
>>
RpcDispatch: Client is being backed off -> Backend reported that it is too busy -> The process failed to get the correct properties. -> MapiExceptionRpcServerTooB
<<
Any help would be greatly appreciated.
Regards,
Mark
Busbar
looks like server is suffering from performance hit to me it is not a client side thing, what is the HW config and No. of users configured
yes, not a client side i mean too!
ASKER
My colleagues and I realize this is a server-side issue. However, this is NOT a HW issue; the server is well over speced for it's particular task in terms of processor, memory and i/o performance.
We have set a limit of twenty concurrent rpc client connections per user in the Default RPC Throttling policy on the server and are about to restart the RPC client access Service to see if this resolves the issue.
I will post an update in due course.
Regards,
Mark
We have set a limit of twenty concurrent rpc client connections per user in the Default RPC Throttling policy on the server and are about to restart the RPC client access Service to see if this resolves the issue.
I will post an update in due course.
Regards,
Mark
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.