none
Errors working with Databases. Microsoft.Mapi.MapiExceptionNoSupport: MapiExceptionNoSupport: Unable to open message store RRS feed

  • Question

  • I'm stucked in the middle of the cross-forest migration from Exchange 2013 to Exchange 2019.

    I've installed new domain (Feature level 2016) and 8 new physical servers running Windows server 2019 for installing Exchange 2019 cu1 on-top of them.

    I've prepared AD and Scheme, installed two of the servers, builded a DAG and briefly tested mail flow and migration (moverequest and migrationbatch). Then I've added two more exchange servers to organization and add them to DAG.

    After that i've started migration of first user batches. Everything went fine for 5 days and first 30% of our users was migrated to 6 new databases.

    Last Friday I've added four more exchange servers and add them to DAG. And there i've got into that issue: I can create new database, but can't create mailbox inside of it or move other mailbox (either cross-forest or local-forest) to that database.  Meanwhile all 6 databases created prior that issue are working. I can move users here, I can add new copies of those databases etc.

    On import or move requests I'm getting error:

    New-MoveRequest -TargetDatabase Testing -Identity temptest@domain.net
    Cannot open mailbox /o=DOMAIN/ou=Exchange Administrative Group
    (FYDIBOHFXXXXXXX)/cn=Configuration/cn=Servers/cn=EXCH-WAW-1/cn=Microsoft System Attendant. There is no support for
    this operation.
        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : [Server=EXCH-WAW-8,RequestId=6178828c-ea0e-4ffd-a026-25f4f708d58e,TimeStamp=4/26/2019 9:
       08:07 AM] [FailureCategory=Cmdlet-RemoteTransientException] E30A6C4A,Microsoft.Exchange.Management.Migration.Mailb
      oxReplication.MoveRequest.NewMoveRequest
        + PSComputerName        : exch-waw-8.domain.net

    And events in event log, one with id 2002 (10KB in toltal, how should I attach it?) and several 1006:
    <ommited>
    Database: Testing
    Error: MapiExceptionNoSupport: Unable to open message store. (hr=0x80040102, ec=-2147221246)
    <ommited>


    I've tried to run /preparead and /preparesheme again, I've made new DAG and move servers there. I've removed one of the server from DAG and make new database without copies. No luck.
    I've checked Arbitration mailboxes. All of them are present.

    I'm run out of ideas how to fix that issue and what have cause it.
    The only clue "cn=Microsoft System Attendant" isn't used by Exchange server since 2013...


    Friday, April 26, 2019 11:13 AM

