Troubleshooting
Learn how to troubleshoot connector SE.
Connection to EWS cannot be established
Errormessage | Possiblereasonsand how to resolve |
---|---|
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (401) Unauthorized. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized. | EWS impersonation user is not allowed to access EWS |
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (403) Forbidden. ---> System.Net.WebException: The remote server returned an error:(403) Forbidden. |
wrong/misspelled URLof EWS e.g.:http://exlab02s1.exlab02.local/ instead of |
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (404) Not Found. ---> System.Net.WebException: The remote server returned an error: (404) Not Found. | |
The request failed. The remote server returned an error: (405) Method Not Allowed. |
wrong/misspelled URL of EWS (when using HTTPS) e.g.: https://exlab02s1.exlab02.local/ instead of |
Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. --- > System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. |
Certificate is not trusted on local machine runningconnector SE Solution is to add this certificate as trusted on local machine |
Microsoft.Exchange.WebServices.Data.ServiceResponseException: Access is denied. Check credentials and try again. | Password of EWS Impersonation User is not correct or expired |
For EWS version Exchange2010_SP1 exception caught: The request failed. The remote server returned an error: (503) Server Unavailable. | wrong/mis-spelled URL of EWS |
The account does not have permission to impersonate the requested user. Thrown exception: SCDataInterop.Exceptions.CDbException: Could not open mailbox | EWS Impersonation User is not configured properly– is not allowed to impersonate |
SYNCHRONIZING MAILBOX: USER.121@EXLAB02.LOCAL 2014.05.14;09:50:00; 438;update.connector ;Error ; 59228160; 2352;10,56121;CExWebSvcAccess.SetImpersonationId ********* EXCEPTIONCAUGHT !!! ************* Thrown exception: System.Exception: There is no contact data found for smtp = USER.121@EXLAB02.LOCAL |
Mailbox USER.121@EXLAB02.LOCAL is not visible in GAL and cannot be accessed by connector (EWS) |
Appointments are not synchronized
Appointments which are created in Aurea CRM are not synchronized to Exchange Server.
Solution:
Check if an appointment type is selected in the "Appointments (I)" tab in the configuration application, e.g.
Check if < auto_sync >
is added to forms.xml.
Check for correct definition of the master user (see also Configuration of users, creation of users.xml further details).
Only appointments of OCSU user are synchronized
If impersonation fails only appointments of OCSU user are synchronized. This might be cause by the missing or falsely authentication tag in the forms.xml (see Configuration of users, creation of users.xml).
If impersonation is properly defined you should find similar entries in the log file as listed below showing.
2009-09-11 11:19:54,820|Inf|interface0|WWW |General |yncML::ProcessCredentials|Login
user=OCSU uri=outlook
2009-09-11 11:19:54,820|Inf|interface0|WWW |General |yncML::ProcessCredentials|Login
user=OCSU master=1
No invitations are sent for company-related appointments
In case of company related appointments no invitations or cancellations are sent even if the company (mail address) belongs to a mail space which is supposed to be synchronized. This is by design.