ESE Error event id 623, Exchagne 2007 crash
MSExchangeIS (4576) Storage Group 6: The version store for this instance (4) has reached its maximum size of 511Mb. 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: 0x000007FFFFE1B8A0 Session-context: 0x00000000 Session-context ThreadId: 0x0000000000000E7C Cleanup: 1 We are having this problem with Exchange 2007 servers from 3 days and there is no solution. Microsoft has thsi Level 1 Ticket and yet to come up with good reason why it is happening.Every 4 to 10 hours all resources on the server get hang and users cannot access the server. We have been looking at the blogs from Microsoft for any solution or reason but no particular reason is identified.We have Cisco Meeting PlaceCisco Unity 5 Blackberry Enterprise server EMC email xtendar also implimentedall integrated with exchange.We have roll up 1 and 2 are applied for exchange.One reason a tech come up was that our search folders have high number of items, Microsoft want like 5000 we have lot of users with 30000 and above. Anyone have any idea please share with us.
January 21st, 2009 5:15am

Hi Akram,We had similar issue on Exchange 2003 and ended up decreasing the mail items in folders less than 5000. We had many mailboxes with 80,000 and above. Performance was impacted when any search request comes to Exchange for a folder which has higher mail item, Exchange becomes irresponsive and local delivery queue is also being build up.Here are some of the good start for planning large mailboxes in Exchange 2007 and you can implement MRM to manage contents...White Paper: Planning for Large Mailboxes with Exchange 2007http://technet.microsoft.com/en-us/library/cc671168.aspxUnderstanding the Performance Impact of High Item Counts and Restricted Viewshttp://technet.microsoft.com/en-us/library/cc535025.aspx- Since you are at rollup 2, suggest you to update it to rollup 5 which is the latest available.Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
Free Windows Admin Tool Kit Click here and download it now
January 21st, 2009 10:37pm

Have you read this article from the Exchange team:http://msexchangeteam.com/archive/2008/05/23/448923.aspx
January 22nd, 2009 12:27am

Hi, On the storage group object in AD, set the attribute msExchESEparamMaxVerPages to 16384. The setting is in 16k units on 32-bit and in 32k units on 64-bit. Thus, on 32-bit, the max version store size will be 256Mb, and on 64-bit, the max version store size will be 512Mb. So for instance, if you have SP1 and you figure out that 512Mb is not large enough for whatever reason, then you could set msExchESEparamMaxVerPages to 32768 to yield a 1Gb max version store size (on 64-bit). You can follow the steps in below article to modify the value on msExchESEparamMaxVerPages. Though it is an article for Exchange 2003,method in the article could be used for Exchange 2007 too. You cannot recover some public folders in Exchange Server 2003 Outlook Web Access, and the information store becomes unavailable to users http://support.microsoft.com/kb/922501 Besides, please apply the latest update for Exchange 2007 sp1. Regards, Xiu
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2009 9:38am

If the issue cannot be solved bychanging msExchESEparamMaxVerPages values,then please feel free to let me know.We may suspect someting on Cisco Unity 5.0Regards,Xiu
January 22nd, 2009 10:29am

We have a similar issue on Exchange 2003 and use Unity as well. This error appears after the store is restarted. Is there any new information regarding this?
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2010 10:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics