The connector logs any abnormal condition that it encounters during processing, regardless of the trace level. It writes the error text to the connector log file; the name and location of this file are set by the LogFileName connector configuration property.
The message contains a detailed description of the condition and the outcome and may also include extra information that may aid in debugging, such as business object dumps or stack traces (for exceptions).
For a complete list of error messages, refer to the BIA_ExchangeConnector.txt file installed in the ProductDir\connectors\messages directory.
Table 13 describes some of more common errors and how the connector handles those errors.
Error description | Error type | Error handling |
---|---|---|
The Exchange Server error MAPI_E_LOGON_FAILED is returned during Session login. The error occurs because the value for UserProfile or UserPassword is invalid, or because Exchange Server is not running properly. | Fatal error | The connector detects the error during initialization. The connector logs a fatal error and then terminates. |
The connector detects a connection error when processing a business object service call request. | Fatal error | The connector logs a fatal error, sends the return code APPRESPONSE_TIMEOUT to trigger email notification, and then terminates. |
The connector detects that the connection is lost while polling for events. The Exchange Server error MAPI_E_NETWORK_ERROR is returned while attempting to retrieve an event from the Event Store. | Fatal error | The connector tries to retrieve the event as many times as specified in the RestartRetryCount configuration property. If the connection has not been restored, the connector logs a fatal error, sends the return code APPRESPONSE_TIMEOUT to trigger email notification, and then terminates. |
The connector attempts to retrieve an unsubscribed event. | Warning | The connector logs the warning and stores the event in the Archive Store with a status of UNSUBSCRIBED. |
The connector encounters a problem with the gotApplEvent() method when trying to publish a business object to the integration broker. | Error | The connector logs the error. The event is stored in the Archive Store with a status of ERROR_POSTING_EVENT. |
The Create, Update, or Delete operation for a message fails during service call requests. | Error | The connector logs the error and returns CWConnectorConstants.FAIL to the calling collaboration or flow. |
The Exchange Server error MAPI_E_NOT_FOUND is returned during event processing because a folder, item, or field does not exist. | Error | The connector logs the error. The event is stored in the Archive Store with a status of ERROR_OBJECT_NOT_FOUND. |
The Exchange Server error E_ACCESSDENIED is returned when the connector attempts to view or update an object on which it does not have permissions. | Error | The connector logs the error. The event is stored in the Archive Store with a status of ERROR_PROCESSING_EVENT. |
The Exchange Server error E_FAIL is returned when an item cannot be updated because the mailbox quota has been exceeded. | Error | The connector logs the error. The event is stored in the Archive Store with a status of ERROR_PROCESSING_EVENT. |
When the connector attempts to poll the Event Store, one or more of the following Outlook messages might be displayed:
A program is trying to automatically send e-mail on your behalf. Do you want to allow this? If this is unexpected, it may be a virus and you should choose "No."
A program is trying to access e-mail addresses you have stored in Outlook. Do you want to allow this? If this is unexpected, it may be a virus and you should choose "No."
This warning is caused by the security features in Outlook. Microsoft provides a method of customizing security settings with a custom form so that this does not occur. For more information refer to the articles at http://support.microsoft.com. In particular: