Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Errors when you have a large "Folder Redirection" policy settings file in Windows Vista, in Windows 7, in Windows Server 2008, or in Windows Server 2008 R2
Article ID: 978098 - View products that this article applies to.
Consider the following scenario:
When you open the Folder Redirection policy settings, you find that the folders do not display the settings. Instead, the folders are displayed as Not configured.
When you try to show the settings of the Folder Redirection policy in the Group Policy Management Console (GPMC), you receive the following error message in the Folder Redirection Policy Details section:
Note for Symptom 1 and for Symptom 2
An unknown error occurred while data was gathered for this extension. Details: FRSettingRead failed with -2147467259
These symptoms occur on policies that are created and that are populated by using the Local Group Policy Editor on a computer that is running Windows Server 2003, Windows Server 2008, or a version of Windows that is newer than Windows Server 2008.
When you try to apply the new Folder Redirection policy settings to a domain user account on a computer that is running Windows Vista or a newer version of Windows, the settings are not applied. Additionally, you may receive the following error message in the Application log:
Log Name: Microsoft-Windows-GroupPolicy/Operational
Event ID: 7016
Task Category: None
Completed Folder Redirection Extension Processing in xxx milliseconds.
<Data Name="CSEExtensionName">Folder Redirection</Data>
These issues occur because of two limitations in the system API that the Folder Redirection engine uses to read the .ini files from SYSVOL.
Cause of Symptom 1 and Symptom 2
For an .ini file that was created in Windows Vista or in a newer version of WindowsThese issues occur because the Folder_Redirection section of the .ini files is larger than 32,767 characters. However, the limit for the combined SID list for all folders is 32,767 characters. This limit is encountered when the GetPrivateProfileSection API is used to read the section.
Note If the SIDs typically have 48-50 characters, you can have about 670 SIDs in a policy for all folders before this issue occurs.
For an .ini file that was created in Windows Server 2003These issues occur because the limit for the number of groups for each redirected folder in a policy is exceeded. This limit depends on the length of the SID string that represents the group and also on the length of the redirection path. For example, you can have about 230 groups for a single folder if a SID string is about 48-50 characters, and if the UNC path of the folder is 80 characters.
Cause of Symptom 3This issue occurs because of a limit of the GetPrivateProfileString API that is used to read this section.
The list of groups is stored as a string of SIDs in an .ini file. When the list exceeds 32,767 characters, this problem occurs. Each string that represent a SID in the .ini file is typically about 48-50 characters. Therefore, you can have around 300 entries for each redirected folder.
To work around these problems, split the policy into smaller policies. Make sure that the total size of each policy file is smaller than the 32,767 character limit.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The Folder Redirection policy settings use a new .ini file format in Windows Vista and in newer versions of Windows to support new options when you apply the settings. This technology lets you redirect more folders compared to the Folder Redirection policy settings in Windows Server 2003.
For more information about the Folder Redirection feature, visit the following Microsoft TechNet Web site:
General information about the Folder Redirection feature
Article ID: 978098 - Last Review: May 14, 2010 - Revision: 1.0