OL2002: Insufficient Rights to Browse the Directory on an LDAP Server

View products that this article applies to.

This article was previously published under Q301393

Expand all | Collapse all

SYMPTOMS

When you try to access directory information on a Lightweight Directory Access Protocol (LDAP) server, you may receive the following error message:

Insufficient rights to browse directory.

Back to the top

CAUSE

This problem can be caused by the Virtual List View feature of Outlook 2002.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

307841 (http://support.microsoft.com/kb/307841/EN-US/ ) OFFXP: How to Obtain the Latest Office XP Service Pack

The English version of this fix should have the following file attributes or later:

  Date            Time         Size     File name     
  -------------------------------------------------------
  09-28-2001      08:21	   361 KB    Olkintl.msp
  09-28-2001      08:22	 1,876 KB    Olkintl_Admin.msp
  10-12-2001      13:47	     5 KB    Hotfix.txt

After the hotfix is installed, the following files will have the listed attributes or later:

   Date       Time   Version        Size         File name      
   --------------------------------------------------------
   9/25/2001  16:31  10.0.3318.0    108,872     Emablt32.dll  	
   8/02/2001  09:12  10.0.3131.0    194,888     Emsabp32.dll
   8/12/2001  20:10  10.0.3311.0    538,952     Emsmdb32.dll
   7/19/2001  13:19  10.0.3117.0    125,256     Emsui32.dll
   9/12/2001  20:10  10.0.3311.0    850,248     Msmapi32.dll
   8/09/2001  13:27  10.0.3207.0    526,664     Mspst32.dll
   9/12/2001  20:10  10.0.3311.0    735,560     Outex.dll
   5/18/2001  09:37  10.0.2915.0  1,972,552     Outllibr.dll

Back to the top

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 Microsoft Office XP Service Pack 1.

Back to the top