Article ID: 975255 - View products that this article applies to.
In a Microsoft Exchange Server 2007 cluster continuous replication (CCR) environment, the following two events are logged on the cluster passive node:
Message: Log file action LogCopy failed for storage group Server\StorageGroup. Reason: CreateFile(\\server\SGGuid$\logfile) = 2
Message: There was a problem with 'nodename', which is an alternate name for 'nodename'. The list of aliases is now 'nodename', and the alias 'was' removed from the list. The specific problem is 'CreateFile(\\nodename\sgguid\log) = 2'.
These event messages indicate that the replication is broken. However, you may find that several other event messages indicate that the replication completed successfully during the same period.
This issue occurs because the lock that locked the log file when the copy operation started was temporary. After the lock was released, the copy operation finished. Therefore, event 2104 and event 2147 should not have been logged.
To work around this issue, follow these steps on the passive nodes that are experiencing the errors:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about this issue, see the following Microsoft TechNet blog post:
MSExchangeRepl 2147 / MSExchangeRepl 2104 / MSExchangeRepl 2127 occurring on Windows 2008 or Windows 2008 R2 with Exchange 2007 Cluster Continuous Replication (CCR)
Article ID: 975255 - Last Review: April 29, 2013 - Revision: 2.0