locked
Event ID 1027 MSExchangeFDS.exe Offline Address List Error RRS feed

  • Question

  • Hello

    I'm hoping someone can assist with an error I'm receiving on one of our MBX/CAS/HT servers.

    The event logged in the Application Log is as follows:

    Source: MSExchangeFDS.exe

    Event ID: 1027

    Level: Error

    "Process MSExchangeFDS.exe (PID=2448). General errors occurred while synchronizing content from server MBX02 for object Default Offline Address List, giving up after 5 retries. Please check previous error events logged by MSExchangeFDS for more information. "

    The server reporting the issue (MBX04) used to be the OAB generation server, however I moved this function to MBX02.

    Synchronization only seems to be failing on the "Default Offline Address List" on this server, the company OAB seems to be synchronizing fine.

    All other servers are not reporting any issues, and all have diagnostic logging set to "High" for MSExchangeFDS.exe -"File Replication" and "General"

    Event ID 1008 is logged, suggesting that 1 offline address has been successfully synchronized.

    The permissions on the ExchangeOAB directory on MBX04 look the same as the other servers.

    Restarting the Exchange services has not rectified the issue either.

    Can anyone suggest the best troubleshooting steps to try and remedy this error?

    Regards

    Matt


    Matt

    Thursday, January 3, 2013 12:29 PM

Answers

  • OK, this issue is now solved.

    The problem was with a copy of one of the OAB's in the OAB virtual directory within IIS on the MBX04 server.

    Once the OAB was deleted from the directory, I ran the Update-FileDistributionService cmdlet to recreate the OAB.

    The event logs on that server now show that both OAB's were successfully synchronised.

    Regards


    Matt

    • Marked as answer by Matt_Pollock Monday, January 7, 2013 10:18 AM
    Monday, January 7, 2013 10:18 AM

All replies

  • Hi

    What is your exchange version?

    Please have a try with the solution on below thread

    http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/96c00ee1-0a71-4f3a-bdfc-0432596391c5/

    "All that was required was to set these three services to delayed start and then, presto, no more errors in the logs.....

    Microsoft Exchange Mailbox Replication

    Microsoft Exchange File Distribution

    Exchange Search Indexer"

    Hope it will help

    Cheers


    Zi Feng
    TechNet Community Support

    Friday, January 4, 2013 8:54 AM
  • Hello Zi,

    My version of Exchange is 2010 SP2 RU4 on all servers.

    I read the article you mentioned yesterday before posting this thread, and restarted the server as a result.

    The problem remained after a restart.

    I have not changed the three services mentioned from startup type "Automatic" to "Automatic (Delayed)" as the services are not set to "Automatic (Delayed)" on the other Exchange servers that are not experiencing the issue.

    I not sure what relevance the service startup type would have in this instance?

    Regards

    Matt


    Matt

    Friday, January 4, 2013 9:18 AM
  • Hi

    Do you have the Problem generating OAB on your Exchange 2010?

    Cheers


    Zi Feng
    TechNet Community Support

    Monday, January 7, 2013 7:35 AM
  • No, I don't believe there is an issue with the generation of either the default OAB, or the custom company OAB.

    Both have been generated successfully today at around 4 am on the generation server.

    "Event ID 9107 - 

    Offline address book generation finished."

    Event ID 1027 (as detailed in the original post) is still being logged on the server with the issue, for the Default Offline Address Book object.

    Reagrds

    Matt


    Matt

    Monday, January 7, 2013 9:20 AM
  • OK, this issue is now solved.

    The problem was with a copy of one of the OAB's in the OAB virtual directory within IIS on the MBX04 server.

    Once the OAB was deleted from the directory, I ran the Update-FileDistributionService cmdlet to recreate the OAB.

    The event logs on that server now show that both OAB's were successfully synchronised.

    Regards


    Matt

    • Marked as answer by Matt_Pollock Monday, January 7, 2013 10:18 AM
    Monday, January 7, 2013 10:18 AM