Blogs - The Official System Center Data Protection Manager Team Blog - Site Home - TechNet Blogs

Blogs

Hotfix: Short File Name & Access Denied issues

  • Comments 1
  • Likes

We recently released a hotfix for an issue related to short file name issues and "access denied" error.

The KB associated with the same is: http://support.microsoft.com/?kbid=906881

 

(906881) - You may receive an "Access Denied" error message when you use the synchronization with consistency check feature in Data Protection Manager and you are running Windows Server 2003.

 

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.

 

This patch is available from PSS (Product Support Services) and can be obtained by calling them (free call). We would recommend installing this hotfix on all DPM servers in production where you are seeing this problem.

 

- Balaji Hariharan (Thanks to Karan)

 

 

 IMPORTANT CLARIFICATION

Please use the updated QFE 911169 instead of 906881. There is no KB article for 911169 yet but it is a super set of the 906881 QFE. This patch is available from PSS (Product Support Services) and can be obtained by calling them (free call).

Please do not use QFE 906881 as you would need to install 911169 anyway. Sorry for the confusion.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • IMPORTANT CLARIFICATION -

    Please use the updated QFE 911169 instead of 906881. There is no KB article for 911169 yet but it is a super set of the 906881 QFE. This patch is available from PSS (Product Support Services) and can be obtained by calling them (free call).

    Please do not use QFE 906881 as you would need to install 911169 anyway.
    - Sorry for the confusion.