question

bhupenderccna avatar image
0 Votes"
bhupenderccna asked bhupenderccna answered

RPC Operations/sec Outstanding Exchange Server 2019

We have added one new server into the existing production, OS 2019 Core, Exchange Server 2019. We have moved one of the databases DAG copy on this server and started to face performance issues and we check it via setting performance counter found that there is always a backlog RPC Operations/sec where on other servers its always on 0.

We moved back the DB to other servers and try to check the same with one DB which's having a single mailbox but again there is always RPC Operations/sec backlogs and which is increasing IS RPC latency so whoever client is connected to this CAS server started to face the slowness in accessing MAPI mailboxes.

We have checked all the Application and System Event logs but did not find anything related.

Server Hardware Configurations are below

HP ProLiant DL360p Gen8
Intel Xeon E5-2650L v2 @ 1.70GHz, 1701 Mhz, 10 Core(s), 20 Logical Processor(s)
Intel Xeon E5-2650L v2 @ 1.70GHz, 1696 Mhz, 10 Core(s), 20 Logical Processor(s)
Memory 128 GB
DISK Enterprise SSD (RAID 0)

windows-serveroffice-exchange-server-administrationwindows-server-2019office-exchange-server-dev
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @bhupenderccna
Welcome.
According to your description, seems the key of your issue is not Outlook desktop client. So I removed the Outlook tag here. Thanks for your understanding and support.

0 Votes 0 ·
YukiSun-MSFT avatar image
0 Votes"
YukiSun-MSFT answered YukiSun-MSFT commented

Hi @bhupenderccna,

From what I read, we usually check the status of both "RPC Operations/sec" and "RPC Requests" when troubleshooting slow RPC request processing issues. So you could check the RPC Requests performance counter as well and see how it goes.

  • If RPC Requests is steadily increasing while RPC Operations/sec remains fairly stable, this indicates that the server cannot handle the existing workload and it's suggested to verify hardware components or decrease the number of users on the server. (This doesn't seem to be applicable to your situation as your hardware configuration seems good enough and you have tried to leave a single mailbox on the server.)

  • If RPC Requests is steadily increasing but RPC Operations/sec steadily decreases, this indicates that the Exchange server is the source of the bottleneck. This kind of situation is generally caused by either a serious physical resource shortage (memory or disk) or a processing issue within the Information Store or an integrated component (antivirus, journaling, and so on).

Reference: Troubleshooting Slow RPC Request Processing Issues.

Furthermore, for current situation, if the users who report the performance issues are running Outlook in Online mode, it's recommended to switching to Cached mode instead which could potentially help improve the performance.


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @bhupenderccna,
Just checking in to see if above information was helpful. If you have any questions or need further help on this issue, please feel free to post back.


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

0 Votes 0 ·

Hey YukiSun, I am aware that how these RPC requests are co related however in our case what is the strange part that from hardware perspective everything seems in excess and RPC counters currently are this

RPC Client Access Counters


Client RPC Average Latency 1.98
RPC Operations/Sec 122
IS RPC Requests 0
User Count 98

We are using this server to handle the CAS request as of now and hosted with only one DB and one mailbox, still you see how strange thigs are. We have raised it to MS too but that's again taking so much of time in analyzing multiple things.






0 Votes 0 ·

Hi @bhupenderccna,

Thanks for posting back with current status of the issue. Considering that it has been raised to MS, personally I'd recommend just focusing on the ticket you opened as they have more resources and things like debugging tools to help troubleshoot. Should there is any result or update, it'd be appreciated if you can post back to share with us.


If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

0 Votes 0 ·

Hello YukiSun,

Sure, will share the same with everyone which may help in overcoming a lot of users who may are into similar situation.

Best Regards,
Bhupender Kumar

0 Votes 0 ·
Show more comments
bhupenderccna avatar image
0 Votes"
bhupenderccna answered

Unfortunately, It's still same and even after getting Exchange server Installed on new server where MS support did nothing but waste a lot of time. Anyone is having any clue why this RPC Operations/sec backlogs from the RPC CLIENT ACCESS COUNTERS is not stable on just one server we are adding in existing Exchange 2019 Production. This is creating huge issues :(

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.