Microsoft KB Archive/933789

= FIX: Error message when you use the ADsSecurityUtility object in VBScript code on a Windows Server 2003-based computer: &quot;Permission denied&quot; =

Article ID: 933789

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
On a Microsoft Windows Server 2003-based computer, when you use the ADsSecurityUtility object to write a security descriptor back to a registry key in VBScript code, you receive the following error message:

Script:

Line:

Char:

Error: Permission denied

Code: 800A0046

Source: Microsoft VBScript runtime error



CAUSE
This problem occurs because the ADsSecurityUtility object does not open the registry key by using the appropriate credentials.



Hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
You must have Windows Server 2003 installed before you apply this hotfix.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The 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.

Windows Server 2003, Itanium-based editions


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



Steps to reproduce the problem
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.   Create a .vbs file that contains the following code example. set sdutil = createobject(&quot;ADsSecurityUtility&quot;)

CONST ADS_PATH_REGISTRY = 3 CONST ADS_SD_FORMAT_IID = 1

Set sd = sdUtil.GetSecurityDescriptor(&quot;HKEY_CURRENT_USER\test&quot;, ADS_PATH_REGISTRY, ADS_SD_FORMAT_IID) sdUtil.SetSecurityDescriptor &quot;HKEY_CURRENT_USER\test&quot;, ADS_PATH_REGISTRY, sd, ADS_SD_FORMAT_IID  Click Start, click Run, type regedit, and then click OK. Right-click HKEY_CURRENT_USER, click New, and then click Key. Type test, and then press ENTER. Double-click the file that you created in step 1.</li></ol>

Keywords: kberrmsg kbbug kbfix kbqfe kbcode kbpubtypekc kbhotfixserver kbwinserv2003postsp2fix KB933789

-

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

© Microsoft Corporation. All rights reserved.