locked
Unable to Start Microsoft Exchange Transport Service on Exchange 2010 & Windows Server 2008 R2 RRS feed

  • Question

  • Hello Everyone,

    I have a Microsoft Windows Server 2008 R2 with Exchange 2010 (Rollup 5) both on the same server (currently in staging and testing environment). Unfortunately, I've not been able to get the Exchange 2010 Transport Service running. It's been almost 7 days now since I've been dealing with this problem and I'm very frustrated now.

    Here's what happens:

    When i try to start the Microsoft Exchange Transport Serrvice manually i get the following error:

    The Microsoft Exchange Transport Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

    Here's the Event ID's that are generated:

    Log Name:      Application
    Source:        ESE
    Date:          9/27/2011 9:47:26 AM
    Event ID:      412
    Task Category: Logging/Recovery
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      computername.domain.com
    Description:
    edgetransport (23704) IP Filtering Database: Unable to read the header of logfile C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter\trn.log. Error -546. 
    
    For more information, click http://www.microsoft.com/contentredirect.asp.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ESE" />
        <EventID Qualifiers="0">412</EventID>
        <Level>2</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-09-27T13:47:26.000000000Z" />
        <EventRecordID>85211</EventRecordID>
        <Channel>Application</Channel>
        <Computer>computername.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>edgetransport</Data>
        <Data>23704</Data>
        <Data>IP Filtering Database: </Data>
        <Data>C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter\trn.log</Data>
        <Data>-546</Data>
      </EventData>
    </Event>
    

     

    Log Name:      Application
    Source:        MSExchangeTransport
    Date:          9/27/2011 9:47:26 AM
    Event ID:      17016
    Task Category: Storage
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      computername.domain.com
    Description:
    IP Filtering Database: An operation has encountered a fatal error. The database may be fragmented and manual offline defragmentation using ESEUTIL may be required. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamLogSectorSizeMismatchException: the log file sector size does not match the current volume's sector size (-546)
       at Microsoft.Exchange.Isam.JetInterop.MJetInit(MJET_INSTANCE instance)
       at Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance)
       at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeTransport" />
        <EventID Qualifiers="49156">17016</EventID>
        <Level>2</Level>
        <Task>17</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-09-27T13:47:26.000000000Z" />
        <EventRecordID>85212</EventRecordID>
        <Channel>Application</Channel>
        <Computer>computername.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>IP Filtering Database</Data>
        <Data>Microsoft.Exchange.Isam.IsamLogSectorSizeMismatchException: the log file sector size does not match the current volume's sector size (-546)
       at Microsoft.Exchange.Isam.JetInterop.MJetInit(MJET_INSTANCE instance)
       at Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance)
       at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()</Data>
      </EventData>
    </Event>
    


    Log Name:      Application
    Source:        MSExchangeTransport
    Date:          9/27/2011 9:47:26 AM
    Event ID:      7001
    Task Category: Components
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:     computername.domain.com
    Description:
    The service will be stopped. Reason: A failure occurred in a transport database operation.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeTransport" />
        <EventID Qualifiers="16388">7001</EventID>
        <Level>4</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-09-27T13:47:26.000000000Z" />
        <EventRecordID>85213</EventRecordID>
        <Channel>Application</Channel>
        <Computer>computername.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>A failure occurred in a transport database operation.</Data>
      </EventData>
    </Event>
    

    I can provide any more information that you might need. Looking forward to resolve this problem.

    Thanks!

    Tuesday, September 27, 2011 2:09 PM

