Global address lookup issue

[Bill Bryson]

I'm using Entourage 13.0 (EWS) and I've discovered that the auto fill-in
feature (address lookup) does not display entries from the global address
book if there happens to be a similar name in my personal address book. For
example, I have several Smiths in my personal address book so NO Smiths are
displayed at all for Directory. When I click the rolex symbol to the right
of the To, I can switch to the GAL and find names. The problem has to do
with the auto-fill menu that pops down as you type in an email address on
the To: line. However, there are names that are not in my personal address
book that will pop-down as listed from the Directory. There is
inconsistency in how the auto-fill in working in EWS. I noticed that
another user reported that it was also taking longer to auto-fill as well.
I don't know if these two issues are related or not.

Very frustrating that I can't determine when names will appear on the To
line for auto-fill.

I've tested with several installations and different identities. I also
tested with identities that I imported and those that I created from
scratch.

Anyone else experiencing with the address auto-fill pop-down menu not
retrieving names properly?

Bill Bryson

 

[Adam Bailey]

I'm using Entourage 13.0 (EWS) and I've discovered that the auto fill-in
feature (address lookup) does not display entries from the global address
book if there happens to be a similar name in my personal address book. For
example, I have several Smiths in my personal address book so NO Smiths are
displayed at all for Directory. When I click the rolex symbol to the right
of the To, I can switch to the GAL and find names. The problem has to do
with the auto-fill menu that pops down as you type in an email address on
the To: line. However, there are names that are not in my personal address
book that will pop-down as listed from the Directory.

I don't use EWS, but from my experience Entourage *does not*
autocomplete from the GAL period. It will fill from your personal
address book, and from the Most Recently Used addresses list (and this
is likely what you are seeing). To get it to recognize a name from the
GAL, you need to use the "Check Names" button.

 

[William Smith [MVP]]

I don't use EWS, but from my experience Entourage *does not*
autocomplete from the GAL period. It will fill from your personal
address book, and from the Most Recently Used addresses list (and this
is likely what you are seeing). To get it to recognize a name from the
GAL, you need to use the "Check Names" button.

While on the same network as the Exchange Server and connected to a
back-end Exchange Server, Entourage will allow for browsing the GAL.
However, this is not possible while connected to an Outlook Web Access
(OWA) address. A manual search is possible still, just not browsing.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[Adam Bailey]

While on the same network as the Exchange Server and connected to a
back-end Exchange Server, Entourage will allow for browsing the GAL.

Browsing, yes. But autocomplete, no.

 

[Bill Bryson]

Adam,

I neglected to mention that this lookup on the To: (autocomplete/browse)
works with the non-EWS versions of Entourage.

In the non-EWS, the matches from the Contacts/Recent are listed first on the
drop-down in the TO: line followed the Directory and the matches from the
GAL.

With Entourage - Web Services (13.0), the directory portion does appear
except if I happen type in a portion of a name that does not match anything
in my Contacts.

 

[Bill Bryson]

I've also verified this on several EWS installs so it is not unique to a
single Identity.

 

[Bill Bryson]

After more testing, I discovered that the pop-down works for most cases but
fails to pop down on others. I am entering the name in the order of last,
first. It appears that the drop down will never display more than 6-7
matches. However, some combinations of last, first never appear.

I've also discovered that when I click the "Check Names" button when in the
Compose window that I get an error message regardless of what name I've
entered on the TO line as follows:

Am unknown error has occurred in Entourage
LDAP Server Error.

Account name: xxx

Error: -17890

My LDAP server setting is correct because I can access the GAL properly
using the rolex card on the To: line and the "All Users" under Directory
when the Address Book module.

 

[William Smith [MVP]]

Browsing, yes. But autocomplete, no.

This just may be a difference in semantics.

While connected to a back-end server, I can begin entering a name in the
To field of a new message such as "john" and Entourage will retrieve a
list of all matches from the GAL automatically without the need to
perform a manual lookup. As I complete the name "johnso" then it narrows
the list of results until I've either found a unique name or I select a
name. It's similar to the auto-complete of the most recently used list
and the local Address Book.

This isn't "auto-complete" from left to right in the same line, but it
is "auto-complete" in that it's dynamically returning addresses from the
GAL.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[Bill Bryson]

I turned the logging feature on for Entourage Web Services edition. In my
testing, I've determined that that the name lookup fails when the log lists
a record returned with "" somewhere in the data . This character
sequence may appear in the data sequence returned in any of several fields.
A lookup will fail whenever any person's record is returned that has this
sequence in it. For example, when I do a lookup on "Robert Hanna", it fails
because the record for Hannah Roberts is also found and her record returns
data with this character sequence in it. When the lookup succeeds none of
the records returned have this character sequence in the data returned.

I've report this to our Exchange systems people so maybe it is related to
our Exchange server or mailbox structures.

Here are some small snippets from various records returned in the Entourage
log:

<t:Surname>Bryson</t:Surname>

<t:Entry Key="BusinessFax"></t:Entry>

<t:Entry Key="MobilePhone"></t:Entry>

<t:GivenName>Catherine A</t:GivenName>

<t:GivenName>Hannah S</t:GivenName>

 

[Bill Bryson]

I've verified with our Exchange admins that this name lookup issue also
occurs in OWA's lookup process. They identified the issue to be with at
least one record returned in the search results containing a null character.
We believe the null characters came via updates through a third-party tool
that allowed users to update a few of their fields in the the GAL.

We can resolve the issue for a particular record by opening a record with
the null in it using the PowerShell tool and then write it back. The
PowerShell write strips out the null characters. The Exchange admins want
to identify only records with nulls in them and update them. So far I don't
believe they have found a way to do that (the null character being more
elusive).