HiWe are running Exchange 2003 SP2. Our max message size is configured as 10 MB.Occasionally, we get Error 623 entries in our Exch server and need to reboot. Information Store (6276) Storage Group 1: The version store for this instance (3) 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: 0xB8336A60 Session-context: 0x00000000 Session-context ThreadId: 0x000021D8 Cleanup: 0 This is followed by logs of Error 1022'sLogon Failure on database "Storage Group 1\Mailbox Store 1 (Mailserver)" - Windows 2000 account Domain\user1; mailbox /o=OU/ou=OU/cn=RECIPIENTS/cn=User1.Error: -1066 From what I can see, this maybe due to large messages entering our mail system.Couple of questions;a) Am I correct in thinking that the Information Store will process -all- messages, regardless of size? It is only when the message gets to the point of delivery that the message size is checked? This could lead to the Version Store running out of space?b) If the above is correct, is there any way to prevent this?c) How does this differ in Exchange 2007 where all the different roles are on different servers?d) Is there anyway to track down this message?e) Could this message be coming from a user's Outlook on our network (i.e. the IS is processing it on the way out) as well as coming into an Exchange server?f) What sort of message size could cause this?Any help appreciated!!

Hi, I suggest you take a look regarding at following article regarding the event: Troubleshooting Version Store issues - JET_errVersionStoreOutOfMemory http://msexchangeteam.com/archive/2006/04/19/425722.aspx Mike