question

Al-Amran avatar image
0 Votes"
Al-Amran asked BrianCollis-8971 commented

After migrating mailbox from Exchange Online to Exchange 2013, users are facing webmail login issue

Hybrid Exchange | After migrating mailbox Exchange Online to Exchange 2013, users are facing webmail login issue


Below is the error,

An unexpected error occurred and your request couldn't be handled.
X-ClientId: MCLC - NA9G - EKFB - KYNGG
X-OWA-Error: SDServerErr;System.ArgumentException
X-OWA-Version: 15.0.1497.12
X-FEServer: EXCH02
X-BEServer: bbl-exch01.bd.example.com
Date: 3/14/2021 12:12:05 PM

office-exchange-server-administrationoffice-exchange-server-connectivityoffice-exchange-hybrid-itprooffice-exchange-server-itpro
· 10
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Try using a different browser, using incognito mode or clearing the browser cache.

0 Votes 0 ·

@AndyDavid

Already tried different browser and incognito mode as well but the result is same. Still unable to login.

0 Votes 0 ·

Ok, I would check security inheritance on the AD account as well. or Try moving it to another database.

Why did you migrate back to on-prem?

0 Votes 0 ·
Show more comments

@Al-Amran

Any update about this thread now?

0 Votes 0 ·

Hi. My customer have the same issue while they migrated back users from Exchange Online to Exchange Server 2013. Could you post whats the workaround that solved your problem before? Thanks.

0 Votes 0 ·

this error is caused by corrupted mailbox property 0x36460102 on Inbox. to fix the issue, use MFCmapi to delete this property

1 Vote 1 ·

this is correct, i solved using MFCmapi to delete this property. Thanks @PaulAllen-3034

0 Votes 0 ·
Show more comments
KyleXu-MSFT avatar image
0 Votes"
KyleXu-MSFT answered Al-Amran commented

@Al-Amran

I would suggest you create a new mailbox on Exchange on-premises, then check whether is this issue only occurs on migrated mailbox.

If this issue also occur on the new created mailbox, I think this issue is related with OWA configuration, we need to troubleshoot from OWA side. Such as recreate OWA virtual directory.

If this issue only occur on migrated mailbox, try to migrate mailbox to another database as AndyDavid said, the migrate could repair some issue on mailbox.


If the response 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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@KyleXu-MSFT

The issue only occurs on migrated mailbox. As per your suggestion, we have migrated mailbox to another database but the issue persists.

0 Votes 0 ·
AndyDavid avatar image
0 Votes"
AndyDavid answered victorvivas-5689 commented

Ok, I have seen this before when you offboard mailboxes back to on-prem, why the need to do that?

There is most likely some metadata in the mailbox properties that still point to 365. The tough part is determining what that is and how to fix it.

If its just one user, can you export everything to a pst via Outlook and create a new mailbox for the user and import back in?

You might get lucky and this will work:

 Set-Mailbox username -ApplyMandatoryProperties





· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@AndyDavid

As per management decision, we will discontinue Exchange Hybrid that's why we need to offboard mailboxes back to on-premise.


Can we execute this command on our problematic user which we already offboard to on-premise?

Set-Mailbox <username> -ApplyMandatoryProperties



0 Votes 0 ·

Yes, use on-prem Exchange Powershell.

I will be surprised if it fixes it, but it wont hurt

0 Votes 0 ·

Did this solution solve your problem?

0 Votes 0 ·

This issue is resolved by Microsoft Support Engineer.

Thanks for your co-operation @AndyDavid @KyleXu-MSFT

0 Votes 0 ·
Show more comments