Hi,

We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013.  We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.  

If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email.  Most of the users do not log into OWA but only uses Outlook.

It looks like other people are also seeing this similar issue but I am unable to find any solution for it.

How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.

T

Hi,

We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013.  We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.  

If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email.  Most of the users do not log into OWA but only uses Outlook.

It looks like other people are also seeing this similar issue but I am unable to find any solution for it.

How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.

T

User couldn't receive notification when his mailbox exceeded a specified storage quota.

This means your server is healthy.

I recommend you reset mailbox storage quotas for the user's specific mailbox to check the result.

If the problem persists, please check the users event log for mailbox size warnings.

for  reference - http://technet.microsoft.com/en-us/library/aa998353.aspx

Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.

Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database 326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.

========================

Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0() at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunc

I saw this solution in another forum.

If the effected users are on 2013, create a new DB on Exchange 2013, set quota limit, move one of the mailboxes to the it and wait 24 hours for Exchange to run the QuotaNotificationSchedule task to check which mailbox is over the limit.

If they are on 2010 create the DB on 2010.

If it works move the other mailboxes to the new DB.

To check what time the DB quota notification job is running on your server use the cmdlet:

Get-MailboxDatabase MBX | select *QuotaNotificationSchedule

Hi Raman,

Please run the following command to check your mailbox quota settings:

Get-MailboxDatabase DB01 | FL *quata*

We can check the IssueWarningQuota limit, ProhibitSendQuota limit and ProhibitSendReceiveQuota limit values for the mailbox and database.

When the mailbox exceeds any of this quota, these quota messages are sent during the QuotaNotificationSchedule specified for each mailbox database. Please set the QuotaNotificationSchedule parameter.

Regards,

Hi

In addition to above you can check below

By design Warning quotas will not fire unless they are set to greater than 50% of the prohibit send quota. 
Also ensure that  "Prohibit Send Quota Message" value is set else quota warning message will not be sent out to end users.

Better check  the two below values  and check they have values 
ProhibitSendReceiveQuota
ProhibitSendQuota

Hi,

Thanks for your responses.

I have done many tests it looks like any mailbox moved from Exchange 2010 to Exchange 2013 is not receiving mailbox full warning alert.  Mailbox only receives it, if I move that mailbox again from Exchange 2013 to 2013 database.  Apparently I cannot do this for thousands of mailboxes.

Are there any other thoughts? Is anyone else able to reproduce this issue?

Thanks,

Hi Raman,

Based on my further research, this is a known issue which is pending research. After migration to Exchange 2013, the moirated mailbox who exceeded quota will not receive quota warning message

The optional workaround is to move the mailbox to another Exchange 2013 database. If this workaround can't be implemented in your environment, please waiting for the updates. Thanks for your understanding.

Regards, 

Thanks Winnie.

I have the same issue on our installation. Has there been any update or resolution on the update. 

Thanks,
Michael 

Hi Michael,

There is no resolution yet.  But If you are on Exchange 2013 CU7.

Run the following command on effected mailbox.  It is not going to make any change it just reset the property.  You may test it first on a mailbox.

Get-Mailbox userid | Set-MailboxRegionalConfiguration

We encountered this issue and this should help you.

This issue occurs because, during the migration process, the Windows Language Code Identifier (LCID) property which dictates the language specifics of the mailbox is not transferred to Exchange Server 2013. Therefore, the appropriate locale and language of the quota warning message cannot be obtained from the mailbox, and the quota warning message submission fails.

Update exchange server to CU8 KB3030080 

https://www.microsoft.com/en-us/download/details.aspx?id=46373

If you do not want to update Exchange 2013, use the method below.

To work around this issue, run the following PowerShell cmdlet to set the language property on Active Directory and the LCID property of the affected mailbox after the migration is complete:

Set-MailboxRegionalConfiguration <user> -Language <language code>

Note This workaround consists of resetting the mailbox regional configuration. Also, it works in an Exchange Server 2013 environment that has Cumulative Update 6 or a later version update installed.

More information 

https://support.microsoft.com/en-us/kb/3036952 

• Edited by DjMaxNz 3 hours 3 minutes ago formatting
• Proposed as answer by DjMaxNz 3 hours 1 minutes ago

We encountered this issue and this should help you.

This issue occurs because, during the migration process, the Windows Language Code Identifier (LCID) property which dictates the language specifics of the mailbox is not transferred to Exchange Server 2013. Therefore, the appropriate locale and language of the quota warning message cannot be obtained from the mailbox, and the quota warning message submission fails.

Update exchange server to CU8 KB3030080 

https://www.microsoft.com/en-us/download/details.aspx?id=46373

If you do not want to update Exchange 2013, use the method below.

To work around this issue, run the following PowerShell cmdlet to set the language property on Active Directory and the LCID property of the affected mailbox after the migration is complete:

Set-MailboxRegionalConfiguration <user> -Language <language code>

Note This workaround consists of resetting the mailbox regional configuration. Also, it works in an Exchange Server 2013 environment that has Cumulative Update 6 or a later version update installed.

More information 

https://support.microsoft.com/en-us/kb/3036952 

• Edited by DjMaxNz Tuesday, May 12, 2015 4:22 AM formatting
• Proposed as answer by DjMaxNz Tuesday, May 12, 2015 4:23 AM

Hi,

Thanks for the update.  As, I mentioned in my earlier post to Michael that it worked if we reset the Regional configuration.

Get-Mailbox userid | Set-MailboxRegionalConfiguration