We encountered this exact error message while doing our Exchange 2013 to 2019 migration. We had to mail-enable the user on one of the Exchange 2019 mailbox databases, and that seems to have resolved the issue. There is a small footnote in the instruc...