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: