Microsoft Exchange Transport Service has been stopped.

Question

I changed out failing drives on a customers SBS 2011 which uses Intel Rapid Storage Technology. I saw that it had an option to email a failing condition to up to three addresses. I configured it but got the Could Not Connect error from the RST software.
I Googled the condition and determined that I needed to install another Receive Connector on a different port, which is what I tried.
I opened all of the receive connectors in the MS Exchange Console - Server Configuration - Hub Transport section. As far as I know I did not change anything there, I just looked and cancelled. None of the new receive connectors I configured worked., Everytime
one configuration made no difference I deleted the connector, re added a connector using different options and tried the RST email test again.
Getting nowhere, I deleted the last new connector I configured, Closed the Exchange management console figuring I had a job for some time in the future when things were slow.
This morning I get the call No e-mail, and found the Exchange Transport Service stopped. I restarted it, made sure it was set to automatic, and it ran for about 3 minutes and then stopped. Right now I am keeping my customer working by starting the service
every 5 to 10 minutes.
Since I am not going to stay here indefinitely restarting the service, I need help!
J R Weymouth

Answer 1

Thanks for the links, I'll check them out. I finally got an error from the logs, in fact there are so many errors in the log I don't even know which one to follow. It gets a cluster of errors every 5 minutes (6 errors one critical) but that is when the transport
is shut down. I am relaying the first message that comes up after I restart the transport.
Log Name:      Application
Source:       
MSExchangeTransport
Date:         
9/16/2014 9:11:48 AM
Event ID:      17003
Task Category: Storage
Level:        
Error
Keywords:      Classic
User:         
N/A
Computer:      SBSSRVR2011.MyDomain.local
Description:
Sender Reputation Database: An operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required. Exception details: Microsoft.Exchange.Isam.IsamDbTimeCorruptedException:
Dbtime on current page is greater than global database dbtime (-344)
   at Microsoft.Exchange.Isam.JetInterop.MJetDelete(MJET_TABLEID tableid)
   at Microsoft.Exchange.Isam.Interop.MJetDelete(MJET_TABLEID tableid)
   at Microsoft.Exchange.Transport.Storage.DataTableCursor.DeleteCurrentRow()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="49156">17003</EventID>
    <Level>2</Level>
    <Task>17</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-16T16:11:48.000000000Z" />
    <EventRecordID>1141638</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SBSSRVR2011.BainInsuranceAgency.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Sender Reputation Database</Data>
    <Data>Microsoft.Exchange.Isam.IsamDbTimeCorruptedException: Dbtime on current page is greater than global database dbtime (-344)
   at Microsoft.Exchange.Isam.JetInterop.MJetDelete(MJET_TABLEID tableid)
   at Microsoft.Exchange.Isam.Interop.MJetDelete(MJET_TABLEID tableid)
   at Microsoft.Exchange.Transport.Storage.DataTableCursor.DeleteCurrentRow()</Data>
  </EventData>
</Event>
J R Weymouth