Posts: 5
Joined: 18.Jun.2008
From: Sao Paulo, Brazil
Status: offline
Hello to all!
We run Windows Server 2003 R2 SP2 and Exchange Server 2007 SP1 with the Update Rollup 2 installed. Every now and then our Hub Transport server stops working with no warnings - the Microsoft Exchange Transport service just stops by itself, and no events explaining why the service has stopped are logged to Event Viewer.
Digging the Event Viewer I found the following:
Event Type: Warning Event Source: MSExchangeMailSubmission Event Category: MSExchangeMailSubmission Event ID: 1009 Date: 18/06/2008 Time: 07:18:07 User: N/A Computer: <server-name> 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.
Even though Service Control Manager is configured to restart the service if it crashes, nothing happens – we solve the issue simply starting the service manually.
This has also happened to our Edge Transport server.
I have searched Microsoft Support, Exchange Blogs (MS-official and no official), the internet, but I couldn't find anything. Does anyone have any idea of what's happening? Is there any way to correct this and/or automate the process of restarting the service (like monitoring the event id 1009 from MSExchangeMailSubmission, since it’s the only one being logged, with “pure” Windows/Exchange – that is, no 3rd party tool/application installed to do the monitoring)?
Remember to backup before applying the advice. www.saiconsult.co.uk. Happy to provide Professional Exchange Server Consultancy to anywhere in the world.
Posts: 5
Joined: 18.Jun.2008
From: Sao Paulo, Brazil
Status: offline
Thank you rishishah, but back pressure occurs when you run out of disk space on the disk where the queue is located, and it does not stop the Microsoft Exchange Transport service: it just makes the service stop accepting new messages until the queue is cleaned and disk space is reclaimed - we have plenty of disk space where the queue is located.
What happens here is that the Microsoft Exchange Transport service just stops, as if someone went to Service Manager and stopped it there - no warnings, no errors, no nothing that could give me a clue of what's happening.
Posts: 784
Joined: 14.Nov.2006
From: Surrey, UK
Status: offline
till you find event logs that relat to you issue, i sugets you sue the net start command and schedule it every few mins to run and start you rlevant services.
Atleast this way they will start back up.
I know this is not want you are looking for, but try and dig around for logs or events.
_____________________________
Rishi Shah, MCP
Remember to backup before applying the advice. www.saiconsult.co.uk. Happy to provide Professional Exchange Server Consultancy to anywhere in the world.
Posts: 5
Joined: 18.Jun.2008
From: Sao Paulo, Brazil
Status: offline
There's no antivirus software installed on the Exchange box; we are using Tivoli Data Protection but it doesn't appear to be the cause of the problem, since it happens way after the backup has finished. Anyway, thank you for your suggestion!
Thank you rishishah, but back pressure occurs when you run out of disk space on the disk where the queue is located, and it does not stop the Microsoft Exchange Transport service ...
I have the same setup and i'm having the exact same error and can't find any traces for my problem, this same behavior is happening with other Exchange Services, but mainly with Transport Service.
I came across an issue on Exchange 2007 a while back now. Basically we received a few alerts on SCOM regarding the Hub Transport Service being stopped on an Exchange Server.
So i jumped onto the server in question and came across the following events in the event log.
“Event Type: Error Event Source: ESE Event Category: Transaction Manager Event ID: 623 Date: Time: User: N/A Computer: Description: edgetransport (5612) Transport Mail Database: The version store for this instance (0) has reached its maximum size of 249Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Possible long-running transaction: SessionId: 0×0000000005217400 Session-context: 0×00000000 Session-context ThreadId: 0x00000000000014F8 Cleanup: 1
Event Type: Error Event Source: MSExchangeTransport Event Category: Storage Event ID: 17017 Date: Time: User: N/A Computer: Description: Transport Mail Database: Quota exceeded while performing a database operation. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamVersionStoreOutOfMemoryException: Version store out of memory (cleanup already attempted) (-1069) at Microsoft.Exchange.Isam.?A0x051b51e0.HandleError(Int32 err) at Microsoft.Exchange.Isam.Interop.MJetSetColumn(MJET_TABLEID tableid, MJET_COLUMNID columnid, Byte[] data, MJET_GRBIT grbit, MJET_SETINFO setinfo) at Microsoft.Exchange.Transport.Storage.DataStreamImmediateWriter.Write(Int64 position, Byte[] data) ”
So i started the Hub transport service again and then had a quick look at the mail queue via queue viewer. In The queue viewer i spotted a 250mb e-mail and consequently was just too big for the hub transport to handle and causing the service to stop.
To get his issue fixed i had to get rid of this mail out of the queue, first i tried removing the mail with no NDR, this got rid of the mail, however 20 seconds later it reappeared again.
So what i had to do was recreate the queue, so it basically got rid of all mail that was currently in the queue. The downside to this is that other mail still queuing up on the Hub Transport server will be lost to.
Resolution
1, Make sure the MS Exchange Transport service is stopped.
2, Rename the following directory “<drive>\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue” to “<drive>\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue_old”
3, Start the MS Exchange Transport service
4, This Should Recreate the Queue folder and the “MS Exchange Transport” will no longer stop.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Message Routing >> Microsoft Exchange Transport service stops by itself 
Microsoft Exchange Transport service stops by itself - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
