OL2k3 LDAP No Such Object Error

[btenpenny]

After changing the search base on several machine to relfect our email
provider's new schema, I get "No Such Object. Possibly your search base is
invalid" errors when the user sends email. The odd thing is that they search
strings are correct. Actually doing a LDAP query using the search base
(through find) produces the correct results, meaning that the bases are not a
typo problem (at least that's how it seems to me). Most of the machines we
have changed DO NOT exibit this problem, but a couple of them do. I can't
find any hints to this via Google or or support.microsoft.com.

Thanks in advance!

 

[AndreasRoeder]

After changing the search base on several machine to relfect our email
provider's new schema, I get "No Such Object. Possibly your search
base is invalid" errors when the user sends email. The odd thing is
that they search strings are correct. Actually doing a LDAP query
using the search base (through find) produces the correct results,
meaning that the bases are not a typo problem (at least that's how it
seems to me). Most of the machines we have changed DO NOT exibit this
problem, but a couple of them do. I can't find any hints to this via
Google or or support.microsoft.com.

Thanks in advance!

Hi,
try the following link to solve your problem

http://wiscsoftware.wisc.edu/wisc/techsub/microsoft/outlook_xp_ldap_patch/patch_inst.html

 

[btenpenny]

Thanks for the link, buit I don't think that's the answer. The file they list
doesn't appear to be available any longer, and it's for OfficeXP and we're in
Office 2k3. I'm pretty sure that the problem they were attempting to solve
had something to do with the VLV issues that Outlook continues to have, but I
don't think this is a VLV-related problem.

I used ethereal to capture traffic on the wire when I send an email from one
of the machine with the problem, and the results were interesting. The
machine that are giving an error are still issuing requests using the OLD
search base. I can't find any instance of the oild search base in the
registry, the only two entries are the one with the new search base in them.
DOes anyone know if there is some secret place the Outlook2k3 caches the
search base it uses when quering the LDAP server during a send?

THANKS IN ADVANCE!

 

[btenpenny]

OK! We figured it out. Outlook keeps a nickname file (outlook.nk2 in our
case) that it uses to fill in the address when you type the name in the To:
field. That file contains the ldap query strings for those addresses. For
some reason, some of the machines were still trying to use the old query
strings, while others updated correctly. Deleting the nk2 file fixed the
problem, although they'll have to rebuild their name lists.

 

[Brian Tillman]

OK! We figured it out. Outlook keeps a nickname file (outlook.nk2 in
our case) that it uses to fill in the address when you type the name
in the To: field. That file contains the ldap query strings for those
addresses. For some reason, some of the machines were still trying to
use the old query strings, while others updated correctly. Deleting
the nk2 file fixed the problem, although they'll have to rebuild
their name lists.

Next time, just delete the offending entry.

 

[btenpenny]

There isn't an "offending entry" per se. It generates an error for every (or
nearly so) name in the file.