All replies

  • Hi,

    >>but can't create mailbox inside of it or move other mailbox (either cross-forest or local-forest) to that database.

    What is the error when you try to create a new mailbox on this database?

    Do you try to new/move mailboxes from ECP?

    >>Error: MapiExceptionNoSupport: Unable to open message store. 

    About this error, I would suggest you try to restart "Microsoft Exchange Mailbox Replication" service first.

    Then use command below to check whether are all needed services  running:

    Test-ServiceHealth

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, April 29, 2019 2:50 AM
    Moderator
  • Thanks for your answer.


    >What is the error when you try to create a new mailbox on this database?
    Mailbox will be created in database, but user can't access it:

    A problem occurred while you were trying to use your mailbox. 
    X-ClientId: 37C37BB90BD443DFAF1D2A66CBB4D379
    request-id d9e98815-85bc-4f8a-b390-afffb579e9c5
    X-OWA-Error Microsoft.Exchange.Data.Storage.NoSupportException
    X-OWA-Version 15.2.330.5
    X-FEServer EXCH-WAW-1
    X-BEServer EXCH-WAW-8
    Date:4/29/2019 7:42:53 AM
    InnerException: Microsoft.Mapi.MapiExceptionNoSupport
    

    >Do you try to new/move mailboxes from ECP?

    A lot of times...


    >About this error, I would suggest you try to restart "Microsoft Exchange Mailbox Replication" service first.

    Tried that at first place. No luck.

    Test-ServiceHealth shows that everything fine for all 8 servers.

    I believe that something broken down in domain schema, but cannot figure what, why and when :(


    Monday, April 29, 2019 7:47 AM
  • So, do you mean mailboxes could be created on this database, however users cannot login OWA?

    Do you try to create a new database on this Exchange server, if it is the same phenomenon on this new created database, you can try to  recycle OWA application Pool on this Exchange server, then try to run IISReset in CMD.

    If this phenomenon is still exist, you can try to remove OWA virtual directory then recreate it.

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 1, 2019 7:29 AM
    Moderator
  • You seams doesn't description your issue clearly, so I confirm with you twice about whether mailbox could be create and which is the real situation:

    >> I can create new database, but can't create mailbox inside of it or move other mailbox 

    >>Mailbox will be created in database, but user can't access it

    Regards,

    Kyle Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, May 6, 2019 2:27 AM
    Moderator
  • Hi guys,

    I am with the same issue in E2k19. When I create a database in E2k19 and a mailbox in it it is not possible to open it thru Outlook on the Web nor OLK:

    - Moving mailbox to affected database (we created several databases with the same behavior):

    New-MoveRequest testems3 -TargetDatabase mbx-2gb-02
    Failed to communicate with the mailbox database. There is no support for this operation.
        + CategoryInfo          : ResourceUnavailable: (:) [New-MoveRequest], NoSupportException
        + FullyQualifiedErrorId : [Server=WIN-EXC003,RequestId=548ff0bf-4b6f-41f8-ad51-af1fa689e6e5,TimeStamp=02/05/2019 20:59:16] [FailureCategory=Cmdlet-NoSupportException] CD295808,Microsoft.Exchange.Management
       .Migration.MailboxReplication.MoveRequest.NewMoveRequest

        + PSComputerName        : win-exc003.teste.com.br

    IN Event Viewer, Replicaation:

    The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
    Database: MBX-2GB-02
    Error: MapiExceptionNoSupport: Unable to open message store. (hr=0x80040102, ec=-2147221246)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=149]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=486][latency=75]
        Lid: 52176   ClientVersion: 15.2.330.5
        Lid: 50032   ServerVersion: 15.2.330.6005
        Lid: 35180  
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x80040102
        Lid: 26937  
        Lid: 21921   StoreEc: 0x80040102
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 1238    Remote Context Overflow
        Lid: 46872   StoreEc: 0x80070005 PropTag: 0xE080014 
        Lid: 55098   StoreEc: 0x80070005
        Lid: 46872   StoreEc: 0x80070005 PropTag: 0x669B0014
        Lid: 55098   StoreEc: 0x80070005
        Lid: 59418   dwParam: 0x79
        Lid: 34842   dwParam: 0x79
        Lid: 59418   dwParam: 0x79
        Lid: 34842   dwParam: 0x79
        Lid: 59418   dwParam: 0x79
        Lid: 34842   dwParam: 0x79
        Lid: 59418   dwParam: 0x79
        Lid: 34842   dwParam: 0x79
        Lid: 59418   dwParam: 0x79
        Lid: 34842   dwParam: 0x79
        Lid: 44106   StoreEc: 0x80040102
        Lid: 56872   dwParam: 0xFE
        Lid: 42712   StoreEc: 0x80040102
        Lid: 45434   Guid: 763bd6e0-2b24-454f-9129-fd1a64464c72
        Lid: 10786   dwParam: 0x0        Msg: 15.02.0330.005:WIN-EXC003:114c3aee-b617-4b3b-b3b5-6091b150e3df
        Lid: 1750    ---- Remote Context End ----
        Lid: 27962   ROP: ropGetPropsSpecific [7]
        Lid: 26881  
        Lid: 21817   ROP Failure: 0x80040102
        Lid: 46042   StoreEc: 0x80040102
        Lid: 32441  
        Lid: 1706    StoreEc: 0x80040102
        Lid: 24761  
        Lid: 20665   StoreEc: 0x80040102
        Lid: 25785  

        Lid: 29881   StoreEc: 0x80040102

    In Outlook on the Web:

    :-(
    Something wrong.
    Occorred a problem while you tried to use the mailbox.
    X-ClientId: 200B7D16EA84442FAB1E8549AF9E9AFF
    request-id: cddd9ad4-b8ac-4486-8ec9-6045b0850add
    X-OWA-Error: Microsoft.Exchange.Data.Storage.NoSupportException
    X-OWA-Version: 15.2.330.5
    X-FEServer: SW010B120
    X-BEServer: WIN-EXC004
    Date: 02/05/2019 15:26:14
    InnerException: Microsoft.Mapi.MapiExceptionNoSupport

    Any clue, Kyle?

    Thanks in advance

    Monday, May 13, 2019 6:17 PM
  • Hi Microsoft,

    I'm running into the same issue with Ex2013 (CU21) and Ex2019 CU2. Note: We'll try to upgrade Ex2013 to CU23 to match the release date of ex2019.

    I verified the SystemAttendant mailboxes do exist and are mail enabled.

    What I found was the attribute homeMDB for the cn=Microsoft System Attendant is missing (I did create one using a DB that's working on 2019).

    Another odd scenario out of hundreds of users only a few moved to 2019 and are actually working using outlook, OWA not tested.

    test-mapiconnectivity reports errors:

    [Microsoft.Exchange.Data.Storage.NoSupportException]: Cannot open
                                                    mailbox /o=xxxxx/ou=Exchange Administrative Group
                                                    (xxxxxxxx)/cn=Configuration/cn=Servers/cn=xxxxx/cn=Microsoft
                                                    System Attendant. There is no support for this operation. Inner error
                                                    [Microsoft.Mapi.MapiExceptionNoSupport]: MapiExceptionNoSupport:
                                                    Unable to open message store. (hr=0x80040102, ec=-2147221246)
                                                    Diagnostic context:
                                                        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=180]
                                                        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned
                                                    [ec=0x0][length=486][latency=86]
                                                        Lid: 52176   ClientVersion: 15.2.397.3
                                                        Lid: 50032   ServerVersion: 15.2.397.6003
                                                        Lid: 35180
                                                        Lid: 23226   --- ROP Parse Start ---
                                                        Lid: 27962   ROP: ropLogon [254]
                                                        Lid: 17082   ROP Error: 0x80040102
                                                        Lid: 26937
                                                        Lid: 21921   StoreEc: 0x80040102
                                                        Lid: 27962   ROP: ropExtendedError [250]
                                                        Lid: 1494    ---- Remote Context Beg ----
                                                        Lid: 1238    Remote Context Overflow
                                                        Lid: 46872   StoreEc: 0x80070005 PropTag: 0xE080014
                                                        Lid: 55098   StoreEc: 0x80070005
                                                        Lid: 46872   StoreEc: 0x80070005 PropTag: 0x669B0014
                                                        Lid: 55098   StoreEc: 0x80070005
                                                        Lid: 59418   dwParam: 0x79
                                                        Lid: 34842   dwParam: 0x79
                                                        Lid: 59418   dwParam: 0x79
                                                        Lid: 34842   dwParam: 0x79
                                                        Lid: 59418   dwParam: 0x79
                                                        Lid: 34842   dwParam: 0x79
                                                        Lid: 59418   dwParam: 0x79
                                                        Lid: 34842   dwParam: 0x79
                                                        Lid: 59418   dwParam: 0x79
                                                        Lid: 34842   dwParam: 0x79
                                                        Lid: 44106   StoreEc: 0x80040102
                                                        Lid: 56872   dwParam: 0xFE
                                                        Lid: 42712   StoreEc: 0x80040102
                                                        Lid: 45434   Guid: 5589061b-5b26-478b-9c67-fafdc02de74f
                                                        Lid: 10786   dwParam: 0x0        Msg:
                                                    15.02.0397.003:Iron:d100bcc0-9490-4b47-9976-c3cb67995bb5
                                                        Lid: 1750    ---- Remote Context End ----
                                                        Lid: 27962   ROP: ropGetPropsSpecific [7]
                                                        Lid: 26881
                                                        Lid: 21817   ROP Failure: 0x80040102
                                                        Lid: 46042   StoreEc: 0x80040102
                                                        Lid: 32441
                                                        Lid: 1706    StoreEc: 0x80040102
                                                        Lid: 24761
                                                        Lid: 20665   StoreEc: 0x80040102
                                                        Lid: 25785
                                                        Lid: 29881   StoreEc: 0x80040102

    Thanks,

    Jakub

    Thursday, July 11, 2019 8:05 PM
  • I am also experiencing the same exact thing with same exact versions.

    Jakub, Have you upgraded to CU23 yet and if so, has it resolved the issue?

    Thanks,

    Micah


    • Edited by MicahHow Wednesday, September 4, 2019 12:40 PM
    Wednesday, September 4, 2019 12:39 PM
  • Hi Micah,

    If there is an Antivirus installed so uninstall it.

    Thanks.

    Luiz Felipe

    Wednesday, September 4, 2019 3:43 PM
  • Hello Luiz,

    At this point, the only AV that would be enabled would be Microsoft's Windows Defender protection on Windows Server.  I can try disabling to see if that nets any positive results.

    Thanks,

    Micah

    Wednesday, September 4, 2019 9:07 PM
  • Luiz,

    I added the Microsoft recommended exceptions via the script created at the following location:

    https://gallery.technet.microsoft.com/office/Add-Exchange-exclusions-to-c6726c67

    This did not resolve the issue.

    Micah

    Friday, September 6, 2019 2:00 PM
  • Hi Micah,,

    can you create a new mailbox in one of MX server?

    Both EAC and EMS?

    Luiz

    Friday, September 6, 2019 5:39 PM
  • Hi Luiz,

    Yes, I am able to create a new mailbox within the DB on the 2019 MBX server(s) using both methods EAC and EMS.  The user however cannot access them after they are created.  I am receiving the same error as other users stated above (cannot open system attendant mailbox).  I am wondering if this has something to do with the arbitration mailboxes that have existed for some time.  Maybe deleting and recreating the migration arbitration mailbox might resolve the issue?

    Micah


    Friday, September 6, 2019 6:05 PM
  • Hi Micah,

    in Event Viewer you see any relevant information?

    Can you open the mailbox in Outlook on the Web/OWApp?

    Recreating Arbitration Mailbox:

    https://docs.microsoft.com/pt-br/exchange/architecture/mailbox-servers/recreate-arbitration-mailboxes?view=exchserver-2019

    Luiz

    Wednesday, September 11, 2019 12:28 PM
  • Hi Luiz,

    Thank you for the suggestion.  I was actually able to figure it out this morning.  I'll do my best to explain it.

    The long of the short of it was that the MAPIoverHTTP wasn't enabled at the Organizational level.  We weren't ready to enable that for the entire company and wanted to enable it groups of mailboxes at a time for a more controlled experience.

    What led us to this answer was reviewing the mapihttp log on the Exchange server.  There were several messages related to RPC access failures and of course not being able to access the Microsoft System Attendant mailbox.  We enabled the MAPIoverHTTP setting for the organization which alone did not resolve the issue.  We had to recreate the mailbox database.  At this point, Test-MAPIConnectivity succeeded and we then deleted and re-created the migration arbitration mailbox (it had been recreated on an Ex19 mailbox database while troubleshooting).  At this point everything is functioning as expected including mailbox migrations.

    Unbeknownst to us, enabling MAPIoverHTTP at the organizational level is huge to getting Exchange 2019 to function properly although we are very aware of Exchange 2019 heavily relying on MAPIoverHTTP vs RPCoverHTTP.  Just a note to ensure that all Outlook clients support MAPIoverHTTP before making this change org wide.  Hopefully this helps someone else having similar issues.

    Best,

    Micah
    • Proposed as answer by MicahHow Wednesday, September 11, 2019 3:13 PM
    Wednesday, September 11, 2019 3:13 PM
  • Cannot thank you enough!
    Sunday, September 15, 2019 1:02 AM