Solved

Exchange 2013 Event ID 15006 not the usual error

Posted on 2016-09-28
6
19 Views
Last Modified: 2016-10-17
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
0
Comment
Question by:maxxtech
  • 4
  • 2
6 Comments
 
LVL 15

Accepted Solution

by:
Todd Nelson earned 500 total points (awarded by participants)
ID: 41820261
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
 

Author Comment

by:maxxtech
ID: 41820280
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
 
LVL 15

Expert Comment

by:Todd Nelson
ID: 41820282
Does that mean the issue is resolved for you after freeing up sufficient disk space?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:maxxtech
ID: 41820288
Yes,mail flow started working after clearing out space. My question is: why the event ID did not provide the correct description.
0
 
LVL 15

Expert Comment

by:Todd Nelson
ID: 41820312
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
 
LVL 15

Expert Comment

by:Todd Nelson
ID: 41846333
Sufficient information provided to achieve resolution.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Read this checklist to learn more about the 15 things you should never include in an email signature.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question