mail flow stopped on HT servers, transport DBs maxxing out
Mike Bonvie
Event Type: Error
Event Source: ESE
Event Category: Transaction Manager
Event ID: 623
Date: 2/25/2008
Time: 5:53:03 AM
User: N/A
Computer: BIL-EXC6-02
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: 0x0000000005217400
Session-context: 0x00000000
Session-context ThreadId: 0x00000000000014F8
Cleanup: 1
For more information, click http://www.microsoft.com/contentredirect.asp.
++
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Storage
Event ID: 17017
Date: 2/25/2008
Time: 5:53:03 AM
User: N/A
Computer: BIL-EXC6-02
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)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
+++
2003 Server STD R2 SP2
2 Exchange 2007 SP1 servers
roles: HT, UM, CAS
Backpressure wasn't an issue as theres over 50GB free space on the C:\ drive
The transport DB\log locations are the default:
C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue
queues on both HT servers were clogged, there was a gigantic email being
processed at the time on one server, that would likely be part of the
problem, but the issue happened on both HT-role servers
We worked around this by:
stopping the MS Exchange Transport service
Renaming the queue folder: C:\Program Files\Microsoft\Exchange
Server\TransportRoles\data\Queue
Starting the MS Exchange Transport service
This automatically recreated the queue folder, DBs & logs
Is there a process to increase the quota of the Transport Mail Database
beyond 249MB?
Will backup programs be able to flush these logs?
What's the best way to prevent the DB\logs from growing out of control
again?
Jamestechman
default value is and would prob consult with MS before changing it. I
would probably leave it as it and I would only increase this if the
root cause was performance rather than an isolated triggered event.
Anything such as a large message or performing tasks on a large MB can
produce this especially if you have IO issues. Before I do anything I
would look into how your current IO is.
I remember running into this on an Exchange 2003 box where an admin
was running inbox rules on the postmaster account once a month and
would hang the store. However; this was due to a combination of large
MB size and already poor IO.
Troubleshooting Version Store issues - JET_errVersionStoreOutOfMemory
http://msexchangeteam.com/archive/2006/04/19/425722.aspx
James Chong (MVP)
MCITP | EMA; MCSE | M+, S+, Security+
msexchangetips.blogspot.com
On Feb 25, 9:38 am, "Mike Bonvie" <m...@d.net> wrote:
> Event Type: Error
> Event Source: ESE
> Event Category: Transaction Manager
> Event ID: 623
> Date: 2/25/2008
> Time: 5:53:03 AM
> User: N/A
> Computer: BIL-EXC6-02
> 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: 0x0000000005217400
> Session-context: 0x00000000
> Session-context ThreadId: 0x00000000000014F8
> Cleanup: 1
>
> For more information, clickhttp://www.microsoft.com/contentredirect.asp.
>
> ++
>
> Event Type: Error
> Event Source: MSExchangeTransport
> Event Category: Storage
> Event ID: 17017
> Date: 2/25/2008
> Time: 5:53:03 AM
> User: N/A
> Computer: BIL-EXC6-02
> 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)
>
> For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.
Mike Bonvie
"Jamestechman" <jamest...@gmail.com> wrote in message
news:593c34f0-bc89-4f1f...@41g2000hsc.googlegroups.com...