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...