Select the product you need help with

Win32 API Function GetEffectiveRightsFromAcl() Returns Incorrect Access Mask Value

Article ID: 215367

This article was previously published under Q215367

SYMPTOMS

Security access related to the Win32 API GetEffectiveRightsFromAcl() function does not return the correct Access Mask value. This problem happens after you install Windows NT 4.0 Service Pack 4. Regardless of the Access Mask value, the GetEffectiveRightsFromAcl() function always returns STANDARD_RIGHTS_ALL (0x00000000).

Back to the top | Give Feedback

CAUSE

In Service Pack 4, the security access objects are not mapped correctly in the AccConvertAccessMaskToActrlAccess() function.

Back to the top | Give Feedback

RESOLUTION

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

Windows Service Pack Center
(http://windows.microsoft.com/en-US/windows/downloads/service-packs)
-or-
152734
(http://support.microsoft.com/kb/152734/EN-US/ )
how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

(http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS)

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

152734

(http://support.microsoft.com/kb/152734/EN-US/ )

How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.

Back to the top | Give Feedback