Moving to Exchange 2010 SP3 ? pay attention to “Logfile ‘f:logsDBEnn.log’ is generation 2024; however the expected generation is 2004”

I have seen the following behavior in certain customer environments, and this is due to the 8DOT3 name creation enforcement.

If 8DOT3 name creation is enabled on volumes that contain transaction logs in Exchange Server 2010 SP3, this can cause invalid transaction logs to be returned as part of a findfile query during the databases' activation process. This causes the databases to be sent to a failed state because of an invalid sequence in the transaction log generation numbers.


The following KB has the full details for this issue and its workarounds: 


Comments (2)
  1. Anonymous says:

    With the recent releases of Exchange Server 2013 RTM CU1, Exchange 2013 sizing guidance, Exchange 2013 Server Role Requirements Calculator, and the updated Exchange 2013 Deployment Asistant, on-premises customers now have the tools you need to begin designing
    and performing migrations to Exchange Server 2013. Many of you have introduced Exchange 2013 RTM CU1 into your test environments alongside Exchange 2010 SP3 and/or Exchange 2007 SP3 RU10, and are readying yourselves for the production migrations.
    There’s one particular Exchange 2010 design choice some customers made that could throw a monkey wrench into your upgrade plans to Exchange 2013, and we want to walk you through how to mitigate it so you can move forward. If you’re still in the design or deployment
    phase of Exchange Server 2010, we recommend you continue reading this article so you can make some intelligent design choices which will benefit you when you migrate to Exchange 2013 or later.

  2. Anonymous says:

    For many IT professionals, PowerShell has come to be the best thing since sliced bread. In this post, Shamsher Dhanoa, our Senior PFE from the US East region, walks us through one more example of how PowerShell is very useful in safely automating tedious
    tasks like altering tons of configuration files.

Comments are closed.

Skip to main content