Exchasnge 2003 623 Error - Users lose connection to Exchange
Hello,
We are running Exchange 2003 SP2 Enterprise Edition. Late last week we started to see error 623 appearing in the application event log on the server:
Information Store (5292) First Storage Group: 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: 0x7FD303E0
Session-context: 0x00000000
Session-context ThreadId: 0x00001B84
Cleanup: 1
Users are then unable to connect to the Exchange for a period of time. To our knowledge no new applications were installed on the server prior to this error apparing and no changes were made to the Exchange enviornment.
To troubleshoot this problem we have so far done the following
1) Applied all latest Exchange 2003 updates from Microsoft Update site
2) Ran an offline defragmentation of the Exchnage database using ESEUTILS
3) Applied the latest hotfix related to this problem - http://support.microsoft.com/default.aspx?scid=kb;en-us;953952 (this is the only hotfix we have found that is not bundled with SP2)
4) Reapplied Exchange Service Pack 2
5) Changed the maximum size of inbound emails to 10MB
However after performing all of these steps the error is still apparant.
Any advice or help with this matter would be greatly appreciated.
We are running Exchange 2003 SP2 Enterprise Edition. Late last week we started to see error 623 appearing in the application event log on the server:
Information Store (5292) First Storage Group: 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: 0x7FD303E0
Session-context: 0x00000000
Session-context ThreadId: 0x00001B84
Cleanup: 1
Users are then unable to connect to the Exchange for a period of time. To our knowledge no new applications were installed on the server prior to this error apparing and no changes were made to the Exchange enviornment.
To troubleshoot this problem we have so far done the following
1) Applied all latest Exchange 2003 updates from Microsoft Update site
2) Ran an offline defragmentation of the Exchnage database using ESEUTILS
3) Applied the latest hotfix related to this problem - http://support.microsoft.com/default.aspx?scid=kb;en-us;953952 (this is the only hotfix we have found that is not bundled with SP2)
4) Reapplied Exchange Service Pack 2
5) Changed the maximum size of inbound emails to 10MB
However after performing all of these steps the error is still apparant.
Any advice or help with this matter would be greatly appreciated.
Last Comment
ASKER
Hi There,
thanks for the reply. However it is not the database that is getting too big. We are running Enterpise edition and so the database can grow to 8TB...
The error above points to a lack of available memory in the Version Store
Any other ideas?
thanks for the reply. However it is not the database that is getting too big. We are running Enterpise edition and so the database can grow to 8TB...
The error above points to a lack of available memory in the Version Store
Any other ideas?
Doh, sorry about that misread the error.... and moving on to the correct answer :)
This could be a huge message that is trying to process, an inbox with more that 5000 messages in the folder or hidden search folders that aren't purging...
There have been a couple of Exchange Team Blogs on this issue, check out these two links
http://blogs.technet.com/b/exchange/archive/2008/05/23/3405532.aspx
http://blogs.technet.com/b/exchange/archive/2006/04/19/425722.aspx
This could be a huge message that is trying to process, an inbox with more that 5000 messages in the folder or hidden search folders that aren't purging...
There have been a couple of Exchange Team Blogs on this issue, check out these two links
http://blogs.technet.com/b/exchange/archive/2008/05/23/3405532.aspx
http://blogs.technet.com/b/exchange/archive/2006/04/19/425722.aspx
Pls install exmon on the exchange server and monitor for a while to identify the user who does the unusual no. of operations.
Secondly you can also diable AV on the server and restart the IS service and check for the issue.
Secondly you can also diable AV on the server and restart the IS service and check for the issue.
ASKER
Hi There,
Sorry for the delay in getting back to you....
I installed EXMON and everything from there looks fine, also AV has been removed and yet the problem remains. Even when the Exchange Databases are dismounted and the information store started this problem occurs.
I have admitted defeat and raised a call with Microsoft who have looked at it for a couple of days and have not found a solution either.....It is currently in the process of being escalated to their Exchange escalation team which rather frsutratingly takes 2 business days!
Thanks for all your help, if and when we get to a resolution I will post it on here,
Sorry for the delay in getting back to you....
I installed EXMON and everything from there looks fine, also AV has been removed and yet the problem remains. Even when the Exchange Databases are dismounted and the information store started this problem occurs.
I have admitted defeat and raised a call with Microsoft who have looked at it for a couple of days and have not found a solution either.....It is currently in the process of being escalated to their Exchange escalation team which rather frsutratingly takes 2 business days!
Thanks for all your help, if and when we get to a resolution I will post it on here,
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Call to Microsoft
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
http://technet.microsoft.com/en-us/library/aa998066(EXCHG.65).aspx
You may also want to make sure that you backups are working properly and truncating the log files, as well as train your users to delete emails that they don't really need to keep the database size down.
For future reference, exhcnage will log eventlog entries when you reach 90% of the database size limit, so keep your eyes out for that in the future