Bug 157226
Summary: | Evolution Exchange support does not work | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Chris Lee <clee> | ||||
Component: | evolution-connector | Assignee: | Dave Malcolm <dmalcolm> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-10-14 19:50:05 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Chris Lee
2005-05-09 16:11:54 UTC
Please can you run this test: 1) Close Evolution 2) Open a terminal. 3) Type the following: 3.1) script 3.2) evolution --force-shutdown 3.3) export E2K_DEBUG=4 3.4) /usr/libexec/evolution/1.4/evolution-exchange-storage & 3.5) evolution & 4) Evolution should now start; try to connect to your account on the Exchange server. 5) Type "exit" to finish the script command and its logging Please attach the "typescript" file Did you ever reproduce this? Created attachment 119964 [details]
script file with some debug output upon running evolution
There are many ways to configure Exchange, and it's not clear from the original report how it was set up. This bug should either have been closed, or clarified with more information on the configuration of the server; the connector has worked for me with RHEL3 in my tests. With the above in mind, I'm going to resolve this bug as WORKSFORME Deepak N: Thanks for attaching the debug output. Unfortunately it's not very useful for identifying the problem without more context. If you have a support agreement with Red Hat, I'd recommend contacting Red Hat Support, and we can establish the details of the problem; otherwise, please open this as a separate bug, so that we can be sure of the details of your situation without confusion. Thanks. |