Go Premium for a chance to win a PS4. Enter to Win


Exchange 2k7 Transport issue

Posted on 2011-03-20
Medium Priority
Last Modified: 2012-05-11
Today one user send 2GB attachement to 10 internals users, since them my exchange server Edgetransport was showing very high memory utilization, after seerver restart Exchange Transport service is in "starting" no error in event log, please help
Question by:sohailaz
  • 4
  • 4
LVL 17

Expert Comment

by:Viral Rathod
ID: 35175332
Again try to restart the Transport service and letus know the results.

Author Comment

ID: 35175369
I can not restart the services because it is hanging, I had to restart the server which I have done sevral times in last 6 hours.

Any other idea
LVL 17

Expert Comment

by:Viral Rathod
ID: 35175376
No do not restart the process go to task manager and kill the MSEXCHNAGETRANSPORT.exe process and then try to start the service.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

LVL 17

Expert Comment

by:Viral Rathod
ID: 35175379
There is no need to restart the server , go to task manager and kill the MSEXCHNAGETRANSPORT.exe process and then try to start the service.

Author Comment

ID: 35175829
I tried that but no luck, service is not starting
LVL 17

Expert Comment

by:Viral Rathod
ID: 35179767
please try to stop Microsoft Exchange Transport Service, then rename mail.queu database, then try to start Transport service (Ranaming the queue database will create new queue database)

Letus know the results.

Expert Comment

by:I Qasmi
ID: 35196979
Check whether lowdisk space is observed on the C:\ or not if below 4 GB then move the database queue path to another drive say D:\ as the backpressure can cause this happen.

What is back pressure?
One problem that many administrators run into after successfully transitioning to Exchange 2007 is back pressure. Back pressure is a feature built into the transport roles (hub and edge) in Exchange 2007 that helps deal with available resources for the transport queue database.  As part of the monitoring, Exchange keeps a watchful eye over some resources including free space on the drives holding both the message queue database and its related tracking logs; the number of uncommitted message queue transactions in memory, and the memory used by both the EdgeTransport.exe as well as all other processes.

The queue database has three thresholds; normal, medium, and high. Normal means just what it implies – all monitored resources are within normal tolerances. Medium means that the resources are a little above normal. As part of the Medium level, internal messages continue to flow fine, but messages and connections from external sources can be rejected. When the High level is reached, the full force of back pressure kicks in, and all message flow stops. Connections and messages are rejected by the server.  You’ll also start to see event 15002 and 1009 messages in your application event log, such as those shown below:

Event Type: Warning
Event Source: MSExchangeTransport
Event Category: ResourceManager
Event ID: 15002
Date: 8/10/2008
Time: 11:38:19 PM
User: N/A
Computer: SH-EMAIL2
Description: The resource pressure is constant at High. Statistics:
Queue database and disk space ("C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue\mail.que") = 75% [High] [Normal=70% MediumHigh=72% High=74%]
Queue database logging disk space ("C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue'") = 76% [Normal] [Normal=92% MediumHigh=94% High=96%]
Version buckets = 1 [Normal] [Normal=40 MediumHigh=60 High=100]
Private bytes = 14% [Normal] [Normal=71% MediumHigh=73% High=75%]
Physical memory load = 52% [limit is 94% to start dehydrating messages.]
Inbound mail submission from other Hub Transport servers, the Internet, the Pickup directory, the Replay directory, and the Mailbox server, if it is on a Hub Transport server, has stopped. Loading of e-mail from the queuing database, if available, continues.
<hr />
Event Type: Warning
Event Source: MSExchangeMailSubmission
Event Category: MSExchangeMailSubmission
Event ID: 1009
Date: 08/10/2008
Time: 11:38:19 PM
User: N/A
Computer: SH-EMAIL2
Description: The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.

Generally, once the thresholds drop down, message flow is restored. The availability of various services based on resource level is shown in Table 1.

Resource level Connections from other Hub Transport servers Connections from other messaging servers Connections from Mailbox servers Pickup directory & Replay directory submission Internal mail flow
Normal Available Available Available Available Available
Medium Available Unavailable Available Unavailable Unavailable
High Unavailable Unavailable Unavailable Unavailable Unavailable

Table 1: Resource level and service availabilities

The exact formulas used to determine back pressure are based on drive sizes and other parameters depending on whether the server is running the RTM or Service Pack 1 version of Exchange 2007. For more info on the formulas, as well as an in depth look at back pressure, see this article in the Microsoft TechNet Library.

Moving the queue database
So let’s take a look at how best to resolve the problem. The default location for the queue database and its related files is C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue. As you can guess, keeping these files on the system drive probably isn’t a good long term plan. As message activity increases, the back pressure problem could become more severe. So let’s look into moving them.

In the RTM version of Exchange 2007, changing the location of the queue database was somewhat painful, because an admin would need to manually edit the C:\Program Files\Microsoft\Exchange Server\Bin\EdgeTransport.exe.config file, move some files, and restart the Transport service. In Service Pack 1, however, the Exchange Product Group made things much simpler by providing a new PowerShell script, Move-TransportDatabase.ps1, that automates the process. By using the script, the following tasks are completed:

Free space is checked on the destination drive for the Queue Database and Queue Database Logs
Create the destination path for the Queue Database and Queue Database Logs
Assign Full Control permissions for Network Service, Local System, and Administrators for both paths
Stop the Exchange Transport Service
Backup the original EdgeTransport.exe.config file
Move the Queue Database files, mail.que and trn.chk, to the destination folder
Update the Queue Database path
Move the file trn.log and any trn*.log files to the destination folder
Update the path for Queue Database Logs
Restart the Transport Service
Note that the PowerShell script does stop the Transport service during the move, so you’ll want to schedule this for a relatively quiet time to minimize disruptions of your messaging system. And obviously, this is a per server setting, so if you’re using more than one transport server, you’ll want to address this on each.

As with any change to your messaging environment, ensure you have a full backup before proceeding. Once you’ve determined where you’re going to move the files to, open the Exchange Management Shell (EMS), and invoke the Move-TransportDatabase.ps1 script, specifying the new QueueDatabasePath and QueueDatabaseLoggingPath variables, such as this:

Move-TransportDatabase.ps1 -QueueDatabasePath: D:\Exchsrvr\TransportRoles\data\Queue -QueueDatabaseLoggingPath: D:\Exchsrvr\TransportRoles\data\Queue

In the above example, I’m moving both the database and log files to the D:\Exchsrvr\TransportRoles\data\Queue folder.

As we can see in the Figure 1, the script goes through each step of the process, and tells us at the end that the script executed successfully.

 Figure 1: Move-TransportDatabase.pst moving the queue database

When we look in the destination location, we can see the database and its files are now there, as seen in Figure 2.

Figure 2: Destination folder

The Move-TransportDatabase.ps1 script does a MOVE of the files, so they no longer exist in their original location. The script runs very quickly, and in this example running on an old server, took about 15 seconds to run.

 1 2

Accepted Solution

sohailaz earned 0 total points
ID: 35311930
Thanks for the help but by the time I received theses answers I have figured out the issue by my self.

Author Closing Comment

ID: 36212781

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

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

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

926 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