Article ID: 917321 - Last Review: October 9, 2011 - Revision: 2.0 Errors are logged in the Secedit.log file when you use the Secedit.exe command-line utility to apply a local Group Policy object in Windows 2000
On This PageSYMPTOMSOn a computer that is running Microsoft Windows 2000, you
use the Secedit.exe command-line utility to apply a local Group Policy object
(GPO). You apply this GPO from an .inf file. When you do this, the Secedit.exe command-line utility stops
processing registry permissions. When this problem occurs, errors that resemble the following are logged in the Secedit.log file: ERROR_MORE_DATA CAUSEThis
problem occurs because the Secedit.exe command-line utility uses the RegQueryInfoKey function to obtain the SubKeyLen variable. The SubKeyLen variable
is used to allocate the buffers for the subkey name that is returned by the RegEnumKeyEx function. Instead, the Secedit.exe command-line utility
should use the maximum buffer size for a key name to allocate these buffers. RESOLUTIONHotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, you must have Windows 2000 Service Pack 4 (SP4) installed.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Collapse this table
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATION For more information
about how hotfix packages are named, click the following article number to view
the article in the Microsoft Knowledge Base: 816915
(http://support.microsoft.com/kb/816915/
)
New file naming schema for
Microsoft Windows software update packages
For more information, click the
following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Other Resources Other Support Sites
CommunityArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top