I noticed last night that I received the below posted event on my Exchange 2003 Enterprise server. The MS KB article I found only references this to Exchange 2000, so I am unsure of how to proceed. Is this something I should be concerned with? If I need to provide more information, please let me know. Event ID Details. Information Store (5624) First Storage Group: Log sequence numbers for this instance have almost been completely consumed. The current log generation is 943000 (0x000E6398) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 105559 (0x00019C57) log generations left to be used. To begin renumbering from generation 1, the instance must be shutdown cleanly and all log files must be deleted. Backups will be invalidated.

You didn't post the link to the KB article to which you are referring. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Herschel Jones" wrote in message news:d0d07332-cf15-4deb-bcc8-1a7ccce223d8... I noticed last night that I received the below posted event on my Exchange 2003 Enterprise server. The MS KB article I found only references this to Exchange 2000, so I am unsure of how to proceed. Is this something I should be concerned with? If I need to provide more information, please let me know. Event ID Details. Information Store (5624) First Storage Group: Log sequence numbers for this instance have almost been completely consumed. The current log generation is 943000 (0x000E6398) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 105559 (0x00019C57) log generations left to be used. To begin renumbering from generation 1, the instance must be shutdown cleanly and all log files must be deleted. Backups will be invalidated. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Wed, 21 Jul 2010 12:48:21 +0000, Herschel Jones wrote: > > >I noticed last night that I received the below posted event on my Exchange 2003 Enterprise server. The MS KB article I found only references this to Exchange 2000, so I am unsure of how to proceed. Is this something I should be concerned with? If I need to provide more information, please let me know. The process is the same. In a nutshell, make sure the dismounted databases in the storage group in a consistent state, remove the .log and .chk files from the directory, remount the databases in the storage group. When they're all mounted, make a backup -- now -- don't wait. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP