Microsoft System Attendant on the Exchange 2019

Question

Microsoft System Attendant on the Exchange 2019

Viktor 1

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

Before migration we have Exchange 2013 CU23 with DAG.
And installed six servers Exchange 2019 CU7, create DAG, switch access points to a new servers.

Then create new database on 2019 server, and move arbitration mailboxes to it.
Then move some mailboxes from 2013 to 2019.
All works fine for a several days.

Test-ServiceHealth - OK
Get-MailboxDatabaseCopyStatus - OK
Server restarted - no effect.
All arbitration mailboxes present, placed in old Exchange 2019 database (Test-MapiConnectivity to this old database is OK).

But now problem is: I can create new databases on 2019, and I can create new mailboxes in the new databases, but I can't access to this mailboxes, and it not receiving emails.

In the Application EventLog have warnings:
MSExchange Mailbox Replication 1006:
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: DAG_DB2
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=494][latency=49]
Lid: 52176 ClientVersion: 15.2.721.2
Lid: 50032 ServerVersion: 15.2.721.6002
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: 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: 980645aa-5d54-434b-98df-49a5cd728669
Lid: 10786 dwParam: 0x0 Msg: 15.02.0721.002:ExchSrv2:e43c253f-8d00-4126-bed8-7c9a14db7de6
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

[PS] C:\>Test-MAPIConnectivity -Database DAG_DB2 -Verbose |fl Error

Error : [Microsoft.Exchange.Data.Storage.NoSupportException]: Cannot open mailbox /o=MyOrg/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/c
n=Servers/cn=ExchSrv2/cn=Microsoft System Attendant. There is no support for this operation. Inner error [Microsoft.Mapi.MapiExceptionNoSupport]: M
apiExceptionNoSupport: 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=494][latency=40]
Lid: 52176 ClientVersion: 15.2.721.2
Lid: 50032 ServerVersion: 15.2.721.6002
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: 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: 668ee38d-5b39-4664-9948-f2384aaffbd0
Lid: 10786 dwParam: 0x0 Msg: 15.02.0721.002:ExchSrv2:ae9f69e6-f095-46ef-b05b-803a52d08c57
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

OWA access for a new user on the new database failed:

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.721.2
X-FEServer EXCHSRV1
X-BEServer EXCHSRV2
Date:4/29/2019 7:42:53 AM
InnerException: Microsoft.Mapi.MapiExceptionNoSupport

This errors affecting ONLY a new databases, old databases on the 2013/2019 versions are working fine.

By googling Internet, I found than th Exchange 2019 is not using SYstem Attendant Service, and no need to check homeDB/homeMTA attributes (and this attributes is not set).

Why it's happened and how to fix it?

Viktor 1 Reputation point

2020-12-24T11:45:18.117+00:00

Found, that problem affect only Exch2019 servers.
Exch2013 servers isn't affected.
And this problem is not in the database inside (detached DB from failed Exch2019 organization was successfully mounted on the test lab servers, not in same organization).
Eric Yin-MSFT 4,396 Reputation points

2020-12-25T08:42:14.89+00:00

in second organization, does it also fail on Ex2019 with same error?
As a workround, you can export those users into pst and import the pst files in Ex2019 server.
Viktor 1 Reputation point

2020-12-25T09:11:28.58+00:00

Not second.
We have one PROD Exchange Organization with Exch2013/2019 servers inside (coexistent config, migration from 2013 to 2019).
And we have similar test lab (independant Exchange Organization)
Test lab working fine, with no errors.
Errors exists only on PROD organization.

So... Migration by export/import .pst files will be a big trouble. Prod Organization is too big for this.
Eric Yin-MSFT 4,396 Reputation points

2021-01-04T01:40:32.563+00:00

You can try to start a mailbox repair on the PROD server:https://learn.microsoft.com/en-us/powershell/module/exchange/new-mailboxrepairrequest?view=exchange-ps
Does the database show correct in eseuti /r?
Eric Yin-MSFT 4,396 Reputation points

2021-01-08T09:37:51.193+00:00

I am writing here to confirm with you how the thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Viktor 1

[PS] C:\Windows\system32>New-MailboxRepairRequest -Database DAG_DB2 -CorruptionType ProvisionedFolder, SearchFolder, AggregateCounts, Folderview
WARNING: The user hasn't logged on to mailbox '00000000-0000-0000-0000-000000000000' ('DAG_DB2'), so there is no data to return. After the user logs on, this warning will no longer appear.
[PS] C:\Windows\system32>Get-MailboxRepairRequest -Database DAG_DB2
[PS] C:\Windows\system32>

Алексей Муравлев 6 Reputation points

2021-02-01T15:23:20.493+00:00

We have the same problem..
Viktor 1 Reputation point

2021-02-01T15:35:03.223+00:00
Hi!

Try to run:

Update-DatabaseSchema "failed_DB_Name"

Then unmount and mount this DB again.
Алексей Муравлев 6 Reputation points

2021-02-01T17:53:11.61+00:00

Unfortunately this did not solve the problem.

Were you able to fix it?

Unfortunately this did not solve the problem.

Were you able to fix it?

Unfortunately this did not solve the problem.

Were you able to fix it?

Unfortunately, this command did not solve the problem. Were you able to fix it?
Алексей Муравлев 6 Reputation points

2021-02-01T17:55:18.457+00:00

Unfortunately, this command did not solve the problem. Were you able to fix it?
Viktor 1 Reputation point

2021-02-01T18:10:47.323+00:00
You must remount database after that command. It's important.
And yes, my problem is fixed by that way.
For test, you can run:

Get-MailboxDatabaseCopyStatus "failed_DB_Name" |fl *guid*,*schema*

If you see something like this:

MinimumSupportedDatabaseSchemaVersion : 0.121 MaximumSupportedDatabaseSchemaVersion : 0.185 RequestedDatabaseSchemaVersion : 0.121

A problem in RequestedDatabaseSchemaVersion
On the correct database it must be 0.185

After Update-DatabaseSchema and remount it should be 0.185

And...
I did it on the database with only one copy (right after create first copy). Not sure, but that might be important too.
Алексей Муравлев 6 Reputation points

2021-02-01T19:12:19.12+00:00

[PS] C:\Windows\system32>Test-MAPIConnectivity -Database "Mailbox Database 1705233893"

MailboxServer Database Result Error

WIN-ST-MBX-02 Mailbox Database 1 Success
705233893

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus "Mailbox Database 1705233893" | fl guid,schema

MinimumSupportedDatabaseSchemaVersion : 0.121
MaximumSupportedDatabaseSchemaVersion : 0.185
RequestedDatabaseSchemaVersion : 0.121

[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus "Exchange Database 11" | fl guid,schema

MinimumSupportedDatabaseSchemaVersion : 0.121
MaximumSupportedDatabaseSchemaVersion : 0.185
RequestedDatabaseSchemaVersion : 0.121

[PS] C:\Windows\system32>Test-MAPIConnectivity -Database "Exchange Database 11"

MailboxServer Database Result Error

WIN-ST-MBX-02 Exchange Database FAILURE [Microsoft.Exchange.Data.Storage.NoSupportException]: Cannot open mailb
11 ox /o=First Hosted Organization/ou=Exchange Administrative Group (FYDIB
OHF23SPDLT)/cn=Configuration/cn=Servers/cn=WIN-ST-MBX-02/cn=Microsoft S
ystem Attendant. There is no support for this operation. Inner error [M
icrosoft.Mapi.MapiExceptionNoSupport]: MapiExceptionNoSupport: Unable t
o open message store. (hr=0x80040102, ec=-2147221246)
Diagnostic context:
Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=180]
Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length
=494][latency=115]
Lid: 52176 ClientVersion: 15.2.721.2
Lid: 50032 ServerVersion: 15.2.792.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: 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: 230f2a35-15fa-4636-b458-e114d217589a
Lid: 10786 dwParam: 0x0 Msg: 15.02.0792.003:WIN-ST-MBX-02:
1034bff9-1497-4751-ae5c-fe4efe67da89
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
Алексей Муравлев 6 Reputation points

2021-02-01T19:16:53.703+00:00

Version of the database Exchange Database 11 is correct, but Test-MapiConnectivity is failed. Any other thoughts?

Thanks in advance.
Viktor 1 Reputation point

2021-02-01T19:45:16.833+00:00
No, DB Schema version for "Exchange Database 11" is not correct too.
You have:
RequestedDatabaseSchemaVersion : 0.121

Correct version is 0.185.

And I remember, we change in BIOS:

Hyper-Threading -> disabled

NUMA Group Size Optimization -> flat

And upgraded to Exch19_CU8 (currently max actual version), by MS SupportPro request, before Update-DatabaseSchema.

That's all.

By the way, we created a new DAG, and moved servers from old DAG to a new DAG, but it's not helped, so I think, it's not so important.
Timothy C. Good 0 Reputation points

2025-05-23T20:41:48.9333333+00:00

I think if found the issues. The database schema is a at a mis match.
Get-MailboxDatabaseCopyStatus "Exchange Database 11" | fl guid,schema

MinimumSupportedDatabaseSchemaVersion : 0.121

MaximumSupportedDatabaseSchemaVersion : 0.185

RequestedDatabaseSchemaVersion : 0.121

Run the following:

Update-DatabaseSchema DB01

Dismount-Database DB01

Mount-Database DB01

https://learn.microsoft.com/en-us/exchange/troubleshoot/migration/cannot-access-move-mailbox

4 answers

Your answer

Viktor 1 Reputation point

2020-12-24T11:45:18.117+00:00

Found, that problem affect only Exch2019 servers.
Exch2013 servers isn't affected.
And this problem is not in the database inside (detached DB from failed Exch2019 organization was successfully mounted on the test lab servers, not in same organization).
Eric Yin-MSFT 4,396 Reputation points

2020-12-25T08:42:14.89+00:00

in second organization, does it also fail on Ex2019 with same error?
As a workround, you can export those users into pst and import the pst files in Ex2019 server.
Viktor 1 Reputation point

2020-12-25T09:11:28.58+00:00

Not second.
We have one PROD Exchange Organization with Exch2013/2019 servers inside (coexistent config, migration from 2013 to 2019).
And we have similar test lab (independant Exchange Organization)
Test lab working fine, with no errors.
Errors exists only on PROD organization.

So... Migration by export/import .pst files will be a big trouble. Prod Organization is too big for this.
Eric Yin-MSFT 4,396 Reputation points

2021-01-04T01:40:32.563+00:00

You can try to start a mailbox repair on the PROD server:https://learn.microsoft.com/en-us/powershell/module/exchange/new-mailboxrepairrequest?view=exchange-ps
Does the database show correct in eseuti /r?
Eric Yin-MSFT 4,396 Reputation points

2021-01-08T09:37:51.193+00:00

I am writing here to confirm with you how the thing going now?
If you need further help, please provide more detailed information, so that we can give more appropriate suggestions.

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Viktor 1 Reputation point

2021-01-08T19:09:52.253+00:00

[PS] C:\Windows\system32>New-MailboxRepairRequest -Database DAG_DB2 -CorruptionType ProvisionedFolder, SearchFolder, AggregateCounts, Folderview WARNING: The user hasn't logged on to mailbox '00000000-0000-0000-0000-000000000000' ('DAG_DB2'), so there is no data to return. After the user logs on, this warning will no longer appear. [PS] C:\Windows\system32>Get-MailboxRepairRequest -Database DAG_DB2 [PS] C:\Windows\system32>
Алексей Муравлев 6 Reputation points

2021-02-01T15:23:20.493+00:00

We have the same problem..
Viktor 1 Reputation point

2021-02-01T15:35:03.223+00:00

Hi!

Try to run:

Update-DatabaseSchema "failed_DB_Name"

Then unmount and mount this DB again.
Алексей Муравлев 6 Reputation points

2021-02-01T17:53:11.61+00:00

Unfortunately this did not solve the problem.

Were you able to fix it?

Unfortunately this did not solve the problem.

Were you able to fix it?

Unfortunately this did not solve the problem.

Were you able to fix it?

Unfortunately, this command did not solve the problem. Were you able to fix it?
Алексей Муравлев 6 Reputation points

2021-02-01T17:55:18.457+00:00

Unfortunately, this command did not solve the problem. Were you able to fix it?
Viktor 1 Reputation point

