Error messages

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 No value for configuration
property xxx. Using default value:
yyy
If needed, set the property as appropriate using the connector configurator.
4008 No value for configuration
property xxx.
If needed, set the property as appropriate using the connector configurator.
4034 Failed to deliver the Document BO
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 found for the attempted
BO delivery, event # xxx, status yyy.
Verify collaborations and connectors are started.
4049 Failed to Retrieve 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 No more events to poll from the
EventTable.
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 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 Database: xxx for 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. Connector has been configured to Log 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.
Connector has been configured to
Log Fatal Error.
Based on connector configuration, In
Progress events are logged as fatal errors. If
configured action is incorrect, update using
connector configurator.
4074 Encountered an IN_PROGRESS Event. Connector has been configured to Ignore Event. Based on connector configuration, In-Progress events are ignored. If configured action is incorrect, update using connector configurator.
4075 Encountered an IN_PROGRESS Event. Connector has been configured to Reprocess 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 connection to event table database/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 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 accessing the Domino server. Verify server is started.
5002 Error accessing database: xxx. Error text: yyy Verify configured user has appropriate authority to access the database.
5003 Database xxx not found. Database specified in the business object was not found. Verify database path/name specified in business object.
5005 Error opening database: xxx Error text: yyy See the Error text for more information.Verify configured user has appropriate authority to access database.
5006 Unsupported verb: xxx The specified verb in the incoming business object is not supported by the connector. Supported verbs are as follows: Create, Retrieve, Update, Delete, Exist.
5007 Error opening document.
NoteID=xxx. Error text: yyy
The business object handler received a business object with a NoteID that is not in the specified database. The document with this NoteID might have been deleted. If the NoteID is incorrect, correct it and resend the business object.
5008 Error opening document.
NoteID=xxx. Document not found
in database.
A document with the specified NoteID was not found in the database.
5009 Error creating document. Error
text: xxx
The user might not have the required authority to create a document in the specified database. Change the authority level or use different user login information.
5010 Error retrieving NoteID from
Document.
During processing of Create verb, an error occurred retrieving the NoteID from the document after it was successfully created in the database. The NoteID will not be added to the Business Object. If the NoteID is required, access the document using the Notes Client to view.
5011 Error deleting document.
NoteID=xxx. Error text: yyy
User might not have authority to delete the
document. Change authority or use
different user login information.
5012 Error validating document.
NoteID=xxx. Error text: yyy
An error occurred validating the specified document. Refer to the error text for more information.
5013 Error saving document. Error text:
xxx
Explanation: An error occurred saving the specified document. Refer to the error text for more information.
5014 The Document was not saved. Possible causes: The document was unchanged by the request, or because of settings of ForceSave and MakeResponse properties. The document was not saved either because it was not changed, or because of connector properties. Set connector application-specific properties; ForceSave, MakeResponse, as appropriate See Table 3 or your Domino
documentation for more information.
5015 Attribute xxx not found in Business
Object yyy.
The specified required attribute was not found in the Business Object. Verify that correct version of the business object is being used.
5016 Attribute xxx is not String type in
Business Object yyy
The specified attribute is not a String type in the specified business object as expected by the adapter. Verify that correct version of the business object is being used.
5017 Attribute xxx is not boolean type in
Business Object yyy
The specified attribute is not a boolean type in the specified Business Object as expected by the adapter. Verify that correct version of the business object is being used.
5018 Attribute xxx is not Business Object
type in Business Object yyy
The specified attribute is not a Business Object type in the specified business object as expected by the adapter. Verify that correct version of the business object is being used.
5019 Error adding Item xxx to
document. Error text: yyy
User might not have authority. Change authority or use different user login information.
5020 Error retrieving Document parent
Database. Error text: yyy
An error occurred retrieving the parent database of the document. See the Error text for more information.
5021 Error retrieving 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
Explanation: An error occurred creating a DateTime
object from the specified String. Date Strings need
to conform to the patterns specified in the
java.text.SimpleDateFormat API. Refer to
"Application-specific configuration properties" for
more information.
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. Verify a supported type is set 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. Verify that DominoItemValue.value is a valid Double value in the incoming business object.
5026 Error converting Domino
Document to a Business Object.
NoteID=xxx Error text: yyy
An error occurred converting a document to a business object. See the error text for more information.
5029 Error removing Item xxx from
Document. NoteID=yyy Error text:
zzz
An error occurred removing the specified Item from the Document. See the error text for more information.
5030 Error initializing and validating
Business Object attributes. BO
Name: xxx Error text: yyy
Make sure that a value is specified in the incoming business object for any attributes with IsRequired set to Yes.
5031 Unsupported subverb: xxx for
DominoItem Name=yyy
The specified subverb is not supported by the connector. Verify that a supported sub-verb is specified for the DominoItem business object. One of: Create, Update, Delete.
5032 Error parsing Date String using
default format for locale. Date: xxx
Locale: yyy
An error occurred parsing the specified date string
using the system default format for the specified
locale. Verify that the Date string matches the
system default format for the Locale of the business
object. If not, specify required date format in the
DateFormats connector application-specific property.
Refer to "Application-specific configuration properties"
for more information.
5033 Error parsing Date String using
configured format. Date: xxx
Locale: yyy Format: zzz.
An error occurred parsing the specified date String
using the specified format and Locale. Verify that
the Date string matches one of the formats specified
in the DateFormats connector application-specific
property. Refer to
"Application-specific configuration properties"
for more information.
5034 Unable to generate Date object
using 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. Refer to
"Application-specific configuration properties"
for more information.
5035 The NoteID was not specified in
the Business Object.
Verify that NoteID is always specified in the incoming business object.
5038 Invalid value specified for Name
attribute. Name=xxx, BO=yyy.
Verify that the attribute does not have a CxIgnore or CxBlank value.

Copyright IBM Corp. 1997, 2003