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 334378 - user not able to subscribe to a calendar to which he has acquired permissions
user not able to subscribe to a calendar to which he has acquired permissions
Status: RESOLVED DUPLICATE of bug 331513
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.5.x
Other All
: Normal normal
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-03-13 06:08 UTC by Vandana
Modified: 2006-03-13 12:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
e2k debug for exchange (15.82 KB, text/plain)
2006-03-13 06:10 UTC, Vandana
Details
e2k debug for evolution (11.36 KB, text/plain)
2006-03-13 06:11 UTC, Vandana
Details

Description Vandana 2006-03-13 06:08:01 UTC
Please describe the problem:
Give all permissions to user , shah to access surf's calendar .

Go to shah account and try to subscribe to that calendar.

Steps to reproduce:
1. in surf account , give all permissions for Calendar to shah
2. go to shah account , and subscribe to the calendar of surf
3. 


Actual results:
A generic error message is displayed

Expected results:
Shah should be able to subscribe to surf's  Calendar

Does this happen every time?
yes

Other information:
Comment 1 Vandana 2006-03-13 06:10:45 UTC
Created attachment 61148 [details]
e2k debug for exchange
Comment 2 Vandana 2006-03-13 06:11:39 UTC
Created attachment 61149 [details]
e2k debug for evolution
Comment 3 Sushma Rai 2006-03-13 11:27:02 UTC
Do you see
"WARNING **: LDAP authentication failed (0xffffffff)" in the console?
Comment 4 Vandana 2006-03-13 12:20:13 UTC
yes , I did get that error.
Comment 5 Sushma Rai 2006-03-13 12:43:39 UTC
Please try the operation with some other server.

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