Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

MAPI and Mailflow tests fail after applying SP1 for Exchange 2013 Standard

$
0
0

MAPI and Mailflow tests fail after applying SP1 for Exchange 2013 Standard

Originally installed Exchange 2013 Standard RTM, applied SU3 immediately.  After a few months, upgraded to SP1.  Found App log issues with Health mailboxes. 

 Found that there was no “Monitoring Mailboxes” OU.  From my understanding, this OU was not part of the original RTM release; however, it does exist in the SP1 version.  I re-ransetup /prepareAD from the SP1 installation which created the container and allowed the health mailboxes to be created. 

All Database copies appeared Healthy in the EAC, showing 0 bad copy count for all, mounted for all

Databases

But MAPI connectivity now fails from C1 to all databases.  Health check prior to SP1 had no MAPI Test failures or MailFlow test failures.  Now  I have failures of both for all servers.

server errors and warnings were detected.

  • KC-P-EX1 - MAPI tests failed.
  • KC-P-EX1 - Mail flow test failed.
  • KC-P-EX2 - MAPI tests failed.
  • KC-P-EX2 - Mail flow test failed.
  • KP-P-EX1 - MAPI tests failed.
  • KP-P-EX1 - Mail flow test failed.
  • KP-P-EX2 - MAPI tests failed.
  • KP-P-EX2 - Mail flow test failed.

Mail flow test: WARNING: Couldn’t perform the operation because a system mailbox isn’t available .  Same MAPI failure on all four servers

Application Log Errors:

1.

Log Name:      Application

Source:        MSExchange Mailbox Replication

Date:          3/28/2014 10:17:04 AM

Event ID:      1006

Task Category: Service

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      KP-P-EX1.kadmon.llc

Description:

The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.

Database: KPExecs

Error: Couldn't find system mailbox 'eaec6631-0d6f-47fa-a296-fecb28a23cf8' in Active Directory.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Mailbox Replication" />

    <EventID Qualifiers="32772">1006</EventID>

    <Level>3</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-28T14:17:04.000000000Z" />

    <EventRecordID>680598</EventRecordID>

    <Channel>Application</Channel>

    <Computer>KP-P-EX1.kadmon.llc</Computer>

    <Security />

  </System>

  <EventData>

    <Data>KPExecs</Data>

    <Data>Couldn't find system mailbox 'eaec6631-0d6f-47fa-a296-fecb28a23cf8' in Active Directory.</Data>

  </EventData>

</Event>

2.

Log Name:      Application

Source:        MSExchange Management Application

Date:          3/28/2014 10:16:07 AM

Event ID:      9001

Task Category: Migration

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      KP-P-EX1.kadmon.llc

Description:

Couldn't connect to the migration service at KP-P-EX1.kadmon.llc.  Error: "The RPC call failed with result 'MigrationPermanentError'."

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange Management Application" />

    <EventID Qualifiers="49152">9001</EventID>

    <Level>2</Level>

    <Task>9</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-03-28T14:16:07.000000000Z" />

    <EventRecordID>680593</EventRecordID>

    <Channel>Application</Channel>

    <Computer>KP-P-EX1.kadmon.llc</Computer>

    <Security />

  </System>

  <EventData>

    <Data>KP-P-EX1.kadmon.llc</Data>

    <Data>The RPC call failed with result 'MigrationPermanentError'.</Data>

  </EventData>

</Event>

I didn’t have these issues prior to SP1 so I have to assume that running setup /prepareAD from the SP1 install after application of SP1 caused a change to the migration mailbox

Found this solution:

support.microsoft.com/kb/2812509

To resolve this issue, follow these steps:

Start the Active Directory Users and Computers snap-in.

Click Users, and then verify that the following account does not exist:

Migration.8f3e7716-2011-43e4-96b1-aba62d229136

Note If this account exists in the Users container, go to step 4.

Run the following cmdlet:

setup /preparead/IAcceptExchangeServerLicenseTerms

Run the following cmdlets:

Enable-Mailbox -Arbitration -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136"

Set-Mailbox "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration –Management:$true

However, when I try to apply the fix, I get an error:

This task does not support recipients of this type. The specified recipient

kadmon.llc/Users/Migration.8f3e7716-2011-43e4-96b1-aba62d229136 is of type UserMailbox. Please make sure that this

recipient matches the required recipient type for this task.

    + CategoryInfo          : InvalidArgument: (kadmon.llc/User...b1-aba62d229136:RecipientIdParameter) [Enable-Mailbo

   x], RecipientTaskException

    + FullyQualifiedErrorId : [Server=KC-P-EX1,RequestId=48e4936f-27c4-43e5-91bd-d091587208d2,TimeStamp=3/28/2014 3:18

   :06 AM] [FailureCategory=Cmdlet-RecipientTaskException] A0A49849,Microsoft.Exchange.Management.RecipientTasks.Enab

  leMailbox


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>