Got the following error yesterday morning:
Log Name: Application
Source: MSExchangeTransport
Date: 5/13/2013 8:01:29 AM
Event ID: 15006
Task Category: ResourceManager
Level: Error
Keywords: Classic
User: N/A
Computer: servername.domain.local
Description:
Microsoft Exchange Transport is rejecting message submissions because the available disk space has dropped below the configured threshold.
The following resources are under pressure:
Queue database logging disk space ("C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\") = 96% [Medium] [Normal=94% Medium=96% High=98%]
Physical memory load = 97% [limit is 94% to start dehydrating messages.]
The following components are disabled due to back pressure:
Inbound mail submission from the Internet
Mail submission from Pickup directory
Mail submission from Replay directory
Content aggregation
The following resources are in normal state:
Queue database and disk space ("C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue\mail.que") = 95% [Normal] [Normal=95% Medium=97% High=99%]
Version buckets = 0 [Normal] [Normal=80 Medium=120 High=200]
Private bytes = 4% [Normal] [Normal=71% Medium=73% High=75%]
Batch Point = 0 [Normal] [Normal=2000 Medium=4000 High=8000]
Submission Queue = 0 [Normal] [Normal=1000 Medium=2000 High=4000]
I noticed that email could be sent outbound, but inbound mail was not being received.
I restarted the server almost 4 hours after this event. After rebooting, mail started coming in inbound. After seeing this error message, I applied more disk space to the C volume to resolve this issue. However, all emails within the timeframe of this event
log until restarting the server seem to be lost. It is important to note that we use MXLogic for email continuity when the server goes down, but MXLogic could communicate to the server the whole time, so it never entered Disaster Recovery mode and stored emails.
I have four questions:
1) What happened to the emails during that time frame?
2) Is there any way for me to recover them?
3) Why did exchange not send Non-Deliverable messages back to the senders during this time frame?
4) Can Exchange be set to do that in this situation?
The problem is that when this occured, there was no notification to anyone sending us emails that we were not getting them. Therefore, unless they contact us again, we will never know that they sent us anything. This is not good.