An Invalid LDAP Request May Cause Inetinfo.exe to Stop (268132)



The information in this article applies to:

  • Microsoft Site Server 3.0

This article was previously published under Q268132

SYMPTOMS

The Lightweight Directory Access Protocol (LDAP) server may generate an access violation when the server processes an invalid LDAP client request. This causes the Inetinfo.exe process to stop.

CAUSE

When processing an LDAP request, the LDAP server builds an LDAP response structure. If the LDAP request is not correctly formatted, some fields may not be correctly initialized and may have some random values. Under rare circumstances, this may cause the LDAP server to crash.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Site Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date      Time     Version     Size    File name     Platform
   -------------------------------------------------------------
  07/06/2000  10:14p  7.0.1313.0  336,656 ldapsvc.dll    Alpha
  07/06/2000  10:14p  7.0.1313.0  229,264 ldapsvc.dll    x86
				

STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB268132