Hi, 

Out transport service keeps crashing. 

The key event in the log appears to be 

"The following resources are under pressure:

Version buckets" (details below) After a while the service crashes and restarts.

Weve reset the mail.que database  by changing its location as per https://technet.microsoft.com/en-us/library/bb125177%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

This has had no discernible impact on the situation.

We have adjusted EdgeTransport.exe.config to increase the VersionBucket Thresholds. We still max out.

We have identified a connector that had no size limit attached (this was an internal one) and most have a 100Mb limit. However the Queue Viewer tool does not show any messages at all in the queues. (earlier in troubleshooting, we would see messages in the queue viewer arriving in waves as clients and remote servers detected the transport service had become (briefly) available).

We have  disabled the default receive connector (on port 25), and again no discernible impact.

Event Logs are below.

Any advice grateful received.

Thanks

Nick

Log Name:      Application

Source:        MSExchangeTransport

Date:          09/07/2015 01:40:38

Event ID:      15004

Task Category: ResourceManager

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:     OURSERVER

Description:

The resource pressure increased from Normal to High.

The following resources are under pressure:

Version buckets = 555 [High] [Normal=160 Medium=250 High=500]

The following components are disabled due to back pressure:

Inbound mail submission from Hub Transport servers

Inbound mail submission from the Internet

Mail submission from Pickup directory

Mail submission from Replay directory

Mail submission from Mailbox server

Mail delivery to remote domains

Content aggregation

Mail resubmission from the Message Resubmission component.

Mail resubmission from the Shadow Redundancy Component

The following resources are in normal state:

Queue database and disk space ("E:\Exchange Server\V15\queue\mail.que") = 66% [Normal] [Normal=95% Medium=97% High=99%]

