Facing mail delivery issue.

Noyon Chandra Das 341 Reputation points
2025-09-10T05:44:09.9866667+00:00

Dear Team,

We are facing issues in the Exchange Server queue viewer while Databases are unkhown. After few times the issue has been solved automatically.

Attached screenshot for your reference.

1

2

3

Regards

Noyon

Exchange | Hybrid management
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Hin-V 4,340 Reputation points Microsoft External Staff Moderator
    2025-09-10T06:54:34.82+00:00

    Hi @Noyon Chandra Das

    Thank you for posting your question in Microsoft Q&A. 

    From my perspective, this issue might be a temporary disruption related to DAG replication, Active Directory, or the Transport Service, causing the Public Folder database status to show as Unknown and the queue to enter a Retry state. Once the system stabilizes, the status typically returns to Mounted, and the queue is automatically released. 

    This could be due to several possible causes: 

    1. Replication/Communication Issue within DAG:

    Since Exchange operates in a DAG, there may have been a temporary network or replication issue between nodes.  If the Public Folder database copy on the active node becomes disconnected or enters a ServiceDown state, Exchange may report the database as Unknown, and related queues may become congested. 

    2. Resource/Performance Bottlenecks:

    If the server experiences a temporary shortage of resources (CPU, memory, or I/O), database mounting or replication may slow down, causing the Exchange Admin Center (EAC) to report the database as Unknown.  Once resources stabilize, the database status typically returns to Mounted, and the queue is cleared. 

    3. Transport Service Disruption 

    If the Microsoft Exchange Transport Service or Microsoft Exchange Replication Service is overloaded or temporarily restarted, it can cause the Public Folder queue to enter a Retry state. 

    4. Temporary AD or Cluster Issues 

    Exchange relies heavily on Active Directory and cluster quorum. A brief interruption in AD replication or cluster witness availability may cause the database status to show as Unknown, which usually resolves itself once synchronization resumes. 

    You could try to use this command to get more detail: 

    Get-Queue | Format-List 
    

    Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution.


    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. 

    Accept answer 1 answer


Your answer

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