CRush1682
asked on
Exchange 2010 server is logging throttling policy "over budget" events for RCA, Outlook emails hang in Outbox
I have a SBS2011 server with Exchange 2010 with a few users configured. I have one user who has about 5 Exchange mailboxes configured in Outlook 2010 as separate Exchange accounts, NOT as "open these additional mailboxes". This was done to keep the local .ost file(s) smaller. Normally performance is fine, however periodically during the work day the user experiences an issue which normally manifests itself in an outgoing email hanging in the Outbox for a period of 5-15 minutes. During this time other users do not experience issues. It seems that when this happens a MSExchange ADAccess event 2915 is logged saying the user has gone over budget for component RCA. I'm not sure if the throttling is causing the Outlook issue, or if there is an underlying issue causing the Outlook performance issues and the 2915 event is a symptom, not a cause. Any thoughts?
ASKER
More information:
Server is a Dell PowerEdge T110 with 32GB of RAM. Exchange database is on it's own physical drives. Antivirus is ESET Mail Security. No other errors occur around the 2915 event. All updates and services packs are installed.
Server is a Dell PowerEdge T110 with 32GB of RAM. Exchange database is on it's own physical drives. Antivirus is ESET Mail Security. No other errors occur around the 2915 event. All updates and services packs are installed.
ASKER
Here's another 2915 event:
Process Microsoft.Exchange.RpcClie ntAccess.S ervice.exe (PID=2088). User 'Sid~CONTOSO\User2~RCA~fal se' has gone over budget '175' times for component 'RCA' within a one minute period. Info: 'Policy:DefaultThrottlingP olicy_cbce 1f4f-569b- 4e67-a6de- e1108c9659 15, Parts:CAS:174;'. Threshold value: '100'.
Process Microsoft.Exchange.RpcClie
ASKER
Output when running "get-throttlingpolicy"
[PS] C:\Windows\system32>get-th rottlingpo licy
RunspaceId : e1db662c-22d9-4229-8b89-a6 a0597e28b6
IsDefault : True
AnonymousMaxConcurrency : 1
AnonymousPercentTimeInAD :
AnonymousPercentTimeInCAS :
AnonymousPercentTimeInMail boxRPC :
EASMaxConcurrency : 10
EASPercentTimeInAD :
EASPercentTimeInCAS :
EASPercentTimeInMailboxRPC :
EASMaxDevices : 10
EASMaxDeviceDeletesPerMont h :
EWSMaxConcurrency : 10
EWSPercentTimeInAD : 50
EWSPercentTimeInCAS : 90
EWSPercentTimeInMailboxRPC : 60
EWSMaxSubscriptions : 5000
EWSFastSearchTimeoutInSeco nds : 60
EWSFindCountLimit : 1000
IMAPMaxConcurrency :
IMAPPercentTimeInAD :
IMAPPercentTimeInCAS :
IMAPPercentTimeInMailboxRP C :
OWAMaxConcurrency : 5
OWAPercentTimeInAD : 30
OWAPercentTimeInCAS : 150
OWAPercentTimeInMailboxRPC : 150
POPMaxConcurrency : 20
[PS] C:\Windows\system32>get-th rottlingpo licy
RunspaceId : e1db662c-22d9-4229-8b89-a6 a0597e28b6
IsDefault : True
AnonymousMaxConcurrency : 1
AnonymousPercentTimeInAD :
AnonymousPercentTimeInCAS :
AnonymousPercentTimeInMail boxRPC :
EASMaxConcurrency : 10
EASPercentTimeInAD :
EASPercentTimeInCAS :
EASPercentTimeInMailboxRPC :
EASMaxDevices : 10
EASMaxDeviceDeletesPerMont h :
EWSMaxConcurrency : 10
EWSPercentTimeInAD : 50
EWSPercentTimeInCAS : 90
EWSPercentTimeInMailboxRPC : 60
EWSMaxSubscriptions : 5000
EWSFastSearchTimeoutInSeco nds : 60
EWSFindCountLimit : 1000
IMAPMaxConcurrency :
IMAPPercentTimeInAD :
IMAPPercentTimeInCAS :
IMAPPercentTimeInMailboxRP C :
OWAMaxConcurrency : 5
OWAPercentTimeInAD : 30
OWAPercentTimeInCAS : 150
OWAPercentTimeInMailboxRPC : 150
POPMaxConcurrency : 20
POPPercentTimeInAD :
POPPercentTimeInCAS :
POPPercentTimeInMailboxRPC :
PowerShellMaxConcurrency : 18
PowerShellMaxTenantConcurr ency :
PowerShellMaxCmdlets :
PowerShellMaxCmdletsTimePe riod :
ExchangeMaxCmdlets :
PowerShellMaxCmdletQueueDe pth :
PowerShellMaxDestructiveCm dlets :
PowerShellMaxDestructiveCm dletsTimeP eriod :
RCAMaxConcurrency : 20
RCAPercentTimeInAD : 5
RCAPercentTimeInCAS : 205
RCAPercentTimeInMailboxRPC : 200
CPAMaxConcurrency : 20
CPAPercentTimeInCAS : 205
CPAPercentTimeInMailboxRPC : 200
MessageRateLimit :
RecipientRateLimit :
ForwardeeLimit :
CPUStartPercent : 75
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : DefaultThrottlingPolicy_cb ce1f4f-569 b-4e67-a6d e-e1108c96 5915
DistinguishedName : CN=DefaultThrottlingPolicy _cbce1f4f- 569b-4e67- a6de-e1108 c965915,CN =Global S
ettings,CN=CONTOSO,CN=Micr osoft Exchange,CN=Services,CN=Co nfigurati
on,DC=CONTOSO,DC=local
Identity : DefaultThrottlingPolicy_cb ce1f4f-569 b-4e67-a6d e-e1108c96 5915
Guid : e714da30-2efc-464f-877b-1e 238e3a1d8d
ObjectCategory : CONTOSO.local/Configuratio n/Schema/m s-Exch-Thr ottling-Po licy
ObjectClass : {top, msExchGenericPolicy, msExchThrottlingPolicy}
WhenChanged : 8/13/2013 11:46:36 AM
WhenCreated : 8/13/2013 11:46:36 AM
WhenChangedUTC : 8/13/2013 3:46:36 PM
WhenCreatedUTC : 8/13/2013 3:46:36 PM
OrganizationId :
OriginatingServer : CONTOSO-SERVER.CONTOSO.loc al
IsValid : True
[PS] C:\Windows\system32>get-th
RunspaceId : e1db662c-22d9-4229-8b89-a6
IsDefault : True
AnonymousMaxConcurrency : 1
AnonymousPercentTimeInAD :
AnonymousPercentTimeInCAS :
AnonymousPercentTimeInMail
EASMaxConcurrency : 10
EASPercentTimeInAD :
EASPercentTimeInCAS :
EASPercentTimeInMailboxRPC
EASMaxDevices : 10
EASMaxDeviceDeletesPerMont
EWSMaxConcurrency : 10
EWSPercentTimeInAD : 50
EWSPercentTimeInCAS : 90
EWSPercentTimeInMailboxRPC
EWSMaxSubscriptions : 5000
EWSFastSearchTimeoutInSeco
EWSFindCountLimit : 1000
IMAPMaxConcurrency :
IMAPPercentTimeInAD :
IMAPPercentTimeInCAS :
IMAPPercentTimeInMailboxRP
OWAMaxConcurrency : 5
OWAPercentTimeInAD : 30
OWAPercentTimeInCAS : 150
OWAPercentTimeInMailboxRPC
POPMaxConcurrency : 20
[PS] C:\Windows\system32>get-th
RunspaceId : e1db662c-22d9-4229-8b89-a6
IsDefault : True
AnonymousMaxConcurrency : 1
AnonymousPercentTimeInAD :
AnonymousPercentTimeInCAS :
AnonymousPercentTimeInMail
EASMaxConcurrency : 10
EASPercentTimeInAD :
EASPercentTimeInCAS :
EASPercentTimeInMailboxRPC
EASMaxDevices : 10
EASMaxDeviceDeletesPerMont
EWSMaxConcurrency : 10
EWSPercentTimeInAD : 50
EWSPercentTimeInCAS : 90
EWSPercentTimeInMailboxRPC
EWSMaxSubscriptions : 5000
EWSFastSearchTimeoutInSeco
EWSFindCountLimit : 1000
IMAPMaxConcurrency :
IMAPPercentTimeInAD :
IMAPPercentTimeInCAS :
IMAPPercentTimeInMailboxRP
OWAMaxConcurrency : 5
OWAPercentTimeInAD : 30
OWAPercentTimeInCAS : 150
OWAPercentTimeInMailboxRPC
POPMaxConcurrency : 20
POPPercentTimeInAD :
POPPercentTimeInCAS :
POPPercentTimeInMailboxRPC
PowerShellMaxConcurrency : 18
PowerShellMaxTenantConcurr
PowerShellMaxCmdlets :
PowerShellMaxCmdletsTimePe
ExchangeMaxCmdlets :
PowerShellMaxCmdletQueueDe
PowerShellMaxDestructiveCm
PowerShellMaxDestructiveCm
RCAMaxConcurrency : 20
RCAPercentTimeInAD : 5
RCAPercentTimeInCAS : 205
RCAPercentTimeInMailboxRPC
CPAMaxConcurrency : 20
CPAPercentTimeInCAS : 205
CPAPercentTimeInMailboxRPC
MessageRateLimit :
RecipientRateLimit :
ForwardeeLimit :
CPUStartPercent : 75
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : DefaultThrottlingPolicy_cb
DistinguishedName : CN=DefaultThrottlingPolicy
ettings,CN=CONTOSO,CN=Micr
on,DC=CONTOSO,DC=local
Identity : DefaultThrottlingPolicy_cb
Guid : e714da30-2efc-464f-877b-1e
ObjectCategory : CONTOSO.local/Configuratio
ObjectClass : {top, msExchGenericPolicy, msExchThrottlingPolicy}
WhenChanged : 8/13/2013 11:46:36 AM
WhenCreated : 8/13/2013 11:46:36 AM
WhenChangedUTC : 8/13/2013 3:46:36 PM
WhenCreatedUTC : 8/13/2013 3:46:36 PM
OrganizationId :
OriginatingServer : CONTOSO-SERVER.CONTOSO.loc
IsValid : True
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Could this be explained by normal usage of Outlook with 5 different exchange mailboxes open, or should I be concerned that something else might be going on? Also is a 5-15 minute period of Outlook not updating be reasonable expectation when someone is being throttled?
What should I configure specifically in the new throttlingpolicy. I know that there are a few dozen parameters that can be throttled depending on the exact kind of communication, as per:
http://technet.microsoft.com/en-us/library/dd297964(v=exchg.141).aspx
Thanks in advance.
What should I configure specifically in the new throttlingpolicy. I know that there are a few dozen parameters that can be throttled depending on the exact kind of communication, as per:
http://technet.microsoft.com/en-us/library/dd297964(v=exchg.141).aspx
Thanks in advance.
Yes, I'd start by doubling the numbers, and applying that one to all his profiles.
ASKER
Update: No user problems reported after re-configuring the throttling policies so far. If no problems within 3 days I'll give you full credit for the fix!
If you could provide an updated output from get-throttlingpolicy, I'm sure that'll prove helpful for others.
ASKER
Right on!
ASKER
Process Microsoft.Exchange.RpcClie