Error messages are logged to STDOUT or a file that you specify. The method for specifying a log file differs depending on your integration broker. For instructions on how to change where messages are logged , refer to the documentation for your particular integration broker, as follows:
Table 6 lists common errors generated by the adapter and recommended
solutions. In the table, "xxx" and "yyy" represent
strings in actual generated messages.
Table 6. Common adapter errors and recommended solutions
Error number | Error message | Explanation/Recommended solution |
---|---|---|
4001 | Exception caught in xxx: yyy | An exception was caught in method xxx. The exception text is described in yyy, which may contain the message ID and text extracted from the NotesException class. |
4006 | There is no value for configuration property xxx. Using default value: yyy. | If needed, set the property as appropriate using the connector configurator. |
4008 | There is no value for configuration property xxx. | If needed, set the property as appropriate using the connector configurator. |
4034 | Failed to deliver the document business object to the broker. Event # xxx, status yyy. | The status will indicate why the failure occurred. You can change the status to "ready for poll" once the problem has been corrected. |
4036 | No subscription was found for the attempted business object delivery. Event # xxx, status yyy. | Verify that the collaborations and connectors are started. |
4049 | Failed to retrieve the document with noteID: xxx, event # yyy. | A problem occurred retrieving the document specified in the event specified. Document may have been deleted subsequent to the specified event. |
4050 | Failed to retrieve event record # xxx. | Verify that the BIALD_EventTable.nsf database is available and that the user specified in connector configuration has appropriate authority to read documents in the database. |
4051 | There are no more events to poll from the event table. | There are no events listed in the event table.No action is required. |
4052 | Failed to retrieve the event view: xxx. | There was a problem reading the event table view of the BIALD_EventTable.nsf database. Verify that the BIALD_EventTable.nsf database is available and that the user specified in connector configurator has appropriate authority to read documents in the database. |
4059 | The item type is not recognized. | The adapter is processing a document that has an Item type that is not supported. The item will not appear in the DominoDocument Business Object. Refer to "Lotus Domino business object definition" for the supported Item types. |
4064 | Failed to open the database: xxx for a Domino event. Document noteID yyy. Event # zzz. | Verify that the database is available and that the user specified in connector configuration has appropriate authority to read documents in the database. |
4072 | Encountered an IN_PROGRESS event, event number # xxx. The connector has been configured to log an error. | Based on connector configuration, In-progress events are logged as errors. If configured action is incorrect, update using connector configurator. |
4073 | Encountered an IN_PROGRESS event, event number # xxx. The connector has been configured to log a fatal error. | Based on connector configuration, In-progress events are logged as fatal errors. If the configured action is incorrect, update using connector configurator. |
4074 | Encountered an IN_PROGRESS event. The connector has been configured to ignore the event. | Based on connector configuration, In-progress events are ignored. If the configured action is incorrect, update using connector configurator. |
4075 | Encountered an IN_PROGRESS event. The connector has been configured to reprocess the event. | Based on connector configuration, In-progress events are reprocessed. If configured action is incorrect, update using connector configurator. |
4076 | Failed to validate session in method xxx. | Verify Domino server is started. Verify server, username and password are configured correctly in connector configuration. |
4077 | Failed to establish a connection to the event table database or view in method xxx. | Verify Domino server is started. Verify server, username and password are configured correctly in connector configuration. |
4081 | Invalid document database path for event # xxx | This message indicates that the database does not exist at the configured path. The database might have been deleted after the event was sent to the event table and before the adapter attempted to process the event. |
4084 | This Domino session is no longer valid. | Verify Domino server is started. Verify that server, username and password are configured correctly in connector configuration or Business Object. |
5001 | Error accessing Domino server.
Server: xxx Username: yyy Error text: zzz | An error occurred when accessing the Domino server. Verify that the server has been started. See the error text for more information. |
5002 | Error accessing database: xxx.
Error text: yyy | An error occurred when accessing the specified database. See the error text for more information. |
5003 | Database xxx not found. | The specified database was not found on the server. |
5005 | Error opening database: xxx
The database does not exist. | The specified database does not exist on the server. |
5006 | Unsupported verb: xxx | The specified verb is not supported by the connector. |
5007 | Error opening document with noteID xxx. Error text: yyy. | An error occurred when opening the specified document. See the error text for more information. |
5008 | Error opening document with noteID xxx. The document was not found in the database. | A document with the specified noteID was not found in the database. |
5009 | Error creating document.
Error text: xxx. | An error occurred when creating a new document in the database. See the error text for more information. |
5010 | Error retrieving noteID from the document. | An error occurred when retrieving the noteID from the document after it was successfully created in the database. The noteID will not be added to the business object. |
5011 | Error deleting the document with noteID xxx. Error text: yyy. | An error occurred when deleting the specified document from the database. See the error text for more information. |
5012 | Error validating document with noteID xxx. Error text: yyy. | An error occurred when validating the specified document. See the error text for more information. |
5013 | Error saving document.
Error text: xxx. | An error occurred when saving the specified document. See the error text for more information. |
5014 | The Document was not saved.
Possible causes are:
| The document was not saved either because it was not changed, or because of the ForceSave and MakeResponse connector property values. |
5015 | Attribute xxx not found in the business object yyy. | The specified attribute was not found in the specified business object. |
5016 | Attribute xxx is not String type in the business object yyy. | The specified attribute is not a String type in the specified business object. |
5017 | Attribute xxx is not Boolean type in the business object yyy. | The specified attribute is not a Boolean type in the specified business object. |
5018 | Attribute xxx is not a business object type in the business object yyy. | The specified attribute is not a business object type in the specified business object. |
5019 | Error adding item xxx to the document. Error text: yyy. | An error occurred when adding an item to a document. See the error text for more information. |
5020 | Error retrieving the document's parent database. Error text: yyy. | An error occurred when retrieving the parent database of the document. See the error text for more information. |
5021 | Error retrieving the current session from the database. Error text: xxx. | An error occurred retrieving the current Session from the Database. See the Error text for more information. |
5022 | Error creating DateTime object from the string xxx. Error text: yyy. | An error occurred when creating a DateTime object from the specified string. See the error text for more information. Date strings need to conform to the patterns specified in the java.text.SimpleDateFormat API. |
5023 | No ItemHandler defined for type: xxx. Valid types include Double, String, and Date. | No ItemHandler is defined for the type specified in the DominoItem.type attribute. |
5024 | Error setting flag xxx in item yyy.
Exception text: zzz. | An error occurred setting the specified flag in the specified item. See the error text for more information. |
5025 | Error converting string xxx to a Double. | An error occurred converting the specified string to a double object. |
5026 | Error converting the Domino document to a business object with noteID xxx Error text: yyy. | An error occurred when converting a document to a business object. See the error text for more information. |
5029 | Error removing item xxx from the document noteID yyy.
Error text: zzz. | An error occurred when removing the specified item from the document. See the error text for more information. |
5030 | Error initializing and validating the business object attributes.
Business object name: xxx. Error text: yyy | An error occurred in the call to CWConnectorUtil.initAndValidateAttributes() for the specified business object. See the error text for more information. |
5031 | Unsupported subverb: xxx for Domino item yyy. | The specified subverb is not supported by the connector. |
5032 | Error parsing the date string using the default format for locale.
Date: xxx.
Locale: yyy. | An error occurred when parsing the specified date string using the system default format for the specified locale. |
5033 | Error parsing the date string using the configured format.
Date: xxx.
Locale: yyy. Format: zzz. | An error occurred when parsing the specified date string using the specified format and locale. |
5034 | Unable to generate a date object using the configured date format
strings.
Date: xxx. Locale: yyy. | All date formats will be attempted before an error is logged. Verify that all attempts to generate the Date have failed. If so, specify required date format in the DateFormats connector application-specific property. For more information, see Application-specific configuration properties. |
5035 | The noteID was not specified in the business object. | Verify that the noteID is always specified in the incoming business object. |
5038 | An invalid value was specified for the name attribute. Name xxx. Business object yyy. | Verify that the attribute does not have a CxIgnore or CxBlank value. |