Traitée Public Folder email routing to incorrect database

  • Monday, May 21, 2012 4:25 AM
     
     

    Hi All,

    I have an issue with public folder mail routing. Basically what is happening is that I have two mailbox servers, SRV1 (hosting PFDB1) and SRV2 (hosting PFDB2). both host a replica of the same public folders, but for some reason even though the active databases are on SRV1 and the databases are configured to connect to PFDB1 public folder email is being delevered to PFDB2.

    The result of this is that users have to wait for PF replication to occur before they see the mail in their public folders. I know that Exchange is supposed to select a public folder database on it own server to route mail to but for some reason mine isnt.

    Has anyone come accross this issue before?

    thanks,

    mvz00

All Replies

  • Tuesday, May 22, 2012 9:09 AM
    Moderator
     
     

    Hello mvz00,

    For this issue, one workaround is go to change the replication time.

    Here is a related thread for you:

    Mail-enabled Public Folders whacky problem
    http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/165cedfe-7f00-4791-8644-ed593f5ff044

    If you want to know more about public folder mail routing, you can refer to this document:

    Internal Message Routing (Routing to Public Folder)
    http://technet.microsoft.com/en-us/library/bb232193.aspx#PF

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Evan Liu

    TechNet Community Support

  • Wednesday, May 23, 2012 2:37 AM
    Moderator
     
     

    Hi mvz00,

    Any updates on this issue?

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttngfb@microsoft.com 


    Evan Liu

    TechNet Community Support

  • Wednesday, May 23, 2012 2:55 AM
     
     

    Hi Evan,

    Thanks a lot for the response, however the reason I didnt want to change the replication interval is that in another Microsoft forum I saw that reccommendation, but they said that changing the replication interval to 1 minute would put a lot of extra load on the server and it might cause performance issues.

    Thanks,

    mvz00

  • Friday, May 25, 2012 2:48 PM
     
     
    I think you are confusing how email transport works for public folders. Just becaus your your mailbox sever1 DBs are pointed to the PFserver1 doesn't mean that emails to the PFs will always go to PFserver1. Email transport for PF uses serveral metrics to find the most appropriate PF server such as site, routing, age etc. If it is a tie such as your case it can choose any server.
    • If still a tie, the first server in the replica list returned by AD is chosen.

    http://blogs.technet.com/b/exchange/archive/2007/04/16/3401930.aspx


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

  • Monday, May 28, 2012 2:50 AM
    Moderator
     
     

    Hi mvz00,

    If you don't want to change the replication interval, you can follow this document to change Exchange Server select the public folder:

    Internal Message Routing (Selecting the Destination Public Folder Database)
    http://technet.microsoft.com/en-us/library/bb232193.aspx#PF

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttngfb@microsoft.com


    Evan Liu

    TechNet Community Support

  • Sunday, June 03, 2012 3:41 AM
    Moderator
     
     Answered

    Hi mvz00,

    Any updates on this issue?

    Thanks,

    Evan Liu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttngfb@microsoft.com


    Evan Liu

    TechNet Community Support

    • Marked As Answer by michael111222 Sunday, June 03, 2012 4:34 AM
    •  
  • Sunday, June 03, 2012 4:34 AM
     
     

    Hi Evan,

    I ended up running the .\AddReplicaToPFRecursive.ps1 script again against the first server, which I wanted mail to route to, this actually resolved the issue. It seems that mail started to route via the origional server again after running the command a second time.

    Regards,

    mvz00