Bug 203617 - Global Address List (GAL) Error loading addressbook.
Global Address List (GAL) Error loading addressbook.
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
All Linux
low Severity urgent
: ---
: ---
Assigned To: Matthew Barnes
Depends On:
  Show dependency treegraph
Reported: 2006-08-22 14:55 EDT by donavan nelson
Modified: 2018-04-11 11:28 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-15 09:39:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output of manually starting /usr/libexec/evolution-data-server-1.6 and trying to access the GAL (several times) (1.58 KB, text/plain)
2006-08-22 14:55 EDT, donavan nelson
no flags Details
screen shot of the gal config page (66.44 KB, image/jpeg)
2006-08-22 15:03 EDT, donavan nelson
no flags Details

  None (edit)
Description donavan nelson 2006-08-22 14:55:17 EDT
Description of problem:

trying to access a global address list configured in the exchange connecter
results in the following dialog box:

"Error loading addressbook.
We were unable to open this addressbook.  This either means you have entered an
incorrect URI, or the server is unreachable."

Version-Release number of selected component (if applicable):
$ rpm -qa |grep evolution

How reproducible:

attempt to access a global adress list not on the same server as the exchange server

Steps to Reproduce:
1.  configure evolution to use exchange
2.  (re) start exchange and login to mail box
3.  access the contacts
4.  attempt to open the "Global Address List"
Actual results:

error above

Expected results:

the ability to search the GAL

Additional info:

I've tested this on two different boxes, both are fully up2date FC5 boxes (as of
todays date).  Same results on both.  One box is i386 and one is x86_64 (running
x86_64 release of FC5).
Comment 1 donavan nelson 2006-08-22 14:55:20 EDT
Created attachment 134660 [details]
output of manually starting /usr/libexec/evolution-data-server-1.6 and trying to access the GAL (several times)
Comment 2 donavan nelson 2006-08-22 15:03:11 EDT
Created attachment 134662 [details]
screen shot of the gal config page

notice how the gal IP address is not the same as the one in the
/usr/libexec/evolution-data-server-1.6 log attatched earlier.
Comment 3 donavan nelson 2006-10-04 12:43:51 EDT
I performed a fresh fc6t3 install and I'm fully yum updated on a i386 box.  I
continue to encounter the same failures.  The IP address of the GAL server is
the same as is used in working RHEL4 installs other in the office use.

[donavan@slackmasterd2 ~]$ uname -a
Linux slackmasterd2 2.6.18-1.2726.fc6 #1 SMP Mon Oct 2 19:27:36 EDT 2006 i686
i686 i386 GNU/Linux
[donavan@slackmasterd2 ~]$ rpm -qa |grep evolution

Please advise if I can provide additonal information.
Comment 4 Brian Wheeler 2006-10-25 10:08:57 EDT
This is true for me also -- The gal:// url is taken from the owa address
entered. (in my case www.exchange.iu.edu instead of the gal address of ads.iu.edu)

changing the value in the gconf key /apps/evolution/addressbook/sources doesn't
seem to fix it 
Comment 5 donavan nelson 2006-10-25 12:59:18 EDT
Problem persists in FC6 final.
Comment 6 Matthew Barnes 2007-10-05 00:43:33 EDT
Is this problem still present in Fedora 8 Test 2 or later?
Comment 7 Matěj Cepl 2007-12-10 16:48:31 EST
Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

[This is mass-filed message to all open Fedora Core 6 bugs related to Evolution.
If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]
Comment 8 Matěj Cepl 2008-01-15 09:39:09 EST
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional


{This is mass-closing of all obsolete bugs; if this bug was in your opinion
closed by mistake, please, reopen it with additional information; thanks a lot
and I am sorry for bothering you in such case.}

Note You need to log in before you can comment on or make changes to this bug.