Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Events 2104 and 2147 are logged in an Exchange Server 2007 CCR environment


View products that this article applies to.

Symptoms

In a Microsoft Exchange Server 2007 cluster continuous replication (CCR) environment, the following two events are logged on the cluster passive node:

ID: 2104
Level: Error
Provider: MSExchangeRepl
Machine: server.domain.com
Message: Log file action LogCopy failed for storage group Server\StorageGroup. Reason: CreateFile(\\server\SGGuid$\logfile) = 2

ID: 2147
Level: Error
Provider: MSExchangeRepl
Machine: server.domain.com
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.

↑ Back to the top


Cause

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.

↑ Back to the top


Workaround

To work around this issue, follow these steps on the passive nodes that are experiencing the errors:
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then select the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters
  3. Set the following DWORD values to 0:
    • FileInfoCacheLifetime
    • FileNotFoundCacheLifetime
    • DirectoryCacheLifetime

    Note
    If these DWORD values are not present, create them manually.
  4. Restart the passive nodes.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: KB975255, kbsurveynew, kbexpertiseinter, kbqfe, kbhotfixrollup

↑ Back to the top

Article Info
Article ID : 975255
Revision : 2
Created on : 4/29/2013
Published on : 4/29/2013
Exists online : False
Views : 452