locked
Exchange 2010 KHI Health Monitoring - Legacy MAPI error? RRS feed

  • Question

  • Hi All,

     

    We have migrated from Exc 2007 (which was unmonitored in SCOM) to Exc 2010 and switched our last Exchange 2007 box off. However we are now seeing a MAPI error on SCOM, which i cannot resolve:

     

    KHI: Transaction Failures Occured during MAPI connectivity Testing:

    Description: 

    Some of the MAPI connectivity transactions failed. Detailed information: Target: System mailbox for <exchange2010>\Public Folder Database Error: [Microsoft.Exchange.Data.Storage.MailboxUnavailableException]: Cannot open mailbox /o=<legacy object>/ou=New Exchange 2010 Administrative Group/cn=Configuration/cn=Servers/cn=<exchange2007server>/cn=Microsoft System Attendant. Inner error [Microsoft.Mapi.MapiExceptionUnknownUser]: MapiExceptionUnknownUser: Unable to make connection to the server. (hr=0x80004005, ec=1003) Diagnostic context: Lid: 47655 EMSMDBPOOL.EcPoolCreateSession called [length=377] Lid: 64039 EMSMDBPOOL.EcPoolCreateSession returned [ec=0x3EB][length=150][latency=0] Lid: 41073 StoreEc: 0x3EB Lid: 48243 Lid: 50033 StoreEc: 0x3EB Lid: 1494 ---- Remote Context Beg ---- Lid: 25805 Error: 0x0 Lid: 11752 StoreEc: 0x8004010F Lid: 19149 Error: 0x0 Lid: 25805 Error: 0x0 Lid: 11752 StoreEc: 0x8004010F Lid: 22787 Error: 0x0 Lid: 13800 StoreEc: 0x8004010F Lid: 9448 StoreEc: 0x8004010F Lid: 16454 Lid: 16966 StoreEc: 0x8004010F Lid: 32121 Lid: 20076 StoreEc: 0x3EB Lid: 57713 StoreEc: 0x3EB Lid: 49009 StoreEc: 0x3EB Lid: 1750 ---- Remote Context End ---- Lid: 52465 StoreEc: 0x3EB Lid: 60065 Lid: 33777 StoreEc: 0x3EB Lid: 59805 Lid: 52209 StoreEc: 0x3EB Lid: 56583 Lid: 52487 StoreEc: 0x3EB Lid: 19778 Lid: 27970 StoreEc: 0x3EB Lid: 17730 Lid: 25922 StoreEc: 0x3EB ------------------------------------- Diagnostic command: "Test-MAPIConnectivity -MonitoringContext:$true -PerConnectionTimeout:60 -AllConnectionsTimeout:90"

     I have located the Exchange 2010 Administrative Group in the AD config (via ADSI edit), but don't see any reference to <Exchange2007Server> - i presume this means that is correct and therefor there is a configuration error in exchange somewhere. I cannot locate this through the EMC. I have reset the alert, but it is persistant and returns. I also ran the "Test-MAPIConnectivity -MonitoringContext:$true -PerConnectionTimeout:60 -AllConnectionsTimeout:90" command from Exchange shell which returned no errors on each server.

     

    We are running Exchange 2010 SP1 (14.01.0289.001) on 2008 R2 SP1. SCOM is 2007 R2 CU4 with Exchange 2010 MP version 14.2.71.0

     

    I'm not a dedicated Exchange admin, so this is probably a simple fix for you guys? (I hope!)

     

    Any pointers appreciated!

     

    Ben

    Friday, November 25, 2011 9:35 AM

Answers

  • Hi,

    Please try to run ExBPA to have a health scan from Exchange 2010 and then post the error information here.

    Please verify if you have move the "Microsoft System Attendant" mailbox from Exchange 2007 to Exchange 2010 server.

    Please try to check the homeMDB on Microsoft System Attendant, you can follow the steps below:

    1) Open up adsiedit.msc
    2) Connect to the configuration context using the pdc/gc (it should be automatically selected for you when you choose the configuration context)
    3) Navigate to Services / Microsoft Exchange / Organisation Name / Administrative Groups / Administrative Group / Servers / Server Name / Microsoft System Attendant
    4) Right click on the "Microsoft System Attendant" object and choose properties
    5) Choose "HomeMDB" and click edit

    Note: It should be CN=<Exchange 2010 database>,CN=Database,CN=Exchange Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=COM


    6) If the value is not correct, then you can try to change it there.
    7) Click ok and exit adsiedit
    8) Restart the System Attendant service.

    Xiu

     

     

    • Marked as answer by Xiu Zhang Friday, December 9, 2011 9:13 AM
    Tuesday, November 29, 2011 6:34 AM

All replies

  • Hi,

    Please try to run ExBPA to have a health scan from Exchange 2010 and then post the error information here.

    Please verify if you have move the "Microsoft System Attendant" mailbox from Exchange 2007 to Exchange 2010 server.

    Please try to check the homeMDB on Microsoft System Attendant, you can follow the steps below:

    1) Open up adsiedit.msc
    2) Connect to the configuration context using the pdc/gc (it should be automatically selected for you when you choose the configuration context)
    3) Navigate to Services / Microsoft Exchange / Organisation Name / Administrative Groups / Administrative Group / Servers / Server Name / Microsoft System Attendant
    4) Right click on the "Microsoft System Attendant" object and choose properties
    5) Choose "HomeMDB" and click edit

    Note: It should be CN=<Exchange 2010 database>,CN=Database,CN=Exchange Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=COM


    6) If the value is not correct, then you can try to change it there.
    7) Click ok and exit adsiedit
    8) Restart the System Attendant service.

    Xiu

     

     

    • Marked as answer by Xiu Zhang Friday, December 9, 2011 9:13 AM
    Tuesday, November 29, 2011 6:34 AM
  • Hi Xiu,

    Thanks for the response - ExBPA revealed a few legacy issues we are working through, although they don't appear related to the MAPI errors. We are programming install of RU6 (or possibly SP2) on exchange infrastructure, and then a re-run of BPA, hence the slow reply.

    The HomeMDB was set correctly for all DB's BTW, so I suspect it is some issues picked up by BPA.

    Thanks for the advice, I will update further if this doesn't help.

    Ben

    Tuesday, December 13, 2011 9:56 AM