Exchange 2013 Event ID 15006 not the usual error

Have any of you seen this information for Event ID 15006?

The description for Event ID 15006 from source MSExchangeTransport cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:


the message resource is present but the message is not found in the string/message table
Juan MontejanoFounderAsked:
Who is Participating?
 
Todd NelsonSystems EngineerCommented:
Sounds related to back pressure ... http://exchangeserverpro.com/exchange-transport-server-back-pressure/

How much free space do you have remaining on your Exchange server?
0
 
Juan MontejanoFounderAuthor Commented:
It was low on space. The thing that threw me off was in information in the event log. Usually it would read something like this:

Event Type: Error
Event Source: MSExchangeTransport
Event Category: Resource Manager
Event ID: 15006
Description: The Microsoft Exchange Transport service is rejecting messages because available disk space is below the configured threshold. Administrative action may be required to free disk space for the service to continue operations.
0
 
Todd NelsonSystems EngineerCommented:
Does that mean the issue is resolved for you after freeing up sufficient disk space?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Juan MontejanoFounderAuthor Commented:
Yes,mail flow started working after clearing out space. My question is: why the event ID did not provide the correct description.
0
 
Todd NelsonSystems EngineerCommented:
I would suspect that because disk space was so low that the transport service wasn't running and that's why the event was written the way it was.  Maybe the managed assistant was attempting to fix something at the same time the event was written.  Not seeing the entire context of the event, I can only guess.

Do you have an antivirus product on the specific server?
0
 
Todd NelsonSystems EngineerCommented:
Sufficient information provided to achieve resolution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.