Queue database logging disk space ("E:\Exchange Server\V15\queue\") = 67% [Normal] [Normal=95% Medium=97% High=99%]

Private bytes = 2% [Normal] [Normal=71% Medium=73% High=75%]

Physical memory load = 64% [limit is 94% to start dehydrating messages.]

Submission Queue = 0 [Normal] [Normal=2000 Medium=4000 High=10000]

Temporary Storage disk space ("C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp") = 79% [Normal] [Normal=95% Medium=97% High=99%]

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchangeTransport" />

    <EventID Qualifiers="32772">15004</EventID>

    <Level>3</Level>

    <Task>15</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-07-09T00:40:38.000000000Z" />

    <EventRecordID>6852117</EventRecordID>

    <Channel>Application</Channel>

    <Computer>OURSERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Normal</Data>

    <Data>High</Data>

    <Data>

The following resources are under pressure:

Version buckets = 555 [High] [Normal=160 Medium=250 High=500]

The following components are disabled due to back pressure:

Inbound mail submission from Hub Transport servers

Inbound mail submission from the Internet

Mail submission from Pickup directory

Mail submission from Replay directory

Mail submission from Mailbox server

Mail delivery to remote domains

Content aggregation

Mail resubmission from the Message Resubmission component.

Mail resubmission from the Shadow Redundancy Component

The following resources are in normal state:

Queue database and disk space ("E:\Exchange Server\V15\queue\mail.que") = 66% [Normal] [Normal=95% Medium=97% High=99%]

Queue database logging disk space ("E:\Exchange Server\V15\queue\") = 67% [Normal] [Normal=95% Medium=97% High=99%]

Private bytes = 2% [Normal] [Normal=71% Medium=73% High=75%]

Physical memory load = 64% [limit is 94% to start dehydrating messages.]

Submission Queue = 0 [Normal] [Normal=2000 Medium=4000 High=10000]

Temporary Storage disk space ("C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp") = 79% [Normal] [Normal=95% Medium=97% High=99%]

</Data>

  </EventData>

</Event>

Followed by 

Log Name:      Application
Source:        MSExchangeTransport
Date:          09/07/2015 01:48:30
Event ID:      17017
Task Category: Storage
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      REDACTED
Description:
Transport Mail Database: Quota was exceeded while performing a database operation. The Microsoft Exchange Transport service is shutting down. Exception details: Microsoft.Isam.Esent.Interop.EsentTransactionTooLongException: Too many outstanding generations between JetBeginTransaction and current generation.
   at Microsoft.Isam.Esent.Interop.Api.JetSetColumn(JET_SESID sesid, JET_TABLEID tableid, JET_COLUMNID columnid, Byte[] data, Int32 dataSize, Int32 dataOffset, SetColumnGrbit grbit, JET_SETINFO setinfo)
   at Microsoft.Exchange.Transport.Storage.DataStreamImmediateWriter.Write(Int64 position, Byte[] data)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="49156">17017</EventID>
    <Level>2</Level>
    <Task>17</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-09T00:48:30.000000000Z" />
    <EventRecordID>6852160</EventRecordID>
    <Channel>Application</Channel>
    <Computer>REDACTED</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Transport Mail Database</Data>
    <Data>Microsoft.Isam.Esent.Interop.EsentTransactionTooLongException: Too many outstanding generations between JetBeginTransaction and current generation.
   at Microsoft.Isam.Esent.Interop.Api.JetSetColumn(JET_SESID sesid, JET_TABLEID tableid, JET_COLUMNID columnid, Byte[] data, Int32 dataSize, Int32 dataOffset, SetColumnGrbit grbit, JET_SETINFO setinfo)
   at Microsoft.Exchange.Transport.Storage.DataStreamImmediateWriter.Write(Int64 position, Byte[] data)</Data>
  </EventData>
</Event>

Then

Log Name:      Application
Source:        MSExchange TransportService
Date:          09/07/2015 01:48:31
Event ID:      1040
Task Category: ProcessManager
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      OURSERVER
Description:
 The existing worker process HasExisted value before calling CloseProcess is True 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange TransportService" />
    <EventID Qualifiers="16388">1040</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-09T00:48:31.000000000Z" />
    <EventRecordID>6852163</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OURSERVER</Computer>
    <Security />
  </System>
  <EventData>
    <Data>True</Data>
  </EventData>
</Event>

Log Name:      Application

Source:        MSExchange TransportService

Date:          09/07/2015 01:48:31

Event ID:      1022

Task Category: ProcessManager

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      OURSERVER

Description:

Worker process with process ID 16052 requested the service to be stopped.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange TransportService" />

    <EventID Qualifiers="16388">1022</EventID>

    <Level>4</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-07-09T00:48:31.000000000Z" />

    <EventRecordID>6852164</EventRecordID>

    <Channel>Application</Channel>

    <Computer>OURSERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data>16052</Data>

  </EventData>

</Event>

Log Name:      Application

Source:        MSExchange TransportService

Date:          09/07/2015 01:48:31

Event ID:      1033

Task Category: ProcessManager

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      OURSERVER

Description:

A worker process encountered transient problems and requested to be restarted in 5 minutes.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="MSExchange TransportService" />

    <EventID Qualifiers="49156">1033</EventID>

    <Level>2</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2015-07-09T00:48:31.000000000Z" />

    <EventRecordID>6852165</EventRecordID>

    <Channel>Application</Channel>

    <Computer>OURSERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data>5</Data>

  </EventData>

</Event>

How much free disk space is there on the drive?

Hi Ed,

40Gb on C (184 Gb total) OS

685Gb on D (1.46Tb total) Databases

46.3Gb on E (149Gb Total) <- transport queue, transport logs, and transaction logs.

Thanks

Nick

Now I have posted this to the forum, a couple of useful suggestions popped up on the left hand side.. which has lead me to running the command

get-messagetrackinglog

and filtering for objects over 30MB between  the hours 00:27:00 and 00:30:00

This gives me multiple entries for a huge email (1.8Gb!).

This has got to be the cause of the trouble. 

Any ideas how I can get rid of it?

The transport service will only stay up for a minute or so, and takes 3-5 minutes to start!

You could reduce the maximum message size for a while.

Hi,

This event arise because of vital resources, such as available hard drive space and memory, are under pressure, it prevents the system resources from being completely overwhelmed, and the Exchange server tries to process the existing messages before accepting any new messages. For your reference: https://technet.microsoft.com/en-us/library/bb201658%28v=exchg.150%29.aspx

We can configure message size limitation in global setting, connector, server and mailbox level, also transport rule can archive this goal. Please refer to: https://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx

Thanks

A call to MS PSS very quickly got us the specific solution for us. The pressure was being caused by some very large emails in a number of outboxes overwhelming the transport service database.

The solution was  (in addition to putting in sane limits as suggested by Ed) to query all mailboxes for the size of their outbox, and then delete any mail items that were too large. 

Thanks for all your help.

Nick

Thanks for reporting back.  Glad you got it sorted out.