After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607611 - Can't view or create contacts list on Exchange 2003 server
Can't view or create contacts list on Exchange 2003 server
Status: RESOLVED DUPLICATE of bug 586096
Product: evolution-mapi
Classification: Applications
Component: Contacts (Addressbook)
0.28.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2010-01-20 22:35 UTC by Matthew Barnes
Modified: 2010-01-21 11:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew Barnes 2010-01-20 22:35:14 UTC 
Forwarding this from a Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=557220


Description of problem:
The global address list shows all entries, but the contact list on the server
doesn't show any entries

Version-Release number of selected component (if applicable):
evolution-mapi-0.28.2-1.fc12.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create some entries in the contact list on the Exchange 2003 server using
another client.
2. Open Contact List in Evolution for a MAPI account.
3. Create a contact in Evolution for a MAPI account

Actual results:
No entries are shown.  Creation of new entry results in error popup: Error
adding contact: Other error

Expected results:
All entries are listed.  New entries are created.
Comment 1 Akhil Laddha 2010-01-21 03:50:55 UTC 
can be marked a duplicate of bug 586096
Comment 2 Milan Crha 2010-01-21 10:24:40 UTC 
(In reply to comment #1)
> can be marked a duplicate of bug 586096

yes, please
Comment 3 Akhil Laddha 2010-01-21 11:33:25 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 586096 ***