Article ID: 826819 - Last Review: July 24, 2007 - Revision: 9.9 The server stops responding and an access violation occurs in Lsass.exe when the server reloads certain policy parameters
On This PageSYMPTOMSWhen the domain controller reloads certain policy parameters for Lightweight Directory Access Protocol (LDAP) policy objects or for Directory Server Agent (DSA) objects because of originating or replicated modifications, the server may stop responding, and an access violation may occur in Lsass.exe. CAUSEThis problem may occur if a Simple Authentication and Security Layer (SASL) connection to the server exists at the time of the reload operation and if a NULL argument, when it is passed in as a ContextHandle parameter in the SaslFindContext() function, is handled correctly. As a result, a Scheduler thread is blocked, and an access violation occurs on Lsass.exe. 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.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, contact 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.PrerequisitesNo prerequisites are required.Restart requirementYou must restart your 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 tool in Control Panel.Windows Server 2003, Standard Edition and Windows Server 2003, Enterprise EditionDate Time Version Size File name Platform --------------------------------------------------------------- 16-Mar-2005 01:43 5.2.3790.288 64,512 Secur32.dll x86 Windows Server 2003, Enterprise Edition for Itanium-based SystemsDate Time Version Size File name Platform ----------------------------------------------------------------- 16-Mar-2005 00:35 5.2.3790.288 170,496 Secur32.dll IA-64 16-Mar-2005 00:43 5.2.3790.288 59,392 Wsecur32.dll x86 STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






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