none
MSExchange Management Application Event id 5000 RRS feed

  • Общие обсуждения

  • Коллеги очень нужна Ваша помощь

    После миграции на Exchange 2013 CU 10 и удаление Exchange  2010 стало засыпать ошибками Event ID: 5000
    не знаю что уже делать, у меня 4 сервера Exchange они в DAG

    Вот что я проверял

    [PS] C:\>Get-Mailbox -Identity DiscoverySearchMailbox*
    DiscoverySearchMailbox... DiscoverySearchMa... ala     50 GB (53,687,091,200 bytes)

    [PS] C:\>Get-Mailbox -Arbitration
    SystemMailbox{bb558c35... SystemMailbox{bb5... ala     Unlimited
    SystemMailbox{1f05a927... SystemMailbox{1f0... ala     Unlimited
    FederatedEmail.4c1f4d8... FederatedEmail.4c... ala     1 MB (1,048,576 bytes)
    Migration.8f3e7716-201... Migration.8f3e771... ala     300 MB (314,572,800 bytes)

    Log Name:      Application
    Source:        MSExchange Management Application
    Date:          5/31/2016 12:22:55 PM
    Event ID:      5000
    Task Category: AdminAuditLog
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ala.com
    Description:
    Failed to save admin audit log for this cmdlet invocation.
    Organization: First Organization
    Log content:
    Cmdlet Name: Update-Recipient
    Object Modified: Татьяна но он ругается на очень многих пользователей
    Parameter: DomainController = dc1.com
    Parameter: Identity = Татьяна
    ExternalAccess: False
    Succeeded: True
    Run Date: 2016-05-31T06:22:55
    OriginatingServer: ALA.com (15.00.1156.000)

    Error:
    Exception thrown during AdminLogProvisioningHandler.Validate: Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The discovery mailbox, a hidden default mailbox that is required to search mailboxes, can't be found. It may have been inadvertently deleted. This mailbox must be re-created before you can search mailboxes.
       at Microsoft.Exchange.Data.Storage.Infoworker.MailboxSearch.MailboxDataProvider.GetDiscoveryMailbox(IRecipientSession session)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.AdminAuditLogHelper.CheckArbitrationMailboxStatus(OrganizationId organizationId, ADUser& user, ExchangePrincipal& principal, Exception& exception)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Management Application" />
        <EventID Qualifiers="49152">5000</EventID>
        <Level>2</Level>
        <Task>5</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-05-31T06:22:55.000000000Z" />
        <EventRecordID>83479210</EventRecordID>
        <Channel>Application</Channel>
        <Computer>ala.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Cmdlet Name: Update-Recipient
    Object Modified: Татьяна
    Parameter: DomainController = dc1.com
    Parameter: Identity = Татьяна
    ExternalAccess: False
    Succeeded: True
    Run Date: 2016-05-31T06:22:55
    OriginatingServer: ALA (15.00.1156.000)
    </Data>
        <Data>First Organization</Data>
        <Data>Exception thrown during AdminLogProvisioningHandler.Validate: Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The discovery mailbox, a hidden default mailbox that is required to search mailboxes, can't be found. It may have been inadvertently deleted. This mailbox must be re-created before you can search mailboxes.
       at Microsoft.Exchange.Data.Storage.Infoworker.MailboxSearch.MailboxDataProvider.GetDiscoveryMailbox(IRecipientSession session)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.AdminAuditLogHelper.CheckArbitrationMailboxStatus(OrganizationId organizationId, ADUser&amp; user, ExchangePrincipal&amp; principal, Exception&amp; exception)</Data>
      </EventData>
    </Event>

     


Все ответы

  •    Здравствуйте,

    Почтовый ящик следует перемещать после установки и проверки Exchange 2013. Если вы не переместите этот системный  почтовый ящик в Exchange 2013, при сосуществовании Exchange 2010 и Exchange 2013 в организации Exchange возникнут такие проблемы.