locked
Service MSExchangeMailboxAssistants. Calendar Sync Assistant for database RRS feed

  • Question

  • Can someone help me with this incident?

     

    Message       : Service MSExchangeMailboxAssistants. Calendar Sync Assistant for database DB32 (ab1e0090-8aad-44cb-8e18-7a64de14df64) is exiting a work cycle. No mailboxes were successfully processed. 1 mailboxes were skipped due to errors. There are 0 mailboxes in this database.

    Saturday, July 9, 2011 6:58 PM

Answers

  • Hi Lis,

    Please check whether you got evnet 9042.

    Below are some description on your error message:

    Event 9042 can be misleading, because it is always be generated whenever a throttle-based assistant runs and there are no mailboxes configured for that assistant to process. It is not-uncommon for event 9042 to be generated and it is important to understand that the event does not indicate a problem unless mailboxes have been configured in a way where it is expected that the corresponding assistant should have processed the mailboxes.
    For example, mailboxes are not configured by default for Internet Calendar Subscriptions. A mailbox user must first subscribe to a desired Internet shared calendar using Outlook or Outlook Web App (OWA). Once a mailbox user has subscribed to an Internet Shared Calendar, the Calendar Sync Assistant, which is responsible for synchronizing internet calendar subscriptions from the source to the mailbox, recognizes the mailbox is so configured and then processes the mailbox accordingly. If no mailboxes in a given database are configured to use shared internet calendars, then Event 9042 is always generated for the Calendar Sync Assistant for that database.

    It is still important to understand that Event 9042 may be an indication of a problem, but additional investigation is required to determine if that is the case. Always consider if there are mailboxes that should have been processed by an assistant that generates an Event 9042.
    Look for string “There are <n> mailboxes in this database.” where <n> indicates the number of mailboxes the assistant found to process. If the number of mailboxes is 0 (zero) then no mailboxes were configured to be processed by the assistant. In this case Event 9042 can be safely ignored.
    However, if the number of mailboxes is anything other than 0, look for the string “<n> mailboxes were skipped due to errors.” where <n> indicates the number of mailboxes that were located in the database, but were skipped by the assistant. In this case, there are mailboxes that should have been processed, but were skipped because there was something wrong with the mailbox that prevented the assistant from processing. This should be investigated to determine why the mailbox is being skipped.

     

    Best Regards!

    • Marked as answer by Rowen-Xu Friday, July 22, 2011 7:43 AM
    Monday, July 11, 2011 5:39 AM

All replies

  • Looks normal to me unless you know something to be wrong with it.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Saturday, July 9, 2011 9:53 PM
  • Hi Lis,

    Please check whether you got evnet 9042.

    Below are some description on your error message:

    Event 9042 can be misleading, because it is always be generated whenever a throttle-based assistant runs and there are no mailboxes configured for that assistant to process. It is not-uncommon for event 9042 to be generated and it is important to understand that the event does not indicate a problem unless mailboxes have been configured in a way where it is expected that the corresponding assistant should have processed the mailboxes.
    For example, mailboxes are not configured by default for Internet Calendar Subscriptions. A mailbox user must first subscribe to a desired Internet shared calendar using Outlook or Outlook Web App (OWA). Once a mailbox user has subscribed to an Internet Shared Calendar, the Calendar Sync Assistant, which is responsible for synchronizing internet calendar subscriptions from the source to the mailbox, recognizes the mailbox is so configured and then processes the mailbox accordingly. If no mailboxes in a given database are configured to use shared internet calendars, then Event 9042 is always generated for the Calendar Sync Assistant for that database.

    It is still important to understand that Event 9042 may be an indication of a problem, but additional investigation is required to determine if that is the case. Always consider if there are mailboxes that should have been processed by an assistant that generates an Event 9042.
    Look for string “There are <n> mailboxes in this database.” where <n> indicates the number of mailboxes the assistant found to process. If the number of mailboxes is 0 (zero) then no mailboxes were configured to be processed by the assistant. In this case Event 9042 can be safely ignored.
    However, if the number of mailboxes is anything other than 0, look for the string “<n> mailboxes were skipped due to errors.” where <n> indicates the number of mailboxes that were located in the database, but were skipped by the assistant. In this case, there are mailboxes that should have been processed, but were skipped because there was something wrong with the mailbox that prevented the assistant from processing. This should be investigated to determine why the mailbox is being skipped.

     

    Best Regards!

    • Marked as answer by Rowen-Xu Friday, July 22, 2011 7:43 AM
    Monday, July 11, 2011 5:39 AM
  • Dienst MSExchangeMailboxAssistants. Postfach-Assistent für verwaltete Ordner für die Datenbank
    'Mailbox Database 1 (f5872c90-6f93-43ge-b181-d8f31f32e8a0)' beendet einen Arbeitszyklus.
    Es konnte kein Postfach erfolgreich verarbeitet werden.
    5 Postfächer wurden aufgrund von Fehlern übersprungen. In der Datenbank sind 1337 Postfächer vorhanden.

    watch out for 9025 events. it shows you the mailboxes that produce the problem. for repairing them, move them to another mailbox database.

    then restart microsoft mailbox assistant service on mailbox server, oof should work again then.

    Monday, December 10, 2012 3:41 PM
  • =================================================
    Log Name:      Application
    Source:        MSExchange Assistants
    Date:          30-03-2016 05:56:29
    Event ID:      9042
    Task Category: Assistants
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      AMAILY.silkeborg.local
    Description:
    Service MSExchangeMailboxAssistants. Calendar Sync Assistant for database Mailbox Database DBXX (2af74fc9-ff18-4702-bf4e-bb6de90d84bc) is exiting a work cycle. No mailboxes were successfully processed. 1 mailboxes were skipped due to errors. There are 0 mailboxes in this database.
    =================================================
    Log Name:      Application
    Source:        MSExchange Assistants
    Date:          30-03-2016 05:56:29
    Event ID:      9025
    Task Category: Assistants
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      AMAILY.silkeborg.local
    Description:
    Service MSExchangeMailboxAssistants. Calendar Sync Assistant skipped 1 mailboxes on database Mailbox Database DBXX (2af74fc9-ff18-4702-bf4e-bb6de90d84bc). Mailboxes:
    Fru Dahl(e3f90749-5243-4925-93bc-3330d79929f8)
    =================================================
    See:
    Remove-Mailbox: https - technet.microsoft.com/en-us/library/aa995948(v=exchg.141).aspx
    Use the Database and StoreMailboxIdentity parameters to remove a mailbox object from the Exchange database. In this case, the mailbox object has already been disconnected from the user. For example, if you run the Disable-Mailbox cmdlet, the Exchange mailbox object still exists, but is disconnected from the Active Directory user object. You can use the Database and StoreMailboxIdentity parameters to remove this disconnected mailbox object.
    See also EXAMPLE 3
    Remove-Mailbox -Database "Mailbox Database DBXX" -StoreMailboxIdentity "e3f90749-5243-4925-93bc-3330d79929f8" -Confirm:$true
    Wednesday, March 30, 2016 12:18 PM