Answers

  • On Tue, 27 Sep 2011 14:09:20 +0000, jas_singh wrote:
     
    >
    >
    >Hello Everyone,
    >
    >I have a Microsoft Windows Server 2008 R2 with Exchange 2010 (Rollup 5) both on the same server (currently in staging and testing environment). Unfortunately, I've not been able to get the Exchange 2010 Transport Service running. It's been almost 7 days now since I've been dealing with this problem and I'm very frustrated now.
    >
    >Here's what happens:
    >
    >When i try to start the Microsoft Exchange Transport Serrvice manually i get the following error:
    >
    >The Microsoft Exchange Transport Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.Here's the Event ID's that are generated:
    >
    >
    >Log Name: Application
    >Source: ESE
    >Date: 9/27/2011 9:47:26 AM
    >Event ID: 412
    >Task Category: Logging/Recovery
    >Level: Error
    >Keywords: Classic
    >User: N/A
    >Computer: computername.domain.com
    >Description:
    >edgetransport (23704) IP Filtering Database: Unable to read the header of logfile C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter\trn.log. Error -546.
     
    Stop the transport service.
     
    Move (don't copy) the contents of the C:\Program
    Files\Microsoft\Exchange Server\TransportRoles\data\IpFilter directory
    to another location. The directory should now be empty.
     
    Start the transport service. This should create a new, empty, database
    and log files.
     
    If everything starts working okay, delete the old contents of the
    directory.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by emma.yoyo Thursday, September 29, 2011 8:15 AM
    • Marked as answer by emma.yoyo Monday, October 3, 2011 2:00 AM
    Tuesday, September 27, 2011 9:57 PM

All replies

  • Any help would be much appreciated!
    Tuesday, September 27, 2011 7:39 PM
  • On Tue, 27 Sep 2011 14:09:20 +0000, jas_singh wrote:
     
    >
    >
    >Hello Everyone,
    >
    >I have a Microsoft Windows Server 2008 R2 with Exchange 2010 (Rollup 5) both on the same server (currently in staging and testing environment). Unfortunately, I've not been able to get the Exchange 2010 Transport Service running. It's been almost 7 days now since I've been dealing with this problem and I'm very frustrated now.
    >
    >Here's what happens:
    >
    >When i try to start the Microsoft Exchange Transport Serrvice manually i get the following error:
    >
    >The Microsoft Exchange Transport Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.Here's the Event ID's that are generated:
    >
    >
    >Log Name: Application
    >Source: ESE
    >Date: 9/27/2011 9:47:26 AM
    >Event ID: 412
    >Task Category: Logging/Recovery
    >Level: Error
    >Keywords: Classic
    >User: N/A
    >Computer: computername.domain.com
    >Description:
    >edgetransport (23704) IP Filtering Database: Unable to read the header of logfile C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\IpFilter\trn.log. Error -546.
     
    Stop the transport service.
     
    Move (don't copy) the contents of the C:\Program
    Files\Microsoft\Exchange Server\TransportRoles\data\IpFilter directory
    to another location. The directory should now be empty.
     
    Start the transport service. This should create a new, empty, database
    and log files.
     
    If everything starts working okay, delete the old contents of the
    directory.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by emma.yoyo Thursday, September 29, 2011 8:15 AM
    • Marked as answer by emma.yoyo Monday, October 3, 2011 2:00 AM
    Tuesday, September 27, 2011 9:57 PM
  • Hi jas_singh,

    Any updates?

    Frank Wang

    Thursday, September 29, 2011 8:15 AM
  • Hi Rich

    Thank you for the advice but it did not work on my server, still have the continual stop of the Microsoft Exchange Transport Service. I sm running on about 2 hours sleep a night for the last 4 nights and am really brin dead, I am sure someone has a simple solution for this log:

    Source: MSExchangeTransport

    Event ID:17016

    Transport Mail Database: An operation has encountered a fatal error. The database may be fragmented and manual offline defragmentation using ESEUTIL may be required. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamLogSectorSizeMismatchException: the log file sector size does not match the current volume's sector size (-546)
       at Microsoft.Exchange.Isam.?A0xf05d328c.HandleError(Int32 err)
       at Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance)
       at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()

    I would appreciate any help at this stage.

    Darren

    Saturday, May 11, 2013 5:25 PM
  • On Sat, 11 May 2013 17:25:20 +0000, dazza2502 wrote:
     
    >
    >
    >Hi Rich
    >
    >Thank you for the advice but it did not work on my server, still have the continual stop of the Microsoft Exchange Transport Service. I sm running on about 2 hours sleep a night for the last 4 nights and am really brin dead, I am sure someone has a simple solution for this log:
    >
    >Source: MSExchangeTransport
    >
    >Event ID:17016
    >
    >Transport Mail Database: An operation has encountered a fatal error. The database may be fragmented and manual offline defragmentation using ESEUTIL may be required. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Exchange.Isam.IsamLogSectorSizeMismatchException: the log file sector size does not match the current volume's sector size (-546) at Microsoft.Exchange.Isam.?A0xf05d328c.HandleError(Int32 err) at Microsoft.Exchange.Isam.Interop.MJetInit(MJET_INSTANCE instance) at Microsoft.Exchange.Transport.Storage.DataSource.InitInstance()
    >
    >I would appreciate any help at this stage.
     
    Although it's not an exact match to your problem, have a look at this:
     
    http://blogs.technet.com/b/exchange/archive/2013/04/24/exchange-2010-database-availability-groups-and-disk-sector-sizes.aspx
     
    If your transport database is on the c: drive you can use this to get
    the bytes per sector and filerecord segment.
     
    fsutil fsinfo ntfsinfo c:
     
    This will get you the information for the log files (change the name
    to one of the log files in the transport database directory):
     
    eseutil /ml trn000000BA.log
     
    You may be trying to use a disk that uses a format not supported by
    the O/S.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Sunday, May 12, 2013 9:45 PM
  • To add to this conversation, I recently faced the same 17016 Exchange transport service error after migrating our SBS 2008 server from VMWare ESXi 4.1 to Hyper-V 2012. Long story short, the problem was caused by the conversion creating the new Hyper-V virtual disk as a .vhdx instead of a .vhd.  Apparently, .vhdx disks have an extra property on them called "bytes per physical sector" which was 4k, as opposed to bytes per sector on the original VMWare drive, which was 512.  

    You can check your drive's status by opening a command prompt and typing:

    fsutil fsinfo ntfsinfo c: (or whatever drive contains your Exchange databases.)

    For me, the solution was to do the migration again and make sure the drives convert to .vhd files.  Doing so literally solved every problem I had with the first migration.


    Max

    Sunday, December 14, 2014 1:42 PM