Share via

Exchange Server SE is throwing RPC errors

Jeyakumar Durai 0 Reputation points
2025-07-31T01:40:47.07+00:00

We have 8 Exchange 2016 servers running smoothly. We installed 8 Exchange server SE versions lately to move mailboxes from 2016 to SE and eventually decommission 2016 environment.

After installing the SE servers, the ECP is throwing several issues/errors when trying to manage from SE server.

  1. The default Database status hosted on all other 7 SE servers are showing as "Unknown"
  2. if try to access the virtual directory of other SE servers, getting RPC errors.
  3. If try to access the Certificates hosted on other SE servers, getting RPC errors.

4.unable to move the system mailboxes back to exchange 2016.ECP-VirtualDirectory.png

All these SE servers are on the same VLAN, no firewall in between. Please help.

Exchange | Exchange Server | Other
Exchange | Exchange Server | Other

A robust email, calendaring, and collaboration platform developed by Microsoft, designed for enterprise-level communication and data management.Miscellaneous topics that do not fit into specific categories.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jeyakumar Durai 0 Reputation points
    2025-08-04T14:10:11.8766667+00:00

    Raised case with Microsoft support. Based on their response, The Exchange SE version is having these kind of bugs and customers are reporting these issues to the Microsoft. We are in the process of rolling back to Exchange 2019.

    Was this answer helpful?

  2. Vergil-V 13,380 Reputation points Microsoft External Staff Moderator
    2025-07-31T09:57:28.3366667+00:00

    Hi @Jeyakumar Durai 
    Thank you for reaching out to Microsoft Learn Q&A! 
    I understand how frustrating and inconvenient it can be when your Exchange Server SE status shows as "Unknown" and you're encountering RPC errors while accessing the virtual directory and certificates after upgrading from Exchange Server 2016. 

    As a forum moderator, I want to acknowledge that we don’t have a dedicated testing environment to replicate every user-specific scenario. However, within the scope of our support, I’d like to offer some common troubleshooting steps that may help resolve this issue: 

    +Restart Exchange Services or Server 
    After an upgrade, it's recommended to restart the Exchange Server or at least the Exchange-related services. If you haven’t done this yet, please consider restarting and then checking the status of all services related to "Microsoft Exchange." 

    +Use Event Viewer for diagnostics 
    Event Viewer is a valuable tool for diagnosing issues. It can help identify specific errors or warnings that may be contributing to the RPC issue or the "Unknown" status. 

    These steps are based on the resources currently available to me and may help move things forward. If you have any updates or additional details, please don’t hesitate to share them. It will help us refine our support and possibly identify a more targeted solution. 

    Thank you again for your understanding and patience. 

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".         

    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 

    Was this answer helpful?

  3. Jeyakumar Durai 0 Reputation points
    2025-07-31T01:41:09.5966667+00:00

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.