Information Store Log sequence numbers for this instance have almost been completely consumed. The current log generation is 1046690 (0x000FF8A2) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 1869 (0x0000074D) 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. nformation Store Log sequence numbers for this instance have almost been completely consumed. The current log generation is 1046690 (0x000FF8A2) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 1869 (0x0000074D) 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. Is there any workaround on this? Thanks for the help

If you're running Enterprise Edition, or if you have another server, you can move the mailboxes off to another server, then delete the storage group.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "chris keg" wrote in message news:cca6e943-f231-4edb-a9e5-2d1c8280d215...Information Store Log sequence numbers for this instance have almost been completely consumed. The current log generation is 1046690 (0x000FF8A2) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 1869 (0x0000074D) 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. nformation Store Log sequence numbers for this instance have almost been completely consumed. The current log generation is 1046690 (0x000FF8A2) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 1869 (0x0000074D) 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. Is there any workaround on this? Thanks for the help Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Mon, 15 Mar 2010 19:05:25 +0000, chris keg wrote:>Information Store Log sequence numbers for this instance have almost been completely consumed. The current log generation is 1046690 (0x000FF8A2) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 1869 (0x0000074D) 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. nformation Store Log sequence numbers for this instance have almost been completely consumed. The current log generation is 1046690 (0x000FF8A2) which is approaching the maximum log generation of 1048559 (0x000FFFEF), there are 1869 (0x0000074D) 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. Is there any workaround on this? Thanks for the help Ed's given you the work-around. But why would you want to go to thatmuch trouble? The restarting of the log file sequence involves arelatively small amount of downtime.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

ok. what are the steps to correct this problem? thanks

On Tue, 16 Mar 2010 02:12:27 +0000, chris keg wrote:>ok. what are the steps to correct this problem? thanks Did you click on the link in the event log description? It should takeyou here:http://technet.microsoft.com/en-us/library/bb217708(EXCHG.80).aspxRead this, too:http://msexchangeteam.com/archive/2008/07/23/449339.aspxUse the troubleshooting tool to get detailed instructions.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Running out of Log sequence numbers - what to do? (Similar case)James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com