2021-02-01T18:10:47.323+00:00

You must remount database after that command. It's important.
And yes, my problem is fixed by that way.
For test, you can run:

Get-MailboxDatabaseCopyStatus "failed_DB_Name" |fl *guid*,*schema*

If you see something like this:

MinimumSupportedDatabaseSchemaVersion : 0.121 MaximumSupportedDatabaseSchemaVersion : 0.185 RequestedDatabaseSchemaVersion : 0.121

A problem in RequestedDatabaseSchemaVersion
On the correct database it must be 0.185

After Update-DatabaseSchema and remount it should be 0.185

And...
I did it on the database with only one copy (right after create first copy). Not sure, but that might be important too.
Алексей Муравлев 6 Reputation points

2021-02-01T19:16:53.703+00:00

Version of the database Exchange Database 11 is correct, but Test-MapiConnectivity is failed. Any other thoughts?

Thanks in advance.
Viktor 1 Reputation point

2021-02-01T19:45:16.833+00:00

No, DB Schema version for "Exchange Database 11" is not correct too.
You have:
RequestedDatabaseSchemaVersion : 0.121

Correct version is 0.185.

And I remember, we change in BIOS:

Hyper-Threading -> disabled

NUMA Group Size Optimization -> flat

And upgraded to Exch19_CU8 (currently max actual version), by MS SupportPro request, before Update-DatabaseSchema.

That's all.

By the way, we created a new DAG, and moved servers from old DAG to a new DAG, but it's not helped, so I think, it's not so important.
Timothy C. Good 0 Reputation points

2025-05-23T20:41:48.9333333+00:00

I think if found the issues. The database schema is a at a mis match.
Get-MailboxDatabaseCopyStatus "Exchange Database 11" | fl guid,schema

MinimumSupportedDatabaseSchemaVersion : 0.121

MaximumSupportedDatabaseSchemaVersion : 0.185

RequestedDatabaseSchemaVersion : 0.121

Run the following:

Update-DatabaseSchema DB01

Dismount-Database DB01

Mount-Database DB01

https://learn.microsoft.com/en-us/exchange/troubleshoot/migration/cannot-access-move-mailbox

Answer 1

Thameur-BOURBITA 36,266 Moderator

Hi,

Try restart the Microsoft Exchange Mailbox Replication service or/and the Information Store service. then if you still have the same issue.

Please Don't forget to mark this reply as answer if it help you to fix your issue

Viktor 1 Reputation point

2020-12-22T11:55:31.98+00:00

Hi,

Server was restarted (cold reboot) - no effect.
Both services restarted (right now) - no effect.

Answer 2

Eric Yin-MSFT 4,396

Enable MapioverHttp on the new organization and recreate the new mailbox database should solve the issue:

Set-OrganizationConfig -MapiHttpEnabled $true

Found a similar thread here: https://social.technet.microsoft.com/Forums/office/en-US/7662c0a7-50fc-459a-ab31-b05b7b451921/errors-working-with-databases-microsoftmapimapiexceptionnosupport-mapiexceptionnosupport?forum=Exch2019

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Viktor 1 Reputation point

2020-12-23T08:21:45.547+00:00

Hi!
Thanks for reply.
I found that thread, but we had MapiHttpEnabled activated for a long time (right after Exchange 2013 was installed).
I applied "Set-OrganizationConfig -MapiHttpEnabled $true" now, with no effect.
Eric Yin-MSFT 4,396 Reputation points

2020-12-23T09:34:37.187+00:00

Have you tried to:
1.recreate the new database
2.recreate arbitration mailbox on new server
3.reboot the new server
Viktor 1 Reputation point

2020-12-23T09:46:24.373+00:00
Yes

Yes

Yes

No effect.

Answer 3

Алексей Муравлев 6

Thanks, fixed after remounting database.

Answer 4

R. Bitrary 1

If you stumbled upon this one please see https://stackoverflow.com/questions/66195884/

Yes, its the scheme. But you cannot change it while beeing DAG member.

Create the MBXDB before joining a DAG in a 2013/2019 migragtion.

Share via

Microsoft System Attendant on the Exchange 2019

4 answers

Your answer