Error handling
http-Status error
Status 401 - Unauthorized (I)
[2009-12-17T07:55:40] [Z-00-N-0011-S] [<!--Exception: java.lang.Exception//-->] [<!--Message: null//-->]
[C][M-36-R-0044-S] [<!--Login: BOMS\crm//-->] [<!--Status: 401//-->] [<!--Text: Unauthorized//-->] [<!--URI: http://exchangedomain1.de/exchange/testuser@adito.de//-->] [<!--Request:
...
//-->]
Cause:
The user BOMS\crm has no access to the mailbox of the user
testuser@adito.de
Solution:
The rights of the user BOMS\crm must be configured on the Exchange
server to allow access to the testuser (if this is a SuperUser).
Status 401 - Unauthorized (II)
Cause:
The password of the impersonation user has expired, or the impersonation user has been deactivated in Active Directory.
Solution:
The user must be reactivated, or a new password must be assigned. This password must be entered in the ADITO alias configuration.
Status 403 - Forbidden
Cause:
Access to the Exchange server is not possible because the IIS running the EWS does not allow access.
Solution:
If the EWS website is configured on IIS to require SSL for access, then SSL and the appropriate port must also be configured on ADITO in the System Editor for the Exchange Webservices alias.
Status 404 - Not Found
[2009-12-17T17:30:40] [Z-00-N-0011-S] [<!--Exception: java.lang.Exception//-->] [<!--Message: null//-->]
[C][M-36-R-0044-S] [<!--Login: crm//-->] [<!--Status: 404//-->] [<!--Text: Ressource wurde nicht gefunden.//-->] [<!--URI: http:// exchangedomain1.de/exchange/testuser@adito.de/Kalender//-->] [<!--Request:
...
//-->]
Cause:
The user "crm" has here no access to the resource "Calendar" of the user testuser@adito.de
Solution:
Make sure that this is a German Exchange server and that the resource is called "Kalender" (and not "calendar").
Security and connectivity
Certificate is not accepted
If a calendar backend is connected and the certificate of the calendar backend does not match the IP or hostname received by the ADITO server, the certificate may not be accepted.
In this case there is the possibility to set the option 'securitySSLdisableCertificateCheck' in the Designer-'PREFERENCES'. This disables the certificate check.
To enable securitySSLdisableCertificateCheck, open the corresponding
system (e.g. default) by a double click and switch to the tab
PREFERENCES. Select security in the navigator and check
securitySSLDisableCertificateCheck.
Connection Error - get Port failed
If the following error occurs, the points listed below should be checked:
[S] [Z-00-N-0011-S] [<!--Exception: de.adito.aditoweb.plugin.exchangewscontact.ExchangeWSException//-->] [<!--Message: getExchangeServerPort: Connection to Server failed//-->] [<!--Invoked Method: plugin.exchangewscontact.ExchangeWSContactServerFactory.getExchangeServerPort//-->] [<!--Line: 77//-->] [<!--Invoker: plugin.exchangewscontact.ExchangeWSContact._getContactFolders//-->] [<!--Line: 488//-->]
Here you have to check if it is a https connection. If yes:
-
Has the certificate been imported into the Java keystore (see chapter Installing certificates)?
-
Has the hostname verifier been enabled?
Windows-Auth enabled, Autodiscover not possible
If only Windows authentication is enabled in IIS, Basic authentication may be required for Autodiscover. For this the http status parameters (see chapter Default Authentication) are set.
Synchronization problems
Unexpected appointment cancellations (When using calendar synchronization)
If appointments are unexpectedly cancelled when calendar synchronization is enabled, it may be because the organizer is not present in the AFFECTEDUSERS column of the calendar entry.
Via a start parameter of the ADITO server it can be activated that ADITO checks if the organizer is also present in the appointment at the involved users. If this user is not present, it will be added later.
This parameter is:
-Dadito.ews.organizertweak=true
Problems with contact synchronization
Get Port Failed
[S] [Z-00-N-0011-S] [<!--Exception: de.adito.aditoweb.plugin.exchangewscontact.ExchangeWSException//-->] [<!--Message: getExchangeServerPort: Connection to Server failed//-->] [<!--Invoked Method: plugin.exchangewscontact.ExchangeWSContactServerFactory.getExchangeServerPort//-->] [<!--Line: 77//-->] [<!--Invoker: plugin.exchangewscontact.ExchangeWSContact._getContactFolders//-->] [<!--Line: 488//-->]
The following things should be checked:
-
Is it an https connection?
-
If yes, was the hostnameverifier-plugin called and the server added to the Java keystore? (InstallCert - important, after copying the jssecacerts into the security folder the server must be restarted)
Display/edit error
"invalid" in user name
Sometimes appointments are created and displayed in the calendar, but errors occur when editing the appointments. In this case, make sure that the correct e-mail address is stored in the user properties in the system editor:
Calendar entries with empty subject
If there is a calendar event on the Exchange side that contains only an empty string as subject, the EWS parser may not be able to read it.
The following error message appears:
[2015-11-12T07:43:50] [Z-00-N-0011-S] [<!--Caused by: microsoft.exchange.webservices.data.ServiceXmlDeserializationException: Could not read value from START_ELEMENT.Could not find CHARACTERS
at microsoft.exchange.webservices.data.EwsXmlReader.readValue(EwsXmlReader.java:420)
at microsoft.exchange.webservices.data.EwsXmlReader.readElementValue(EwsXmlReader.java:315)
at microsoft.exchange.webservices.data.TypedPropertyDefinition.loadPropertyValueFromXml(TypedPropertyDefinition.java:113)
at microsoft.exchange.webservices.data.PropertyBag.loadFromXml(PropertyBag.java:482)
at microsoft.exchange.webservices.data.ServiceObject.loadFromXml(ServiceObject.java:268)
at microsoft.exchange.webservices.data.EwsServiceXmlReader.readServiceObjectsCollectionFromXml(EwsServiceXmlReader.java:180)
at microsoft.exchange.webservices.data.GetItemResponse.readElementsFromXml(GetItemResponse.java:57)
at microsoft.exchange.webservices.data.ServiceResponse.loadFromXml(ServiceResponse.java:109)
at microsoft.exchange.webservices.data.MultiResponseServiceRequest.parseResponse(MultiResponseServiceRequest.java:54)
at microsoft.exchange.webservices.data.ServiceRequestBase.readResponse(ServiceRequestBase.java:393)
at microsoft.exchange.webservices.data.SimpleServiceRequestBase.readResponse(SimpleServiceRequestBase.java:163)
at microsoft.exchange.webservices.data.SimpleServiceRequestBase.internalExecute(SimpleServiceRequestBase.java:47)
... 44 more//-->]
[C][Z-00-N-0011-S] [<!--Caused by: microsoft.exchange.webservices.data.ServiceRequestException: The request failed. Could not read value from START_ELEMENT.Could not find CHARACTERS
at microsoft.exchange.webservices.data.SimpleServiceRequestBase.internalExecute(SimpleServiceRequestBase.java:58)
at microsoft.exchange.webservices.data.MultiResponseServiceRequest.execute(MultiResponseServiceRequest.java:138)
at microsoft.exchange.webservices.data.ExchangeService.internalLoadPropertiesForItems(ExchangeService.java:1168)
at microsoft.exchange.webservices.data.Item.internalLoad(Item.java:145)
at microsoft.exchange.webservices.data.ServiceObject.load(ServiceObject.java:345)
at de.adito.aditoweb.server.dz.a(Unknown Source)
at de.adito.aditoweb.server.dz.c(Unknown Source)
at de.adito.aditoweb.server.dz.a(Unknown Source)
at de.adito.aditoweb.server.dz.a(Unknown Source)
... 36 more//-->]
[C][M-36-R-0350-S] [<!--de.adito.aditoweb.core.checkpoint.exception.mechanics.AditoException: [M-36-R-0350-S]
at de.adito.aditoweb.core.checkpoint.CheckPointHandler.checkPoint(Unknown Source)
at de.adito.aditoweb.server.dq.getEventTodos(Unknown Source)
at de.adito.aditoweb.server.b.a(Unknown Source)
at de.adito.aditoweb.server.v.a(Unknown Source)
at de.adito.aditoweb.server.a.getEntries(Unknown Source)
at de.adito.aditoweb.calendar.backend.exchangews.ExchangeWSLimitationsBackend.getEntries(Unknown Source)
at de.adito.aditoweb.server.aj.getEntries(Unknown Source)
at de.adito.aditoweb.server.ag.getEntries(Unknown Source)
at de.adito.aditoweb.server.ae.getEntries(Unknown Source)
at de.adito.aditoweb.server.q.getEntries(Unknown Source)
at de.adito.aditoweb.server.ai.getEntries(Unknown Source)
at de.adito.aditoweb.server.ak.getEntries(Unknown Source)
at de.adito.aditoweb.server.fp.a(Unknown Source)
at de.adito.aditoweb.server.fy.a(Unknown Source)
at de.adito.aditoweb.server.bhd.a(Unknown Source)
at de.adito.aditoweb.server.bgq.b(Unknown Source)
at de.adito.aditoweb.server.bgu.a(Unknown Source)
at de.adito.aditoweb.server.bgv.b(Unknown Source)
at de.adito.aditoweb.server.bgv.a(Unknown Source)
at de.adito.aditoweb.server.bjd.h(Unknown Source)
at de.adito.aditoweb.server.bjd.c(Unknown Source)
at de.adito.aditoweb.server.bjn.run(Unknown Source)
at de.adito.aditoweb.server.bip.a(Unknown Source)
at de.adito.aditoweb.server.cdk.c(Unknown Source)
at de.adito.aditoweb.server.cdk.a(Unknown Source)
at de.adito.aditoweb.server.cdk.b(Unknown Source)
at de.adito.aditoweb.server.cdk.a(Unknown Source)
at de.adito.aditoweb.server.cdk.b(Unknown Source)
at de.adito.aditoweb.server.cdk.a(Unknown Source)
at de.adito.aditoweb.server.bho.a(Unknown Source)
at de.adito.aditoweb.server.chx.a(Unknown Source)
at de.adito.aditoweb.server.chx.p(Unknown Source)
at de.adito.aditoweb.server.cib.run(Unknown Source)
at de.adito.aditoweb.server.aiy.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)//-->]
"The folder was not found in the information store"
This admittedly cryptic message appears whenever the logged-in user does not have permissions to other users' calendars. In this case, Exchange Web Services does not report that a permission does not exist, but does not provide the information about the user’s required folder ("Appointments"). In case of direct access, items cannot be modified if the rights settings (See chapter Rights: Release of rights in Microsoft Outlook.) are only set to "Free / Booked".
"Too many items were picked up"
If a very large number of calendar items are contained in a mailbox, this can lead to errors. This applies to both direct access, calendar caching, and synchronization. This error can be prevented by specifying the following parameter at server startup:
-Dadito.calendar.updater.strict=false