[ExchangeList] Re: Running out of transaction log generations

  • From: "Michael B. Smith" <michael@xxxxxxxxxxxxxxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 24 Dec 2007 10:42:25 -0500

http://www.msexchange.org
-------------------------------------------------------This happens when a 
message containing an X-* header is promoted to MAPI
from the STM file in Exchange 2003. That's the only time it happens within
Exchange itself.

The default limit for named properties in a store is set to 16K and the hard
limit is 32K.

MFCMAPI allows you to examine the named properties contained in a store.
This may allow you to determine the source.

To eliminate the named properties, move the mailbox to another store.

Regards,

Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Kern
Sent: Tuesday, December 18, 2007 8:04 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Running out of transaction log generations

http://www.msexchange.org
-------------------------------------------------------Thanks but I started
and ended there.

Its a good reference for recovering from exhausting the qouta but
doesn't help much with determining why you got (or keep) getting there
to begin with.
I did what the recomendation was and 6 weeks later i have about 2000
named props per store and hitting the trans log limit

And speaking of  trans logs, I'm just wondering if its normal to run
out of generations as quickly as I have.

I'd say there are about 100,000 emails journalED  to these mailboxes per
day.

Thanks



On Dec 18, 2007 7:48 PM, Michael B. Smith
<michael@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> http://www.msexchange.org
> -------------------------------------------------------This is a good
place to start:
>
> http://technet.microsoft.com/en-us/library/bb851495.aspx
>
> (the text applies to Exchange 2003 as much as to Exchange 2007)
>
> I can't imagine where you are getting those properties from. I've no clue.
>
> Wrapping transaction logs is completely dependent on how much i/o occurs.
I
> wouldn't be surprised to wrap quickly based on a volatile environment.
>
> Regards,
>
> Michael B. Smith
> MCSE/Exchange MVP
> http://TheEssentialExchange.com
>
>
>
> -----Original Message-----
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Kern
> Sent: Tuesday, December 18, 2007 6:28 PM
> To: ExchangeList
> Subject: [ExchangeList] Running out of transaction log generations
>
> http://www.msexchange.org
> -------------------------------------------------------I'm have an
exchange
> 2k3 sp2 server which is used only to house
> journaling mailboxes (about 6 dedicated to 6 servers housing ~500
> users each).
>
> This server keeps reaching the trans log # limit every 6-8 weeks.
> It also reached the named props quota on 4 db's.
>
> After recreating the db's, the named props is back up to ~20000 (dont
> know if this is high) and i am getting event id's warning that the
> trans log limit is approaching.
>
> Is this normal for a server with only mailboxes that are being
> journaled to (a mailbox manager process runs every nite to purge the
> deleted items on these mailboxes, i guess increasing the # of
> transactions)
> should i be worried?
>
> is there a way to tell what is creating all the named props?
>
> Thanks very much
> -------------------------------------------------------
> List Archives: http://www.freelists.org/archives/exchangelist/
> MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
> MSExchange Articles and Tutorials:
> http://www.msexchange.org/articles_tutorials/
> MSExchange Blogs: http://blogs.msexchange.org/
> -------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> -------------------------------------------------------
> To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
>
> -------------------------------------------------------
> List Archives: http://www.freelists.org/archives/exchangelist/
> MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
> MSExchange Articles and Tutorials:
http://www.msexchange.org/articles_tutorials/
> MSExchange Blogs: http://blogs.msexchange.org/
> -------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> -------------------------------------------------------
> To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
>
-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/  
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp 
MSExchange Articles and Tutorials:
http://www.msexchange.org/articles_tutorials/ 
MSExchange Blogs: http://blogs.msexchange.org/ 
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx 


-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/  
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp 
MSExchange Articles and Tutorials: 
http://www.msexchange.org/articles_tutorials/ 
MSExchange Blogs: http://blogs.msexchange.org/ 
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: