Hello,

Our Exchange 2013 CU7 infrastructure is facing Outlook connection outage. We are using MAPI over HTTP protocol and most of the client are Outlook 2013 SP1.

After a lot investigation we found out that this issue is related to the OAB generation. It seems that OAB generation triggers stopping of all the service related to IIS. This result in an Outlook outage of minimum 5 minutes that is resolved by the MSExchangeMapiMailboxAppPool recycling.

Here is a non-exhaustive list of event during OAB generation:

1.  OAB generation start
   • Source: MSExchangeMailboxAssistants
   • Event ID: 17001
   • Task Category: OAB Generator Assistant
   • Generation of OAB "\OAB_XXX" started.
2. MAPI AddressBook service stops
   • Source: MSExchangeMapiAddressBookAppPool
   • Event ID: 2002
   • Task Category: General
   • Message: Stopping MSExchangeMapiAddressBookAppPool. Process ID 6632. Microsoft Exchange 15.00.1044.021.
3. Autodiscover service stops
   • Source: MSExchange Autodiscover
   • Event ID: 2002
   • Task Category: Web
   • Message: The Autodiscover service has stopped.
4. ECP Stops
   • Source: MSExchange Control Panel
   • Event ID: 2
   • Task Category: General
   • Message: The Exchange Control Panel stopped in AppDomain '/LM/W3SVC/2/ROOT/ecp-9-130811956943276553'.
5. MAPI AddressBook service restarts
   • Source: MSExchangeMapiAddressBookAppPool
   • Event ID: 2000
   • Task Category: General
   • Message: Starting MSExchangeMapiAddressBookAppPool. Process ID 6632. Microsoft Exchange 15.00.1044.021.
6. MAPI Mailbox AppPool generates errors
   • Source: ASP.NET 4.0.30319.0
   • Event ID: 1309
   • Task Category: Web Event
   • Message:   

  Application Virtual Path: /mapi/emsmdb

  Exception type: HttpException

  Exception message: RpcObjectSetType

  Application domain: /LM/W3SVC/2/ROOT/mapi/emsmdb-2-130812818329875041

7. OAB generation complete
   • Source: MSExchangeMailboxAssistants
   • Event ID: 17002
   • Task Category: OAB Generator Assistant
   • Message: Generation of OAB "\OAB_AmarisGroupMbx" completed.

Thanks for your help,

Etienne

For this kind of issue I recommend you open an incident with Microsoft Support.

Exchange 2013 CU9 has been out for about a month (release article here). Any chance you can try deploying it on the affected server ?

Hi,

I suggest you can try to update Cumulative Update 9 for the problematic Exchange 2013.

This update rollup is highly recommended for all Exchange Server 2013 customers.

Please download it in the below link:

http://www.microsoft.com/en-us/download/details.aspx?id=47679

Then check if the issue persists.

Regards,

David