Microsoft KB Archive/906881

= Error message that you may receive when you use the synchronization with consistency check feature in Data Protection Manager and you are running Windows Server 2003: &quot;Access Denied&quot; =

Article ID: 906881

Article Last Modified on 6/28/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft System Center Data Protection Manager 2006

-





SYMPTOMS
When you use the synchronization with consistency check feature in Microsoft Data Protection Manager in Microsoft Windows Server 2003, you may receive the following error message:

Access Denied

Note Synchronization with consistency check is also known as consistency check.



CAUSE
This problem occurs when the following conditions are true:
 * A user is granted permissions to folders or to files that have long file names.
 * The short name of one or more files on the destination server does not match the short name of the corresponding files on the source server.

The problem occurs because, during a consistency check, both the long name and the short name of each file must match. Short names are assigned according to the order in which they are created. Therefore, the short names of the files on the destination server may not match the short names of the files on the source server. For example, this problem occurs in the following scenario:
 * The LongFileName02.txt file is created on the source server. The short name of the LongFileName02.txt file is LongFi~1.txt.
 * The LongFileName01.txt file is created on the source server. The short name of the LongFileName01.txt file is LongFi~2.txt.
 * A consistency check is run. The files are validated by using the long name in alphabetical order. The LongFileName01.txt file is validated first.
 * A LongFileName01.txt file is created on the replica. This file is given the LongFi~1.txt short name.
 * During the next synchronization, the LongFileName02.txt file is created. The short name of this file is LongFi~2.txt.

In this scenario, the short names of LongFileName02.txt and LongFileName01.txt are exchanged.

The next time that you run a consistency check, the synchronization fails because the long name and the short name of each file do not match. Therefore, the replica remains inconsistent with the source server.



RESOLUTION
To resolve this problem, you must install the hotfix that is mentioned in Microsoft Knowledge Base article 911169. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

911169 You receive an error message and the replica state is invalid in Data Protection Manager 2006

Additional query words: replication

Keywords: kbtshoot KB906881

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.