8 BDSS-00000 to BDSS-50248

BDSS-00000: DispatcherSettings - error loading settings. {0}

Cause: Cannot load the preferences node for BDSS.

Action: Verify that the preferences back end store exists and that user this application is running under has correct access rights.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-00005: Exception thrown by backing store when setting ChunkSize: {0}

Cause: Cannot store data to the preferences node for BDSS.

Action: Verify that the preferences back end store exists and that user this application is running under has correct access rights.

Level: 1

Type: ERROR

Impact: Data

BDSS-00006: Exception thrown by backing store when setting EngineEndpointUrl: {0}

Cause: Cannot store data to the preferences node for BDSS.

Action: Verify that the preferences back end store exists and that user this application is running under has correct access rights.

Level: 1

Type: ERROR

Impact: Data

BDSS-00010: Cannot retrieve the backing store to load preferences.

Cause: Cannot retrieve the preferences node for BDSS.

Action: Verify that the preferences back end store exists and that user this application is running under has correct access rights.

Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-00011: Cannot initilize SyncDispatcherBean.

Cause: There is either imporper configuration or BDSS components are not installed correctly.

Action: Verify your configuration and re-install the BDSS components if necessary.

Level: 1

Type: ERROR

Impact: Data

BDSS-00012: User chunk size is not available from configuration. Using the default.

Cause: Cannot retrieve the data from the preferences node for BDSS.

Action: Verify that the preferences back end store exists and that user this application is running under has correct access rights.

Level: 1

Type: WARNING

Impact: Configuration

BDSS-00014: ArrayOutOfBounds exception occured!

Cause: The code referenced an array index that does not exist.

Action: Restart the application.

Level: 1

Type: ERROR

Impact: Data

BDSS-00015: Cannot get users to dispatch from configuration!

Cause: The list of users to synchronize was not returned by the BDSS configuration.

Action: Verify that there are users that are configured properly using the User Settings MBean.

Level: 1

Type: ERROR

Impact: Data

BDSS-00017: Calling SynchronizeUsers failed: {0}

Cause: The call to the operation SynchronizeUsers failed.

Action: Verify that the BDSS hub components are installed on your applications server and are accessable.

Level: 1

Type: ERROR

Impact: Data

BDSS-00019: A member of the input users array was an empty string or was null. Continuing to process other users.

Cause: A hub user login was stored as an empty string.

Action: Verify that all hub users have a non-empty string for thier login.

Level: 1

Type: NOTIFICATION

Impact: Data

BDSS-10001: Failed to allocate an object of type {0}.

Cause: Failed to allocate an object of the type specified.

Action: Ensure that the system is not running low on memory. Check the log for other errors that may have led to this problem. Try restarting the appropriate component or machine.

Level: 1

Type: ERROR

Impact: Other

BDSS-10002: Null object detected. Context: {0}

Cause: A null object has been detected. The object name or type is logged with this message.

Action: Examine the log to determine the cause of this problem. If it cannot be determined an resolved then contact Oracle technical support.

Level: 1

Type: ERROR

Impact: Other

BDSS-10004: Original Error already logged.

Cause: This indicates that an exception has been detected, although details of the primary error are not logged with this message to avoid duplicate logging of an error. The primary error which caused this exception should already be logged.

Action: Examine the log for an earlier log entry that indicates the primary error which caused this exception.

Level: 1

Type: ERROR

Impact: Other

BDSS-10005: Object {0} is invalid.

Cause: A component in the BDSS product has detected an invalid object that is expected to be valid. For example, the object may be null, or it may be an empty string, etc. The invalid object may be a function parameter or an object retrieved by other means.

Action: Try checking configuration. Try restarting components or the machine. Try reinstalling the appropriate BDSS component. Examine the log for other messages that may indicate the cause of this problem. If necessary, contact Oracle technical support.

Level: 1

Type: ERROR

Impact: Data

BDSS-10006: Failed to access EJB due to problem with object {0}.

Cause: Indicates that an error occurred when attempting to access an Enterprise Java Bean.

Action: Examine the log to determine the cause for this error as an exception cause may have been logged with this message. Ensure that the product is properly installed.

Level: 1

Type: ERROR

Impact: Other

BDSS-10007: Version Id

Cause: This message string is a label that identifies a PIM record version ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Other

BDSS-20001: An unrecoverable error occurred while pushing record change(s) to the target PIM. Aborted pushing additional events to the PIM.

Cause: The cause is unknown but has been caught by a Java Exception. The exception occured while the Sync-Engine was in the process of pushing record change events to a connector.

Action: Search the BDSS log for the exception text that should give a clue to the cause.

Level: 1

Type: ERROR

Impact: Data

BDSS-20004: Failed to create a new record. The Sync-Engine will continue to push any additional create-record actions to the target PIM. Source-PIM record data: {0}

Cause: A failure code was returned from the target connector when the Sync-Engine invoked its createRecord method.

Action: Ensure that the target PIM and PIM connector is installed and working correctly. Look in the target connector log for clues to the failure.

Level: 1

Type: ERROR

Impact: Data

BDSS-20005: Failed to update a PIM record. The Sync-Engine will continue to push any additional update-record actions to the target PIM.

Cause: The Sync-Engine detected an error while attempting to update a PIM record.

Action: Ensure that the target PIM and PIM connector are installed and working correctly. Look in the Sync-Engine log and the target connector log for clues to identify the failure.

Level: 1

Type: ERROR

Impact: Data

BDSS-20006: Failed to update a PIM record.

Cause: The Sync-Engine has detected an exception while in the process of updating a PIM record. The failure may be due to a problem in the hub, rather than a connector issue.

Action: Examine the Sync-Engine log for the exception text that should give a clue as to why the failure occurred.

Level: 1

Type: ERROR

Impact: Data

BDSS-20007: Source PIM record data:

Cause: This message is simply used as a label to identify the source PIM record data that is logged immediately following this label text. This message is appended to a primary error message and is never logged by iteself.

Action: No action is required specifically for this error message. Instead, see the action defined for the primary error message to which this error message is appended.

Level: 1

Type: ERROR

Impact: Other

BDSS-20009: The target PIM connector failed to delete a PIM record. The Sync-Engine will attempt to push any additional delete-record actions to target PIM.

Cause: The Sync-Engine has detected an error while attempting to delete a PIM record.

Action: Examine the Sync-Engine log for information about the error cause.

Level: 1

Type: ERROR

Impact: Data

BDSS-20010: Failed to write an error status message to a PIM metadata record for Connector {0}, PIM record ID {1}.

Cause: The Sync-Engine detected an error while preparing to write an error message to the database for a particular PIM Map Record.

Action: Examine the Sync-Engine log to find the underlying exception message.

Level: 1

Type: ERROR

Impact: Data

BDSS-20011: Failed to propagate a delete-event to the target PIM server. Source Connector = {0}. Source PIM record ID = {1}.

Cause: This error occurs when the Sync-Engine detects an exception, when attempting to obtain hub-map or pim-map record metadata, while trying to process a delete-record event.

Action: Look in the log file for the exception text that should give a clue to the underlying cause. It is possible that an earlier exception was logged and propagated for additional handling. So there may be another message with an exception logged prior to this message, that may indicate the real underlying cause.

Level: 1

Type: ERROR

Impact: Data

BDSS-20012: Failed to delete a PIM record.

Cause: The Sync-Engine has detected an exception while in the process of deleting a PIM record. The failure may be due to a problem in the hub, rather than a connector issue.

Action: Examine the Sync-Engine log for the exception text that should give a clue as to why the failure occurred.

Level: 1

Type: ERROR

Impact: Data

BDSS-20013: Failed to update metadata to the BDSS hub-record. \tSource Connector user = {0} \tSource PIM Connector Name = {1} \tSource PIM Record Identifier = {2}.

Cause: This error occurs when the Sync-Engine is unable to persist updated metadata to the BDSS database for a particular BDSS hub-record. In particular, this error occurs when the Sync-Engine catches an exception when invoking method SyncConfig::getHubRecordForPimRecord. This error could indicate corrupt metadata for a particular BDSS hub-record, or perhaps a network or database failure, or a problem with the SyncConfig component.

Action: Check that the database is accessible. Perhaps try restarting the BDSS hub. If corrupt metadata is suspected, then try removing all metadata for a user and perform initial synchronization for a user.

Level: 1

Type: ERROR

Impact: Data

BDSS-20014: Cannot find find a hub record using the following information from the source record: \tSource Connector user = {0} \tSource Connector Name = {1} \tSource PIM Record Identifer = {2}.

Cause: The Sync-Engine cannot find a hub record for the specified PIM record identifier and Connector. This problem is unexpected and should not occur under normal operating conditions. This error message signifies that either hub metadata is missing or incorrect, or there was some other problem - such as a database access error. The Sync-Engine detects this error by means of an Exception thrown from SyncConfig method getHubRecordForPimRecord.

Action: Examine the log for evidence of exception text that will give more specific information as to the cause of the problem. Ensure that all infrastructure, such as the database and network, are working correctly. Ensure that all configuration is correct. Ensure that metadata is not corrupt for the specified user, Connector user and PIM Connector Name and PIM Record identifier. If the problem is due to hub metadata corruption for a given user then try clearing that user hub metadata and perform first-time synchronization for the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-20015: Failed to find an BDSS PIM metadata record for BDSS master hub record ID = {0}

Cause: This error message is logged when a PIM metadata record could not be found for the specified hub user ID, hub record ID and Connector. In particular, the Sync-Engine logs this message when it detects an exception from method SyncConfig::getPimRecordForHubRecord. This problem could be due to corrupt metadata (e.g. the PIM metadata record is actually missing) or some other cause.

Action: Examine the log for the exception text that should give a better clue as to the underlying cause of the error. Ensure that all infrastructure, such as the database and network, are working correctly. Ensure that all configuration is correct. Ensure that hub metadata is not corrupt for the logged hub record ID. If the problem is due to hub metadata corruption for a given user then try clearing that user hub metadata and perform first-time synchronization for the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-20016: Record metadata is not available to assign an error message to the target PIM record using config manager method updatePimMapRecordError.

Cause: Unable to write an error message to a PIM-map metadata record in the BDSS database because not enough information is available to identify a PIM-map metadata record.

Action: Examine the log for more detailed information about the underlying error that the Sync-Engine is attempting to log in the database. Expect to find log information about the underlying exception.

Level: 1

Type: ERROR

Impact: Data

BDSS-20017: (Target Connector user)

Cause: This message string is a label for a Connector user identifier that is a destination target for record events that are being pushed to a PIM connector. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.

Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20018: (Target PIM Connector Name)

Cause: This message string is a label for the name of a PIM connector that is a destination target for record events that are being pushed to a PIM. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.

Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20019: BDSS queue message receiver timeout expired. Queue message not received.

Cause: This error indicates that the Sync-Engine ExtractResponseTimeout occurred it recieved an ExtractResponse for which it was waiting. In particular, this error represents a failure to recieve an ExtractResponse via a queue message in a timely fashion. The Sync-Engine uses the ExtractResponseTimeout as a time-trigger to determine when a connector has become unresponsive. In such a case, the Sync-Engine has determined that it will not receive an ExtractResponse in a timely fashion and thus takes recovery action to abort the synchronization. This problems could be caused by a connector does not correctly send an ExtractResponse to the Sync-Engine. Alternatively, the ExtractResponse was sufficiently large, or network latency slow enough, that the time-out occurred before the ExtractResponse could be properly transferred to the Sync-Engine from a connector.

Action: Ensure that all connectors are properly working and can successfully send ExtractResponse objects to the Sync-Engine. Ensure that the Sync-Engine machine is not overloaded and can handle receiving ExtractResponse objects efficiently. Ensure that the amount of data transferred via an ExtractResponse is not too large, or the network latency to slow, to trigger the ExtractResponseTimeout. If necessary, increase the ExtractResponseTimeout time-out value. Determine whether an http webservice timeout is occurring when a connector sends an ExtractResponse to the Sync-Engine.

Level: 1

Type: ERROR

Impact: Data

BDSS-20020: Received queue message that is an unexpected message class type. Expecting class type ObjectMessage. {0}.

Cause: This error indicates that the Sync-Engine has received a queue message with an unexpected Java class type. This error indicates an internal communication protocol failure within the Sync-Engine.

Action: Contact Oracle technical support.

Level: 1

Type: ERROR

Impact: Data

BDSS-20021: Invalid Hashtable element key.

Cause: This error indicates that the Sync-Engine has detected an invalid hash table element key.

Action: Contact Oracle technical support.

Level: 1

Type: ERROR

Impact: Data

BDSS-20022: Invalid Hashtable element value for key = {0}.

Cause: This error indicates that the Sync-Engine has detected an invalid hash table element value for the specified element key.

Action: Contact Oracle technical support.

Level: 1

Type: ERROR

Impact: Data

BDSS-20023: null Hub User ID detected in an element of UsersArray.

Cause: The Sync-Engine has detected an invalid hub-user in the UsersArray. The Sync-Engine cannot synchronize an invalid hub user. In particular, a string array element is null, instead of specifying a valid hub user.

Action: Ensure that the array of users sent to the Sync-Engine has a valid hub user for each element in the array.

Level: 1

Type: ERROR

Impact: Data

BDSS-20024: Invalid Hub User ID detected in an element of UsersArray.

Cause: The Sync-Engine has detected an invalid hub-user in the UsersArray. The Sync-Engine cannot synchronize an invalid hub user. In particular, a valid string array element has been detected, but the string is empty and does not specify a hub user.

Action: Ensure that the array of users sent to the Sync-Engine has a valid hub user for each element in the array.

Level: 1

Type: ERROR

Impact: Data

BDSS-20026: Must configure a user hub-domain synchronization between two connector URLs. Currently detecting {0} URLs.

Cause: Specifies that an invalid number of connector URLs have been identified for synchronization of a hub domain for a user. Synchronization can only occur between two connector URLs for a given user and hub domain.

Action: Validate that BDSS configuration is correct for synchronizing between two connectors.

Level: 1

Type: ERROR

Impact: Data

BDSS-20027: Duplicate PIM domain priority.

Cause: This error occurs when the Sync-Engine detects that the same priority value has been assigned to more than one PIM domain for the specified hub domain, PIM user and connector.

Action: Fix configuration so that each PIM domain has a unique priority value for the specified hub domain, PIM user and connector.

Level: 1

Type: ERROR

Impact: Data

BDSS-20028: Invalid ExtractResponse detected. The ExtractResponse sent by a connector indicates that it contains delete events but the delete events do not exist.

Cause: This error occurs when the Sync-Engine detects that an ExtractResponse specifies a true value for member ExtractResponse.ExtractResponseData.hasDeletes and yet specifies a null value for member ExtractResponse.ExtractResponseData.deleteRecordIdArray. Thus, the ExtractResponse object is corrupt and cannot be processed.

Action: Fix the connector that is providing the invalid ExtractResponse.

Level: 1

Type: ERROR

Impact: Data

BDSS-20029: Invalid ExtractResponse detected. The ExtractResponse sent by a connector contains a null delete record ID.

Cause: This error is logged when the Sync-Engine detects a null array element in member ExtractResponse.ExtractResponseData.deleteRecordIdArray when a valid delete record ID is expected.

Action: Fix the connector that is providing the invalid ExtractResponse.

Level: 1

Type: ERROR

Impact: Data

BDSS-20030: An ExtractResponse indicates that upserts exist but they do not.

Cause: This error occurs when the Sync-Engine determines that an ExtractResponse should contain upsert records when it does not. In particular, member ExtractResponse.ExtractResponseData.hasUpserts is true but upsertRecordArray is ExtractResponse.ExtractResponseData.upsertRecordArray is invalid.

Action: Fix the connector that is providing the invalid ExtractResponse.

Level: 1

Type: ERROR

Impact: Data

BDSS-20031: Runtime metadata is corrupt. A PIM Row Map record exists but is not linked to a hub master record.

Cause: This occurs when BDSS metadata validation fails. In particular, a PIM metadata record was found but the corresponding hub metadata record was not found. This indicates corruption because each PIM metadata record must be mapped to a hub metadata record.

Action: Clear all BDSS runtime metadata for the affected user. Then perform first-time synchronization for the user. The goal is to start fresh for the affected user.

Level: 1

Type: ERROR

Impact: Data

BDSS-20035: Cannot find a PIM connector endpoint for the current user and Connector {0}

Cause: The Sync-Engine queried all connector URLs for a particular Connector using connector interface method getPimServerEndPoint. However, none of the connector instances provided a connector endpoint for a particular Connector user.

Action: See the log entry to identify the Connector and the corresponding hub user ID for this error. Ensure that the Connector user is configured in the PIM, that BDSS configuration is correct, that all connector instance URLs are properly configured, and that the connector instance can successfully return the endpoint for the Connector and user for which this problem occurs.

Level: 1

Type: ERROR

Impact: Data

BDSS-20038: An invalid key-field detected in BDSS configuration for hub domain {0}.

Cause: An empty or null domain key-field value has been detected in the key-field configuration for the hub domain specified in the log for this error message. The Sync-Engine detected this problem when it examined the key-field String array returned by method SyncConfig::getDomainKeyFields.

Action: Fix the key-field configuration for the specified hub domain.

Level: 1

Type: ERROR

Impact: Data

BDSS-20039: Configuration requires {0} PIM record key fields and yet there are only {1} PIM record description fields in the PIM record metadata.

Cause: The number of description fields available in the record metadata, for a particular PIM record, is not sufficient to support the required key fields specified in configuration.

Action: Examine the log to determine which PIM record has insufficient description fields. Fix configuration for the corresponding connector so the connector provides the description fields that contain the required key fields.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-20040: An error occurred while pushing create, update or delete changes to Connector {0} for hub domain {1}.

Cause: This is a generic high-level error message indicating that an error occurred while pushing create, update, or delete events to the specified Connector and hub domain.

Action: Examine this message in the log to find the pertinent Connector and hub domain. Examine the log for the underlying error that is expected to have been logged prior to this error message. Take appropriate action once the underlying error has been identified.

Level: 1

Type: ERROR

Impact: Data

BDSS-20041: The BDSS Engine will continue to push record changes to the next PIM if any are available.

Cause: The text of this informational message is a supplement to the text of message SYNCENG_PUSH_TO_PIM_ERROR. This message text is logged only when the Sync-Engine has changes to additional PIMs that can be propagated for the same hub domain.

Action: No action is necessary that is specific to this message. Instead, see the action text for error message SYNCENG_PUSH_TO_PIM_ERROR.

Level: 1

Type: ERROR

Impact: Data

BDSS-20043: Unexpected or failure result code detected in an ExtractResponse. ExtractResponse Result Code = {0}. ExtractResponse Error Description = {1}

Cause: An ExtractResultCode value of either PARTIAL_EXTRACT_COMPLETED_OK or PARTIAL_EXTRACT_COMPLETED_NOTOK has been detected in an ExtractResponse received from a connector. An ExtractResponse, with either of these ExtractResultCode values, is considered non-viable for synchronization by the Sync-Engine. Thus, the Sync-Engine cannot perform synchronization with the corresponding ExtractResponse.

Action: Examine the connector, PIM server and configuration corresponding to the failed ExtractResponse. Fix the problem with this connector-related error.

Level: 1

Type: ERROR

Impact: Data

BDSS-20044: Unknown failure code detected in an ExtractResponse. ExtractResponse Result Code = {0}. ExtractResponse Error Description = {1}

Cause: The Sync-Engine detects an unknown ExtractResultCode value in an ExtractResponse received from a connector.

Action: Examine the connector, PIM server and configuration corresponding to the failed ExtractResponse. Fix the problem with this connector-related error.

Level: 1

Type: ERROR

Impact: Data

BDSS-20045: Unknown Connector detected when retrieving an extract response.

Cause: The Sync-Engine recognizes only two Connectors - one for Exchange and the other for Webcenter. The Connector, received in an ExtractResponse from a connector, is not recognized by the Sync-Engine.

Action: Examine the log entry for this message to obtain the Connector retrieved from the problematic ExtractResponse. Examine the connector, PIM server and configuration corresponding to the problematic ExtractResponse. Ensure that the connector provides the correct PIM server type in the ExtractResponse objects it sends to the Sync-Engine.

Level: 1

Type: ERROR

Impact: Data

BDSS-20046: Error getting ExtractResponse objects.

Cause: This message indicates that the Sync-Engine detected an error while receiving ExtractResponse objects during a synchronization session. The underlying problem should already have been logged.

Action: Examine earlier log messages, just prior to this log message, to identify the underlying problem.

Level: 1

Type: ERROR

Impact: Data

BDSS-20047: Null name-key object detected in PIM record description array.

Cause: This error occurs when the Sync-Engine is comparing records using their key fields and detects that the name of a field is invalid, in other words empty or null, for an UpsertRecord provided by a connector ExtractResponse.

Action: Ensure that key-field configuration is correct. Examine recent ExtractRequests in the log to help determine which connector is providing invalid an invalid key-field. Ensure that all connectors are providing valid ExtractRequest responses to the Sync-Engine.

Level: 1

Type: ERROR

Impact: Data

BDSS-20048: An Exception error occurred during synchronization.

Cause: An exception has been detected in the Sync-Engine during synchronization.

Action: Examine the log file for information about this exception.

Level: 1

Type: ERROR

Impact: Data

BDSS-20049: Unable to access FtsLogger class object while processing an Exception error. Exception: {0}.

Cause: An exception has been detected in the Sync-Engine during synchronization. However, the Sync-Engine is unable to log the session ID and hub user ID with this message.

Action: Examine the log file for information about this exception.

Level: 1

Type: ERROR

Impact: Data

BDSS-20050: Invalid Engine Endpoint URL received from configuration. URL is null or empty string.

Cause: An invalid Sync-Engine endpoint URL has been returned from method SyncConfig::getEngineEndPointURL, without the method having thrown an exception.

Action: Confirm that a valid engine endpoint URl is configured.

Level: 1

Type: ERROR

Impact: Data

BDSS-20052: Hub domain synchronization failed.

Cause: This message indicates that an error was detected while synchronizing a particular hub domain. The hub user, synchronization session identifer and hub domain are logged with this message.

Action: Examine this message in the log to determine which hub domain failed. Examine the log to find the underlying cause of the failure.

Level: 1

Type: ERROR

Impact: Data

BDSS-20053: Failed to send extract request.

Cause: An error was detected while attempting while attempting to send an extract request to a connector.

Action: Examine the log to determine the underlying problem which caused the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-20054: Failed to initialize connector user synchronization session. BDSS presumes the connector instance URL is invalid and will clear the connector endpoint for hub user: {0}, Connector: {1}. Synchronization will be attempted in a subsequent sync cycle.

Cause: An error was detected while invoking connector method initializeUserSyncSession.

Action: Examine the log to determine the underlying problem which caused the error. Expect to find the hub user ID, Connector and a description of the underlying exception in the log.

Level: 1

Type: ERROR

Impact: Data

BDSS-20055: Invalid connector endpoint for hub user: {0}, Connector: {1}. The current endpoint will be cleared from configuration.

Cause: An empty or null connector endpoint was returned from configuration via method SyncConfig::getConnectorEndPoint, even though the method did not throw an exception to indicate a problem. As a result, the Sync-Engine will attempt to clear the connector endpoint configured for this user so that a subsequent synchronization will reconfigure the connector endpoint for the user.

Action: Ensure that that connector endpoint configuration is configured correctly, especially for the hub user and Connector logged by this error message. Also, contact Oracle Technical Support to notify them of this error message.

Level: 1

Type: ERROR

Impact: Data

BDSS-20057: Failed connector initialization.

Cause: An error was detected while attempting to initialize the connectors involved in synchronization for a hub-user.

Action: Examine the log to determine the underlying problem which caused the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-20058: Unable to get a connector instance URL for the configured connector endpoint for hub user: {0}, Connector: {1}. The failed connector endpoint will be cleared for this user so a new connector endpoint can be configured during the next synchronization cycle.

Cause: The Sync-Engine was not able to get a connector endpoint for the hub user and Connector specified in this message.

Action: Examine the log entry for information about the underlying exception, and to identify the hub user and Connector for which the problem occurred.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-20059: Unable to get valid connector instance URL for hub user: {0}, Connector: {1}.

Cause: The Sync-Engine has determined that a connector instance URL is invalid, either empty or null, even though an exception did not occur while attempting to retrieve the connector instance URL.

Action: Examine the log message to determine the hub user and Connector for which this error occurred. Ensure that all connector instance URL and endpoint configuration is correct. Also, notify Oracle Technical Support of this issue.

Level: 1

Type: ERROR

Impact: Data

BDSS-20060: Failure detected when attempting to invoke connector method {0}.

Cause: An exception has been detected while invoking the connector method specified by this message.

Action: Examine the log to determine the hub user ID and Connector corresponding to this failure. Also, examine the log to determine which connector method failed.

Level: 1

Type: ERROR

Impact: Other

BDSS-20061: Unable to configure connector endpoint for current hub user and Connector.

Cause: The Sync-Engine detected an exception thrown from method m_SyncConfig.setConnectorEndPoint.

Action: Ensure that configuration and installation are correct. Examine this message in the log to determine the corresponding hub user ID and Connector.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-20062: "Connector method {0} returned error code {1}."

Cause: The Sync-Engine has detected an error code returned from a connector method.

Action: Examine the log to determine which connector method failed and the error code it returned.

Level: 1

Type: ERROR

Impact: Other

BDSS-20063: Detected an invalid message type. Expecting type javax.jms.MapMessage. {0}

Cause: The SyncUserMDB Message Driven Bean has erroneously received a queue message that is not of type javax.jms.MapMessage. SyncUserMDB retrieves messages from a Weblogic Server in-memory queue. It retrieves queue messages having message property RECIPIENT = BDSS SyncUser MDB Recipient.

Action: Ensure that no other software products are sending messages to the configured WLS in-memory queue with queue message having property RECIPIENT = BDSS SyncUser MDB Recipient. For reference, content of the erroneous queue message is appended to this log entry. Notify Oracle Technical Support of this error.

Level: 1

Type: ERROR

Impact: Data

BDSS-20084: PIM Record Description:

Cause: This message string is a label whose purpose is to indicate that PimRecordDescription metadata is being logged for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Data

BDSS-20085: Field Name

Cause: This message string is a label that identifies a single PimRecordDescription field name for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Data

BDSS-20086: Field Value is null

Cause: This message string indicates that a PimRecordDescription.descriptionArray object contains a KeyValuePair object with a null field value. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. Also, fix the cause of that is producing this null field value within the PimRecordDescription metadata of a PIM record.

Level: 1

Type: ERROR

Impact: Data

BDSS-20087: Field Value

Cause: This message string is a label that identifies a single PimRecordDescription field value for a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Data

BDSS-20088: The description array is empty

Cause: This string is never logged by itself but is only ever appended, to another primary logged message string, to provide ancillary information. The primary message may be an error or may simply be a debug message. This message indicates that a PimRecordDescription information is not available. In this case, the PimRecordDescription object is valid, and contains a valid KeyValuePair array object, but the KeyValuePair array has no elements.

Action: See the log for the primary logged message to determine whether any action is needed.

Level: 1

Type: ERROR

Impact: Data

BDSS-20089: The description array is null

Cause: This string is never logged by itself but is only ever appended, to another primary logged message string, to provide ancillary information. The primary message may be an error or may simply be a debug message. This message indicates that PimRecordDescription information is not available for a PIM record. In this case, the PimRecordDescription object is valid but contains a null KeyValuePair array.

Action: See the log for the primary logged message to determine whether any action is needed.

Level: 1

Type: ERROR

Impact: Data

BDSS-20090: Invalid configuration. Configuration is not set to synchronize between exactly two Connector user data sources for a given hub user.

Cause: This problem may also occur if domain information is not configured properly between two Connector users that correspond to the same hub user.

Action: Look in the log to determine which hub user is associated with this message. Ensure that domain configuration matches between Connector users for the specified hub user.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-20092: No PimRecordDescription data is provided in this record

Cause: This string is never logged by itself but is only ever appended, to another primary logged message string, to provide ancillary information. The primary message may be an error or may simply be a debug message. This message indicates that PimRecordDescription information is not available, for a PIM record, because the PimRecordDescription object is null.

Action: See the log for the primary logged message to determine whether any action is needed.

Level: 1

Type: ERROR

Impact: Data

BDSS-20093: A null field name is detected for a PimRecordDescription field name.

Cause: This message string indicates that a field name is null within the PimRecordDescription metadata of a PIM record. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. Also, fix the cause that is producing this null field name.

Level: 1

Type: ERROR

Impact: Data

BDSS-20094: ErrorCode

Cause: This message string is a label that identifies an error code. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message.

Level: 1

Type: ERROR

Impact: Other

BDSS-20095: Hub Domain

Cause: This message string is a label that identifies a hub domain identifier. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Other

BDSS-20096: Hub User

Cause: This message string is a label that identifies a hub user ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Other

BDSS-20097: SessionID

Cause: This message string is a label that identifies a user synchronization session ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Other

BDSS-20098: Connector user

Cause: This message string is a label that identifies a Connector user ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Other

BDSS-20099: Connector Name

Cause: This message string is a label that identifies a PIM connector name. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed. No action is needed based on this message alone.

Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20100: PIM Record Id

Cause: This message string is a label that identifies a PIM record ID. This string is never logged by itself but is only ever appended to another primary logged message string. The primary message may be an error or may simply be a debug message.

Action: See the log for the primary logged message to determine whether any action is needed for the primary log message. No action is needed based on this message alone.

Level: 1

Type: ERROR

Impact: Other

BDSS-20102: Error detected when attempting to delete BDSS master hub metadata record {0}.

Cause: This message indicates that an exception occurred when attempting to delete a hub metadata record from the BDSS database. In particular, method SyncConfig::deleteHubMapRecord threw an exception. The cause of the exception is logged with this message.

Action: See the log to find the exception cause that is logged with this message.

Level: 1

Type: ERROR

Impact: Data

BDSS-20103: Failed to delete an BDSS Pim-Map metadata record corresponding to specified PIM record.

Cause: This message indicates that an exception occurred when attempting to delete a PIM map record from the BDSS database. In particular, method SyncConfig::deletePimMapRecord threw an exception. The cause of the exception is logged with this message.

Action: See the log to find the exception cause that is logged with this message.

Level: 1

Type: ERROR

Impact: Data

BDSS-20104: Hub domain synchronization succeeded.

Cause: This is an informational message that indicates that synchronization has succeeded. The hub-user, sync-session ID, Connector and hub-domain are logged with this message.

Action: No action needed.

Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20106: Started synchronization for user

Cause: This is an informational message that indicates when a synchronization session has started for a hub user. The hub user is specified in the log message header.

Action: No action needed.

Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20107: A user synchronization session has ended. User sync status is {0}.

Cause: This is an informational message that indicates when a hub user synchronization session has ended. In particular, the call to method SyncConfig::setUserSyncSessionToEnded has succeeded. This notification does not imply whether domain synchronization succeeded or not for this same synchronization session. The hub user is specified in the log message header.

Action: No action needed.

Level: 1

Type: NOTIFICATION

Impact: Other

BDSS-20108: Failed to end a user synchronization session.

Cause: This error message indicates that a hub user synchronization session did not end successfully. In particular, the call to method SyncConfig::setUserSyncSessionToEnded threw an exception. This error does not imply whether domain synchronization succeeded or not for this same synchronization session. The hub user is specified in the log message header.

Action: No specific action recommended. However, check configuration - perhaps for the hub user in particular. Also suggest restarting the BDSS application server, or reinstalling BDSS .

Level: 1

Type: ERROR

Impact: Other

BDSS-20109: Hub-domain {0} will not be synchronized for Connector {1} because no other Connector is configured to synchronized it for the current hub-user.

Cause: Hub-user configuration, for the specified hub-domain, is set to synchronize the hub-domain using only a single Connector. It is invalid to synchronize a hub-domain by only a single Connector. The Sync-Engine has modified its only local copy of configuration, for the current hub-user sync-session, so that it will not synchronize the specified hub-domain for the current hub-user sync-session.

Action: Fix configuration for the specified hub-user so that the specified hub-domain is configured to synchronize by more than one Connector. Alternatively, remove the specified hub-domain from configuration for the specified hub-user.

Level: 1

Type: WARNING

Impact: Configuration

BDSS-20110: Connector {0} will not be synchronized, for the current hub-user sync-session, because it is not configured to synchronize any hub-domains.

Cause: The Sync-Engine has determined that hub-user configuration, for the specified Connector, is not valid because it is not configured to synchronize any hub-domains. The specified Connector will not be allowed to synchronize for the current hub-user sync-session.

Action: Ensure that configuration, for the specified hub-user and Connector, is correct for synchronizing at least one hub-domain with another Connector.

Level: 1

Type: WARNING

Impact: Configuration

BDSS-30001: The engine setting for {0} is invalid.

Cause: The Engine Settings for this parameter are invalid.

Action: Use the EngineSettings MBean to enter a valid value for this parameter.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30003: Error during construction of SyncConfig. {0}

Cause: There was an out of memory error or SyncConfig cannot get EngineSettings MBean.

Action: Verify that the EngineSettings MBean was deployed or verify that there was sufficient memory.

Level: 1

Type: ERROR

Impact: Other

BDSS-30006: Can not find section {0} in profile {1}.

Cause: The configuration data for that profile and section cannot be retrieved from the data store.

Action: Verify that the profile and section exist in the data store and that the data store can be reached.

Level: 1

Type: ERROR

Impact: Other

BDSS-30007: EngineSettings - error loading settings. {0}

Cause: Cannot find the engine settings in the preferences store or cannot load the preferences store.

Action: Verify that the preferences store extist on the server and that it is accessable.

Level: 1

Type: ERROR

Impact: Data

BDSS-30011: A {0} was detected when attempting to set the {1} configuration option. {2}

Cause: Cannot find the engine settings in the preferences store, cannot load the preferences store or cannot write to the preferences store.

Action: Verify that the preferences store extist on the server and that it is accessable.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30012: A {0} was detected when attempting to invoke the MBean operation. {1}

Cause: The BDSS MBeans are not accessable or were not successfully installed.

Action: Using the Application Server administration UI, verify that the BDSS MBeans were installed correctly.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30013: A {0} was detected when converting profile data: Profile = {1}, Section = {2}, Parameter = {3}, Value = {4}.

Cause: There was an error converting the Profile settings returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the Profile Settings MBean.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30014: Failed to build open mbeaninfo.

Cause: There was an error loading the MBeans.

Action: Try restarting the MBean console or reinstalling the MBeans.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30015: Operation name cannot be null.

Cause: There was an error loading the MBeans because an operation name was null.

Action: Try reinstalling the MBeans.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30016: Cannot call invoke with null operation name.

Cause: There was an error loading the MBeans because an operation name was null.

Action: Try reinstalling the MBeans.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30017: An error occurred when invoking MBean operation {0}. Exception Class Name = {1}. Caught [{2}].

Cause: There was an error running the operation.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the MBeans.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30018: Cannot find MBean operation {0}.

Cause: There was an error finding the MBean operation.

Action: Try the operation again. If the error persists, using the Application Server administration UI, verify that the BDSS MBeans were installed correctly.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30019: Cannot invoke operation {0} because an invalid parameter was provided to the MBean.

Cause: An invalid parameter was given to the MBean.

Action: Try the action again with valid parameters. If the error continues, contact Suppport.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30020: Error converting the server map. {0}

Cause: There was an error converting the server map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the Server and Connectors MBean.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30021: Error converting the connector map. {0}

Cause: There was an error converting the connector map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the Server and Connectors MBean.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30022: Error getting hub users. {0}

Cause: This may be an error in the configuration of the Hub User or the Hub User does not exist.

Action: Ensure that the hub user exists in configuration and is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30023: Error getting Connector users. {0}

Cause: This may be an error in the configuration of the Connector user or the Connector user does not exist.

Action: Ensure that the Connector user exists in configuration and is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30024: Error getting domains. {0}

Cause: This may be an error in the configuration of the domain.

Action: Ensure that the domain exists in configuration and is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-30025: Error getting records. {0}

Cause: This may be an error in the database for the record.

Action: Ensure that the record exists in the database.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35001: Cannot create a Connector user with the login {0} and cannot map the user to the hub user {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35002: The configuration parameter {0} in the section {1} of the profile {2} cannot be deleted.

Cause: The configuration was not accessable.

Action: Ensure your database is running and you can log into it from a client.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35003: Cannot delete the record with an id of {0}.

Cause: The data store was not accessable or the user does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35004: Cannot find the hub record with an id of {0} for user {1}.

Cause: The data store was not accessable or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user and record exist in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35005: Cannot find the hub record for the PIM record with an id of {0} for user {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35006: Cannot find the hub user {0}.

Cause: The data store was not accessable or the user does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the hub user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35007: Cannot find the {0} LOV with a value of {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35008: Cannot find the {0} object with an id of {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35009: Cannot find the PIM record with an id of {0}.

Cause: The data store was not accessable or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user and record exist in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35010: Cannot find the PIM record with an id of {0} for user {1}.

Cause: The data store was not accessable or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user and record exist in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35011: Cannot find the PIM record for the hub record with an id of {0} for user {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35012: Cannot find the Connector user with the ID of {0} for the Connector named {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35013: Cannot find the record associated data for the record {0}.

Cause: The data store was not accessable or the user or record data does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user and record exist in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35014: Cannot return users from the data source.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35015: Cannot retrieve {0} records for user {1}.

Cause: The data store was not accessable or the user does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35016: Cannot remove the {0} object with an id of {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35017: Cannot update the sync level for the domain {0} for the Connector named {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35018: Cannot update the hub record with an id of {0} for user {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35019: Cannot update or create the {0} object with an id of {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35020: Cannot update the PIM record with an id of {0} for user {1}.

Cause: The data store was not accessable or the record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the record exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35021: Cannot update the session for hub user {0}.

Cause: The user cannot be found in configuration or the data store is not allowing the update.

Action: Ensure your data store is running and you can log into it from a client and that the hub user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35022: The configuration parameter {0} in the section {1} of the profile {2} cannot be writen to the data store.

Cause: The configuration was not accessable or cannot be writen to.

Action: Ensure your database is running and you can log into it from a client.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35023: Cannot store record associated data for the record with an id of {0}.

Cause: The data store was not accessable or the user does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35024: Cannot store record description data for the record with an id of {0}.

Cause: The data store was not accessable or the user or record does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user and record exist in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35025: Cannot write user associated data for user {0}.

Cause: The data store was not accessable or cannot be writen to.

Action: Ensure your data store is running and you can log into it from a client.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35026: Cannot write the {0} domain sync status for user {1} on the Connector named {2}.

Cause: The data store was not accessable or cannot be writen to or configuration for this user is corrupted.

Action: Ensure your data store is running and you can log into it from a client. Also ensure the configuration for this user is correct.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35027: The configuration for the Connector {0} has an error.

Cause: There is an error in the configuration of this Connector.

Action: Review the configuration for this Connector and resolve the problem.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35028: The configuration for the domain {0} has an error.

Cause: There is an error in the configuration of this domain.

Action: Review the configuration for this domain and resolve the problem.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35029: One of the Connector user mappings is invalid for hub user {0}.

Cause: The configuration for one of the hub user to Connector user mappings is corrupted or not present.

Action: Ensure that the mapping exists in configuration and is valid.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35030: The configuration for the Connector instance {0} is not correct. Review the configuration for {1}.

Cause: There was missing configuration for this Connector instance.

Action: Review the configuration for this Connector instance and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35031: The configuration for the PIM domain {0} is not correct. Review the configuration for {1}.

Cause: There was missing configuration for this domain.

Action: Review the configuration for this domain and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35032: The configuration for the user {0} is not correct. Review the configuration for the user on Connector {1}.

Cause: There was missing configuration for this user.

Action: Review the configuration for this user and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35033: The Connector user for Connector {0} does not exist for hub user {1}, or there is more than one Connector user with this name configured for this Connector.

Cause: This hub user had no Connector user associated to it for the Connector.

Action: Review the configuration for this user and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35034: The configuration for the Connector {0} is not correct. Review the configuration for {1}.

Cause: There was missing configuration for this Connector.

Action: Review the configuration for this Connector and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35035: The configuration for the profile {0} is does not exist. Review the configuration for the profile.

Cause: There was missing configuration for this profile.

Action: Review the configuration for this profile and correct any configuration problems if needed.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35036: The configuration parameter {0} in the section {1} of the profile {2} does not exist.

Cause: There was missing configuration for this profile.

Action: Review the configuration for this profile and correct any configuration problems if needed.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35037: There is no {0} for the user {1}.

Cause: There was missing configuration for this user.

Action: Review the configuration for this user and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35038: The configuration for the PIM server {0} has an error.

Cause: There is an error in the configuration of this PIM server.

Action: Review the configuration for this PIM server and resolve the problem.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35039: A Connector user with a login of {0} already exists for the Connector {1}.

Cause: The configuration for at least one of the Connector users already exists. Verify this user is not already in configuration and that this is the correct ID for the Connector.

Action: Ensure that the mapping exists in configuration and is valid.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35040: The user is not in the same session whose ID is {0}.

Cause: The session ID for the user is not the same as the stored session ID. This may be due to 2 seperate BDSS engines processing the same user.

Action: Ensure only one BDSS dispatcher is running at a time and that the user is not stuck in a sync session.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35041: Cannot store associated data for the user {0}.

Cause: The data store was not accessable or the user does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35042: Cannot store metadata for the user {0}.

Cause: There was an error while storing the configuration of this user.

Action: Verify the data base can be accessed and that the BDSS configuration is correct.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35043: Cannot store a record for the user {0}.

Cause: The data store was not accessable or the user does not exist in configuration.

Action: Ensure your data store is running and you can log into it from a client and that the user exists in configuration.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35044: There were too many {0} records found for {1}.

Cause: There were too many records found that matched the query.

Action: Ensure your configuration is correct and that the users data is not corrupted

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35045: The configuration for the user {0} has an error.

Cause: There is an error in the configuration of this user.

Action: Review the configuration for this user and resolve the problem.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35046: Cannot find the associated data for user {0}.

Cause: The associated data for the user is not in the database.

Action: This may not be an error if this is the first time sync for the user. If not, verify the user is in the database and the database is accessable.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35047: Could not find entity to update.

Cause: The entity is not in the database.

Action: This may not be an error if this is the first time sync for the user. If not, verify the missing entity is in the database and the database is accessable.

Level: 1

Type: ERROR

Impact: Other

BDSS-35048: Entity already exists.

Cause: The entity already exists in the database and cannot be duplicated.

Action: Determine which entity is being duplicated and take appropriate action to resolve the duplication.

Level: 1

Type: ERROR

Impact: Other

BDSS-35049: Could not find entity to update.

Cause: The entity in the database.

Action: This may not be an error if this is the first time sync for the user. If not, verify the missing entity is in the database and the database is accessable.

Level: 1

Type: ERROR

Impact: Other

BDSS-35050: Either no record or too many records were returned for this Connector user.

Cause: There is no hub user associated to this Connector user or there is more than one hub user associated with this Connector user.

Action: Verify that the configuration for this user is correct and that only one hub user is associated to this Connector user.

Level: 1

Type: ERROR

Impact: Other

BDSS-35051: Cannot store the cached sync state for the user {0}.

Cause: There was an error while storing the cached sync state of this user.

Action: Verify the data base can be accessed, that the BDSS configuration is correct and the cached sync state exists.

Level: 1

Type: ERROR

Impact: Data

BDSS-35052: Cannot store the permanent sync state for the user {0}.

Cause: There was an error while storing the permanent sync state of this user.

Action: Verify the data base can be accessed, that the BDSS configuration is correct.

Level: 1

Type: ERROR

Impact: Data

BDSS-35053: Could not obtain the Pim Record Versions for Connector User {0}, HubDomain {1}, Connector {2}. Exception detected: {3}.

Cause: There was an error while attempting to obtain the Pim Record Version identifiers from the BDSS database for this user.

Action: Verify the database can be accessed and that the BDSS configuration is correct.

Level: 1

Type: ERROR

Impact: Data

BDSS-35054: An invalid Connector domain synchronization level has been detected.

Cause: An invalid Connector domain synchronization level has been detected in configuration.

Action: Review Connector domain synchronization level configuration and correct it.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35055: An invalid Connector user synchronization level has been detected.

Cause: An invalid Connector user synchronization level has been detected in configuration.

Action: Review Connector user synchronization level configuration and correct it.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35057: There is more than one record with the Hub user login of {0}.

Cause: There is more than one hub user with this login. This is a configuration error.

Action: Review the configuration for this user and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35063: Cannot find the domain {0} for Connector user Id {1}.

Cause: The supplied domain does not exist for the Connector user. This could be a configuration error.

Action: Review the configuration for this user and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35070: Cannot find the PIM server instance {0} for Connector {1}.

Cause: Cannot update the PIM server instance. This could be a configuration error.

Action: Review the configuration for this PIM server instance and correct any configuration problems.

Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35071: Cannot find the domain {0} for the Connector named {1}.

Cause: Cannot update the domain. This could be a configuration error.

Action: Review the configuration for this domain and correct any configuration problems.

Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-35072: Cannot update the filter {0} for the domain {1} for the Connector named {2}.

Cause: Cannot update the domain filter. This could be a configuration error.

Action: Review the configuration for this domain and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35073: Cannot find the LOV for the PIM server type {0}.

Cause: Cannot find the LOV for the PIM server type. This could be a configuration error.

Action: Review the LOVs, ensure you are using the correct LOV and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35074: Cannot create or update the connector {0}.

Cause: Cannot create or update the connector. This could be a configuration error or a data base access error.

Action: Review the configuration and database connect information. Then correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35075: Cannot delete the connector {0}.

Cause: Cannot delete the connector. This could be a configuration error or a data base access error.

Action: Review the configuration and database connect information. Then correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35077: Cannot delete the filter {0} for the domain {1} for the Connector named {2}.

Cause: Cannot delete the domain filter. This could be a configuration error.

Action: Review the configuration for this domain and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35078: Cannot get connector details.

Cause: Cannot get the details for the connectors. This could be a configuration error or a data base access error.

Action: Review the configuration and database connect information. Then correct any configuration problems.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35079: Error converting the connector instance map. {0}

Cause: There was an error converting the connector instance map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the Servers and Connectors MBean.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35080: Error converting the domain map. {0}

Cause: There was an error converting the domain map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the Servers and Connectors MBean.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35081: Error converting the domain filter map. {0}

Cause: There was an error converting the domain filter map returned from the database to a format that will display properly.

Action: Try the operation again. If the error persists, check the data in the data base or re-install the Servers and Connectors MBean.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-35082: Mismatcher lenths of lists for records and record versions.

Cause: The length for the list of records given to RuntimeCfgMge does not match the length of the list of versions.

Action: Retry the operation. If the problem persists, redeploy the BDSS ear files.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50002: An Incremental Change Synchronization conflict has occurred on the Exchange record.\r%s\r\tBDSS record ICS Information: \r\t\t%s\r\tExchange Record ICS Information: \r\t\t%s\rAttempting to resolve the conflict (BDSS Wins).

Cause: A record in Exchange has been modified by an Exchange user just prior to BDSS attempted to update the record.

Action: No action required. The connector will programmatically attempt to resolve the Incremental Change Synchronization conflict such that BDSS wins.

Level: 1

Type: TRACE

Impact: Data

BDSS-50004: Unable to resolve Incremental Change Synchronization conflict.\r%s

Cause: The MAPI properties used by Incremental Change Synchronization (PR_SOURCE_KEY, PR_CHANGE_KEY, PR_PREDECESSOR_CHANGE_LIST) may be corrupted.

Action: The end user should use Microsoft Outlook to first try to resolve the conflict manually. If this fails, the Outlook user should delete the record and recreate it.

Level: 1

Type: ERROR

Impact: Data

BDSS-50005: Failed while establishing a MAPI session or obtaining IExchangeManageStore using the application user id '%s'. Attempting logon using the 'legacyExchangeDN' of user %s (%s).

Cause: The identity of the administrative user that the connector application runs as is ambiguously defined in Active Directory. For example, there is another user in Active Directory that has a similar sAMAccountName.

Action: Run the DCOMCNFG utility to configure the connector application to run as a different user or use the 'Active Directory Users and Computers' console to manually resolve the ambiguity. Perform one of these two options if the connector fails to programmatically resolve the ambiguity.

Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-50006: Successfully established a MAPI session and obtained IExchangeManageStore using legacyExchangeDN for user %s (%s).

Cause: The identity of the administrative user that the connector application runs as is ambiguously defined in Active Directory. For example, there is another user in Active Directory that has a similar sAMAccountName.

Action: No action is required because the connector successfully resolved the ambiguous user definition.

Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-50007: Failed to get Active Directory property. Property Name = %s.

Cause: The specified property is not desigated as one to be replicated from Active Directory to the Global Catalog.

Action: Configure Active Directory such that the specified property is replicated to the Global Catalog.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50010: Unable to resolve or access the synchronization folder. Folder path = %s. Admin User Id = %s. Admin Server Name = %s.

Cause: The receive folder of the user message store does not have the folder identifier property needed to access the folder that is to be synchronized.

Action: Use the Active Directory Users and Computers console to recreate the user mailbox.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50011: Unable to establish a MAPI session. A failure occurred attempting to obtain the user name that the application is running under.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'OpenThreadToken', 'OpenProcessToken', 'GetCurrentThread', 'GetCurrentProcess', 'GetTokenInformation', and 'LookupAccountSid'.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50012: Unable to establish a MAPI session. Admin User Id = %s. Admin Server Name = %s.

Cause: Connector is running on a machine that either currently has Microsoft Outlook installed or at some point in the past had Outlook installed.

Action: Microsoft does not support running Exchange System Managment tools on any box that has ever had Outlook installed on it. Install the connector on a different machine that has never had Microsoft Outlook installed on it or reimage the machine and reinstall the Exchange connector.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50013: Unable to logon to MAPI. Admin User Id = %s. Admin Server Name = %s. %s

Cause: Cannot access mapisvc.inf.

Action: Verify file exists on the connector machine and the administrative user has full access to the file.

Level: 1

Type: ERROR

Impact: Security

BDSS-50014: MAPI logoff failed. Admin User Id = %s. Admin Server Name = %s.

Cause: An error occurred when attempting to logoff the MAPI session.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Session

BDSS-50015: Failed to open the user message store. Admin User Id = %s. Admin Server Name = %s. Synchronizing users msExchHomeServerName = %s. Synchronizing users legacyExchangeDN = %s.

Cause: The administrative user does not have sufficient priviledges to access the synchronizing users mailbox.

Action: Use the Active Directory Users and Computers console to grant the administrator full mailbox priviledges to the synchornizing users mailbox.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50016: Failed to create a MAPI profile. Admin User Id = %s. Admin Server Name = %s. Please ensure the user that the application is running under has administrative access rights on the machine and verify the system drive has sufficient disk space to contain a MAPI profile.

Cause: Could not create or configure a message service.

Action: Ensure the correct version of the Exchange System Managment tools is installed on the connector machine.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50018: Failed to verify content of mapisvc.inf file. Admin User Id = %s. Admin Server Name = %s. Please ensure the user that the application is running under has administrative access rights on the machine.

Cause: Could not verify the content of the mapisvc.inf file.

Action: Ensure the correct version of the Exchange System Managment tools is installed on the connector machine. Verify the file exists on the system and is not corrupted.

Level: 1

Type: ERROR

Impact: Security

BDSS-50019: Failed to extract the Pim domain.

Cause: The connector could not extract data from the synchronizing users mailbox.

Action: Verify connector and user configuration. Examine log file for original error.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50021: Failed to associate the user with the application.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Other

BDSS-50022: The user is not associated with the application.

Cause: A request for a user that is not being synchronized by the connector application instance was received.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support..

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50023: Failed to initialize COM.

Cause: COM could not be initialized with the current thread.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support..

Level: 1

Type: ERROR

Impact: Operating System

BDSS-50025: Failed to initialize synchronization agent. Pim Folder Name = %s.

Cause: Invalid MAPI restriction.

Action: Verify the Pim Filter Condition is configured correctly.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50026: Failed to obtain an Exchange Synchronizer interface (MAPI property PR_CONTENTS_SYNCHRONIZER). Pim Folder Name = %s.

Cause: Prerequisite software not installed correctly.

Action: Ensure the correct version of the Exchange System Managment tools is installed on the connector machine.

Level: 1

Type: ERROR

Impact: Data

BDSS-50027: Failed to obtain an Exchange Collector interface (MAPI property PR_COLLECTOR). Pim Folder Name = %s.

Cause: Prerequisite software not installed correctly.

Action: Ensure the correct version of the Exchange System Managment tools is installed on the connector machine.

Level: 1

Type: ERROR

Impact: Data

BDSS-50028: Failed to configure the Exchange Synchronizer. Pim Folder Name = %s.

Cause: Prerequisite software not installed correctly.

Action: Ensure the correct version of the Exchange System Managment tools is installed on the connector machine.

Level: 1

Type: ERROR

Impact: Data

BDSS-50031: Failed to copy an attachment.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPIProp::CopyTo' and 'IMAPIProp::SetProps'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50032: Failed to open an attachment.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMessage::OpenAttach'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50033: Failed to create an attachment.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMessage::CreateAttach'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50034: Failed to save an attachment.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMessage::GetAttachmentTable' and 'IMAPIProp::SaveChanges'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50035: Failed setting the columns of a MAPI table.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPITable::SetColumns' and 'IMAPIProp::SaveChanges'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50036: Failed to obtain the attachment rows.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPITable::QueryRows'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50037: Failed to get the existing properties of an item.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPIProp::GetProps'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50038: Failed to copy the existing properties of an item.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPIProp::SetProps'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50039: Failed to set MAPI property %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPIProp::SetProps'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50040: Failed to obtain MAPI named properties from property tags. Property Tags = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for methods 'IMAPIProp::GetNamesFromIDs'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50042: MAPI returned an invalid named property. Property Information = %s.

Cause: The Exchange record has a invalid named property whose 'Kind' attribute is not 0 ('MNID_ID') or 1 ('MNID_STRING').

Action: Delete or recreate the Exchange record.

Level: 1

Type: ERROR

Impact: Data

BDSS-50043: Invalid LDAP search filter parameter. Active Directory Property Name = %s. Active Directory Property Value = %s.

Cause: The property used in the search filter portion of the LDAP search filter is not supported by the connector.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50044: Failed to obtain the server name of the domain controller from Active Directory.

Cause: A serverless bind request (ldap://rootDSE) to Active Directory failed or did not contain a 'ServerName' value. The connector can not bind to Active Directory on the current domain.

Action: Configure the 'Preferred Global Catalog Servers' to specify specific Global Catalog servers that the connector should query. Restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50052: Invalid Perferred Domain configuration. The following entries will be ignored: %s.

Cause: Invalid preferred domain configuration.

Action: Fix the configuration and restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50053: There is no MAPI session established for the connector application. No users can synchronize.

Cause: Microsoft API failure when initializing and logging in to MAPI.

Action: Refer to Microsoft documentation on 'MAPIInitialize', and 'MAPILogonEx'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50054: Failed to convert domain field definitions to MAPI equivalent. Additional information: Current field name: %s. Current field class: %s. Current field type: %s.

Cause: Microsoft API failure when resolving MAPI named fields to property tags.

Action: Verify field configuration in the domains .XSD file. Refer to Microsoft documentation on 'IMsgStore::GetIDsFromNames'.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50055: Failed to base-64 decode the following encoded string: %s.

Cause: User or record level associated data, stored in the BDSS store, is corrupt.

Action: The user needs to be reinitialized. Please see the product documentation for the procedure.

Level: 1

Type: ERROR

Impact: Data

BDSS-50056: Failed to convert MAPI properties to record associated data. MAPI property values = %s.

Cause: The Exchange record has a corrupted PR_SOURCE_KEY, PR_CHANGE_KEY, and/or PR_PREDECESSOR_CHANGE_LIST MAPI property value.

Action: Recreate or delete the record from the Exchange mailbox.

Level: 1

Type: ERROR

Impact: Data

BDSS-50057: Failed to convert record assocociated data to MAPI properties. Associated data values = %s.

Cause: The BDSS store has a corrupted or missing PR_SOURCE_KEY, PR_CHANGE_KEY, and/or PR_PREDECESSOR_CHANGE_LIST MAPI property value stored as Pim Record Associated Data.

Action: Delete the record from the Exchange mailbox and resynchronize the user or reinitialize the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-50058: Failed to create record associated data for an outbound record.\rSource Record Associated Data values: %s\rTarget Record Associated data values %s\rSource Key %s.

Cause: Invalid call.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50059: Failed to import a Pim record because a CSSMAPIMessage object could not be created or initialized.

Cause: The Exchange record has a corrupted or missing PR_SOURCE_KEY, PR_CHANGE_KEY, and/or PR_PREDECESSOR_CHANGE_LIST MAPI property value.

Action: Recreate or delete the Exchange record from the Exchange mailbox and resynchronize the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-50060: The COM interface identified by GUID %s is not supported by object %s.

Cause: Prerequisite software not installed correctly.

Action: Reinstall all prerequisite software.

Level: 1

Type: ERROR

Impact: Deployment

BDSS-50061: Failed to convert a Pim XML field value to a MAPI equivalent. MAPI data type = %s. Pim Record Id = %s. Field Name = %s. XML Field Value = %s. MAPI Property Tag = %s.

Cause: The field data is corrupted or invalid.

Action: Modify the field value in the source Pim and resynchronize the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-50062: Failed to convert a MAPI field value to a Pim XML equivalent. MAPI data type = %s. Pim Record Id = %s. Field Name = %s. MAPI Property Tag = %s.

Cause: The field data is corrupted or invalid.

Action: Modify the field value in Exchange and resynchronize the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-50063: Failed to convert string %s to binary representation.

Cause: The Pim record identifier value provided by BDSS is invalid and can not be converted to an array of bytes.

Action: The user needs to be reinitialized. Please see the product documentation for the procedure.

Level: 1

Type: ERROR

Impact: Data

BDSS-50064: Failed to add the MAPI field data to the field collection. Pim Record Id = %s. Field Id = %s. Field Value = %s. MAPI Property = %s.

Cause: A field definition for a MAPI named property could not be found in the cache of fields.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50065: Unexpected field converter type. Expected: %s.

Cause: Object type is invalid.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50066: Failed to convert a MAPI delete message to a BDSS delete. Pim Record Id = %s.

Cause: Microsoft API failure. The MAPI array containing the identifiers of deleted records is invalid.

Action: Refer to Microsoft documentation on 'IExchangeImportContentsChanges::ImportMessageDeletion'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50067: Failed to convert a MAPI upsert message. Pim Record Id = %s.

Cause: If the HRESULT error code is not of the form '0x800750nn or '0x800760nn', the failure occurred as the result of calling a Microsoft API.

Action: Examine the connector log file content to obtain additional information about the HRESULT. See Microsoft documentation about the HRESULT and the API that returned the error code.

Level: 1

Type: ERROR

Impact: Data

BDSS-50068: Failed to add IStream-based property values to the fields collection. Pim Record Id = %s.

Cause: Microsoft API failure.

Action: See Microsoft documentation on 'IStream::Seek' and 'IStream::Read'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50069: Failed to create a MAPINAMEID structure for MAPI named field %s.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50070: Failed to save Pim record.

Cause: If the HRESULT error code is not of the form '0x800750nn or '0x800760nn', the failure occurred as the result of calling a Microsoft API.

Action: Examine the connector log file content to obtain additional information about the HRESULT. See Microsoft documentation about the HRESULT and the API that returned the error code.

Level: 1

Type: ERROR

Impact: Data

BDSS-50071: Failed to open a MAPI property. Requested MAPI property = %s.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50072: Exchange requested a MAPI property tag for an unknown MAPI named field.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'Incremental Change Synchronization.'s

Level: 1

Type: ERROR

Impact: Data

BDSS-50073: Failed to obtain COM interface %s.

Cause: The specified COM interface is not available.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50075: Detected an error with the following configuration option: Profile = '%s'. Section = '%s'. Parameter = '%s'. Value = '%s'. Using default value of '%s'.

Cause: Invalid configuration.

Action: Fix the specified configuration option and restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50076: The following configuration is invalid because the value is not in an acceptable range: Profile = '%s'. Section = '%s'. Parameter = '%s'. Value = '%s'. Acceptable range is %s to %s (inclusive). Using default value of '%s'.

Cause: Invalid configuration.

Action: Fix the specified configuration option and restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50077: The following configuration is invalid because the value is invalid for boolean options. Profile = '%s'. Section = '%s'. Parameter = '%s'. Value = '%s'. Acceptable values for turning an option on are 'true' (case insensitive) or '1' and for turning an option off use 'false' (case insensitive) or '0'. Using default value of '%s'.

Cause: Invalid configuration.

Action: Fix the specified configuration option and restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50080: No server name configured.

Cause: The 'Preferred Global Catalog Servers' configuration is missing a server name.

Action: Fix the specified configuration option and restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50084: Failed to convert MAPI associated data properties to BDSS record associated data. No assocciated data was provided.

Cause: The Exchange record does not have the MAPI associated data properties (PR_SOURCE_KEY, PR_CHANGE_KEY, PR_PREDECESSOR_CHANGE_LIST, PR_LAST_MODIFICATION_TIME) or the connector was unable to obtain the properties.

Action: Recreate or delete the Exchange record and resynchronize the user.

Level: 1

Type: ERROR

Impact: Data

BDSS-50085: Failed to convert record level associated data properties provided by BDSS to MAPI associated data. No associated data was provided.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50086: Failed to convert base-64 encoded strings to BDSS record associated data.

Cause: Could not allocate memory to contain the decoded strings.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50087: Failed copying the predecessor change list record associated data property.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50088: Failed to create a PR_CHANGE_KEY and/or PR_PREDECESSOR_CHANGE_LIST value.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50094: Failed because of an invalid parameter.

Cause: The parameter is invalid.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50095: Failed to convert date/time value '%s' to an equivalent system time value.

Cause: Date value not in correct format of 'YYYY-MM-DDTHH:MM:SS.xxxZ'.

Action: Verify date format from the source Pim.

Level: 1

Type: ERROR

Impact: Data

BDSS-50096: Failed to convert system date/time value to an equivalent BDSS format.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50097: Failed to create a globally unique identifier (GUID).

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for 'UuidCreate' and 'UuidToString'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50098: Failed to convert string %s to a long.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation for 'wcstol'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50099: Failed parsing the Common Name (CN) from %s.

Cause: Could not parse out the last CN from a msExchHomeServerName value.

Action: Configure the users' Exchange account such that the fully qualified distinguished name contains a 'CN' value.

Level: 1

Type: ERROR

Impact: Data

BDSS-50100: Unable to convert Xml Schema type '%s' to a supported MAPI data type.

Cause: The Pim Domain .XSD file contains a field with an unsupported data type. The connector does not support mapping this XML type to a MAPI data type.

Action: Modify the Pim Domain .XSD file and change the field definition to have a supported Xml data type. Supported types are: 'xsd:string', 'xsd:datetime', 'xsd:boolean', 'hubpercent', 'exchangeunsignedlong', 'hubtokens', 'exchangetaskpriority', and 'exchangetaskstatus'. If the field is not one of the supported types, remove the field from the .XSD. If the .XSD file is modified, restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50101: Unable to convert Xml Schema type '%s' to a supported MAPI data type. Field Id = %s.

Cause: The Pim Domain .XSD file contains a field with an unsupported data type. The connector does not support mapping this XML type to a MAPI data type.

Action: Modify the Pim Domain .XSD file and change the field definition to have a supported Xml data type. Supported types are: 'xsd:string', 'xsd:datetime', 'xsd:boolean', 'hubpercent', 'exchangeunsignedlong', 'hubtokens', 'exchangetaskpriority', and 'exchangetaskstatus'. If the field is not one of the supported types, remove the field from the .XSD. If the .XSD file is modified, restart BDSS.

Level: 1

Type: ERROR

Impact: Data

BDSS-50102: Invalid call made by Exchange MAPI service provider.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'Incremental Change Synchronization'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50103: No column names provided for the MAPI table.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Data

BDSS-50104: Active Directory search results:\r\tSearch string: %s\r\tProperty Names and Values: %s

Cause: The connector can not communicate with a server containing the Global Catalog.

Action: Verify the server is running and the Global Catalog is available. Verify the LDAP and GC ports are open.

Level: 1

Type: ERROR

Impact: Data

BDSS-50105: The connector application failed to initialize.

Cause: Could not create a unique name for the connector application.

Action: See Microsoft documentation on 'UuidCreate' and 'UuidToString'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50109: Failed to create connector monitor thread or event object. Idle connector applications will not be forced to terminate.

Cause: Microsoft API failure.

Action: See Microsoft documentation for 'CreateThread' and 'CreateEvent'.

Level: 1

Type: ERROR

Impact: Other

BDSS-50111: Failed to establish an SSL connection because the server is requesting client authentication and no certificate is available.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50112: Failed to establish an SSL connection because the Certificate Authority that issued the Exchange Server certificate is not a trusted Certificate Authority on the connector machine.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50113: Failed to establish an SSL connection because the SSL certificate date is bad or expired.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50114: Failed to establish an SSL connection because the SSL certificate common name (host name field) is incorrect. For example, if you entered a common name of www.server.com and the common name on the certificate says www.different.com.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50115: Client authorization is not set up on this computer.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50116: The data being submitted to an SSL connection is being redirected to a non-SSL connection.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50117: The SSL certificate contains errors

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50118: The content is not entirely secure. Some of the content being viewed may have come from unsecured servers.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50119: No more handles could be generated at this time

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Data

BDSS-50120: The URL is invalid.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Data

BDSS-50121: The requested option cannot be set, only queried.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50122: WinINet support is being shut down or unloaded.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Other

BDSS-50123: The requested operation is invalid.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Other

BDSS-50124: The operation was canceled, usually because the handle on which the request was operating was closed before the operation completed

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Other

BDSS-50125: The requested item could not be located.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Other

BDSS-50126: The attempt to connect to the server failed.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50127: The connection with the server has been terminated.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50128: The connection with the server has been reset.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50129: The function needs to redo the request.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50130: The request to the proxy was invalid.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50131: The request failed because the handle already exists

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50132: The application is moving from a non-SSL to an SSL connection because of a redirect.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50133: The application is moving from an SSL to an non-SSL connection because of a redirect.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50134: The request has timed out.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50135: The connector application experienced an internal error loading the SSL libraries.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Security

BDSS-50136: The Exchange Server indicated in the request is unreachable.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Network

BDSS-50137: The required protocol stack is not loaded and the connector application cannot start WinSock.

Cause: Microsoft WinINet API failure.

Action: Refer to Microsoft WinINet documentation.

Level: 1

Type: ERROR

Impact: Installation

BDSS-50138: Failed to allocate memory.

Cause: Not enough memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Memory

BDSS-50142: Failed to process the extraction of Hub domain '%s'.

Cause: Could not post request to a extract thread.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50145: An error occurred when extracting data from Exchange for Pim Domain %s.

Cause: If the HRESULT error code is not of the form '0x800750nn or '0x800760nn', the failure occurred as the result of calling a Microsoft API.

Action: See Microsoft documentation on 'IExchangeExportChanges::Synchronize'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50147: Failed to save the synchronization state. Connector Runtime Library Url = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documention on 'CSoapSocketClientT' APIs.

Level: 1

Type: ERROR

Impact: Data

BDSS-50148: Failed to send an extract response to the hub. Hub callback URL = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documention on 'CSoapSocketClientT' APIs.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50150: An error occurred when ending the synchronization for the Hub Domain. Number of Extract Response Packets set to the hub = %s.

Cause: Could not save the Source Key Pool properties to the BDSS store.

Action: Attempt to save the Source Key Pool properties by resynchronizing the user.

Level: 1

Type: ERROR

Impact: Other

BDSS-50154: Failed to transform the following %s message.\r%s.\rVerify the content of XSL file = %s. %s

Cause: Microsoft API failure.

Action: Refer to Microsoft MSXML documentation for more information about the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50155: Failed to parse the following Hub XML message\r%s. %s

Cause: Microsoft API failure.

Action: Refer to Microsoft MSXML documentation for more information about the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50157: Failed to load XSL files needed for transformation. XSL File = %s. %s

Cause: Microsoft API failure.

Action: Refer to Microsoft MSXML documentation for more information about the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50158: Failed to load XML. XML = %s. %s

Cause: Could not load the source XML.

Action: Verify the XML is valid. If invalid, verify the XSD and XSL files are valid. Restart BDSS if any XSD or XSL files are modified.

Level: 1

Type: ERROR

Impact: Data

BDSS-50159: The '%s' Pim record operation failed for the Exchange record.\r%s

Cause: If the HRESULT error code is not of the form '0x800750nn or '0x800760nn', the failure occurred as the result of calling a Microsoft API.

Action: Examine the connector log file content to obtain additional information about the HRESULT. See Microsoft documentation about the HRESULT and the API that returned the error code.

Level: 1

Type: ERROR

Impact: Data

BDSS-50171: Failed parsing XML. The error occurred while parsing the XML element %s or the XML element after it. %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft MSXML documentation for more information about the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50172: Failed to parse the Pim Xml message: %s. %s

Cause: Microsoft API failure.

Action: Refer to Microsoft MSXML documentation for more information about the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50175: Failed to dispatch the domain extraction request to a worker thread.

Cause: Queue has exceeded the thread capacity.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50176: Failed to queue the domain extraction request.

Cause: Microsoft API failure.

Action: See Microsoft documentation on 'SetEvent'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50177: Failed to create a '%s' thread.

Cause: Microsoft API failure.

Action: See Microsoft documentation on 'CreateThread'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50178: Failed to get Associated Data from the BDSS store.\r\tAssoc Data Identifier = %s.\r\tRuntime Library URL = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documention on 'CSoapSocketClientT' APIs.

Level: 1

Type: ERROR

Impact: Data

BDSS-50180: Failed to set Associated Data to BDSS store.\r\tAssoc Data Identifier = %s.\r\tAssoc Data = %s.\r\tRuntime Library URL = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documention on 'CSoapSocketClientT' APIs.

Level: 1

Type: ERROR

Impact: Data

BDSS-50190: An error occurred sending an extract response containing %s records to the hub.\rAdditional information:\r\tHub callback URL: %s\r\tHTTP Status Code: %s\r\tSoap Error: %s\r\tAdditional Error Information:\r%s

Cause: Microsoft API failure.

Action: Refer to Microsoft documention on 'CSoapSocketClientT' APIs.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50191: SOAP error - initialization failed.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50192: SOAP error - out of memory.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_OUTOFMEMORY'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50193: SOAP error - failed in generating the response.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_GENERATE_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50194: SOAP error - failed connecting to server.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_CONNECT_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50195: SOAP error - failed in sending message.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_SEND_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50196: SOAP error - server error.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_SERVER_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50197: SOAP error - a SOAP Fault was returned by the server.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_SOAPFAULT'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50198: SOAP error - failed in parsing SOAP fault returned by server.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_PARSEFAULT_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50199: SOAP error - failed in reading response.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_READ_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50200: SOAP error - failed in parsing response.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'SOAPCLIENT_PARSE_ERROR'.

Level: 1

Type: ERROR

Impact: Requests/Responses

BDSS-50204: An error occurred calling the Connector Runtime Library method '%s'.\rAdditional information:\r\tConnector Runtime Library URL: %s\r\tHTTP Status Code: %s\r\tSoap Error: %s\r\tAdditional Error Information:\r%s

Cause: Microsoft API failure.

Action: Refer to Microsoft documention on 'CSoapSocketClientT' APIs.

Level: 1

Type: ERROR

Impact: Data

BDSS-50209: A COM exception was detected containing the following description '%s'.

Cause: The connector called a COM API that threw an exception.

Action: Verify the connector prerequisite software is installed. Evaluate the the exception description and resolve the issue.

Level: 1

Type: ERROR

Impact: Other

BDSS-50210: An error occurred trying to build a Pim Xml message. %s

Cause: Microsoft API failure.

Action: Refer to Microsoft MSXML documentation for more information about the error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50211: Failed resolving MAPI named properties.

Cause: Microsoft API failure.

Action: See Microsoft documentation on 'IMsgStore::GetIDsFromNames'.

Level: 1

Type: ERROR

Impact: Data

BDSS-50213: The mailbox for the user on the Exchange server is not currently accessible. Synchronizing users msExchHomeServerName = %s. Synchronizing users legacyExchangeDN = %s.

Cause: The mailbox may have been deleted, be in the process of being moved, or the administrative user has insufficient priviledges to access the mailbox.

Action: The user may need to be reinitialized. Please see the product documentation for the procedure.

Level: 1

Type: ERROR

Impact: Data

BDSS-50215: Failed to obtain the Pim Domain metadata for the specified Hub domain. %s

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50216: There is no Pim Domain Id configured for the specified Hub domain.

Cause: The .XSD file containing the Pim Domain Metadata does not have a 'exch:PimDomainId' XML attribute.

Action: Add the 'exch:PimDomainId' XML attribute to the root element of the domain in the .XSD file. Restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50220: There are no Pim fields defined for Pim domain '%s'.

Cause: There are no Pim field definitions contained in the .XSD file for the Pim Domain.

Action: Add the Pim field definitions to the .XSD file for the Pim Domain and restart BDSS.

Level: 1

Type: NOTIFICATION

Impact: Configuration

BDSS-50221: Invalid parameter. LDAP binding path is invalid.

Cause: The string containing the LDAP path is empty.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Data

BDSS-50222: There is no Folder Class configured for the specified Hub domain.

Cause: The .XSD file containing the Pim Domain Metadata does not have a 'exch:FolderClass' XML attribute.

Action: Add the 'exch:FolderClass' XML attribute to the root element of the domain in the .XSD file. Restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50223: There is no property tag identifying the folder configured for the specified Hub domain.

Cause: The .XSD file containing the Pim Domain Metadata does not have a 'exch:IPMFolderEntryIdPropTag' XML attribute.

Action: Add the 'exch:IPMFolderEntryIdPropTag' XML attribute to the root element of the domain in the .XSD file. The attribute value should be a MAPI property tag of type PT_BINARY and available on the receive folder of the Exchange mailbox. Restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50224: There is no XML namespace configured for the specified Hub domain.

Cause: The .XSD file containing the Pim Domain Metadata does not have a 'targetNamespace' XML attribute.

Action: Add the 'targetNamespace' XML attribute to the 'schema' element of the domain .XSD file. Restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50225: Could not obtain the root element configured for the specified Hub domain.

Cause: The .XSD file containing the Pim Domain Metadata does not have a 'name' XML attribute for the root ('xsd:element') element.

Action: Add the 'name' XML attribute to the root 'xsd:element' element of the domain .XSD file. Restart BDSS.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50226: Failed to extract the Pim Domain. SyncSessionId = %s. Hub User Id = %s. Pim User Id = %s. Hub Domain = %s. Error = %s.

Cause: The connector failed to extract the specified domain.

Action: Examine the error message to resolve the underlying extraction error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50227: The '%s' Pim record operation failed for the Exchange record. SyncSessionId = %s. Hub User Id = %s. Pim User Id = %s. Hub Domain = %s. Error = %s.

Cause: The connector failed to create or update an Exchange record.

Action: Examine the error message to resolve the underlying create or update error.

Level: 1

Type: ERROR

Impact: Data

BDSS-50228: A socket error occurred when attempting to resolve the address when connecting. Address = %s. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'CSocketAddr::FindAddr'.

Level: 1

Type: ERROR

Impact: Configuration

BDSS-50229: A socket error occurred when attempting to create a socket. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSASocket'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50230: A socket error occurred when attempting to set or reset a socket event. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSASetEvent' and 'WSAResetEvent'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50231: A socket error occurred when attempting to associate an event object with a socket. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSAEventSelect'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50232: A socket error occurred when attempting to create a an event object. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSACreateEvent'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50233: A socket error occurred when attempting to connect to the remote computer. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSAConnect'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50234: A socket error occurred when attempting to receive data from the remote computer. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSARecv'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50235: A socket error occurred when attempting to send data to the remote computer. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSARecv'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50236: A error occurred when attempting to send data to the remote computer.

Cause: A non-socket related error occurred when trying to send data to the remote computer.

Action: Evaluate the error code to determine the cause and then follow the appropriate actions for that error.

Level: 1

Type: ERROR

Impact: Other

BDSS-50237: A socket error occurred when attempting to obtain the result of a overlapped result. Socket Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'WSAGetOverlappedResult'.

Level: 1

Type: ERROR

Impact: Network

BDSS-50238: A error occurred attempting to read data from the socket.

Cause: A non-socket related error occurred when trying to read data from the remote computer.

Action: Evaluate the error code to determine the cause and then follow the appropriate actions for that error.

Level: 1

Type: ERROR

Impact: Other

BDSS-50239: The socket is in a state that prevents further socket operations from occurring .

Cause: Attempting to send or receive data, but the socket is blocked.

Action: The error is meant for internal diagnostic and debugging by Oracle Engineering.? If you encounter it, please contact Oracle Technical Support.

Level: 1

Type: ERROR

Impact: Network

BDSS-50240: A error occurred attempting to connect to the remote computer.

Cause: An error occurred during SSL handshaking or verification of the server certificates.

Action: Verify the server certificate is valid. If client authentication is enabled, verify the client certificate is installed and valid.

Level: 1

Type: ERROR

Impact: Security

BDSS-50241: A security related error occurred when attempting to query the security package for buffer sizes. Security Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'QueryContextAttributes'.

Level: 1

Type: ERROR

Impact: Security

BDSS-50242: A security related error occurred when attempting to initialize a security context. Security Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'InitializeSecurityContext'.

Level: 1

Type: ERROR

Impact: Security

BDSS-50243: An error occurred when encrypting data.

Cause: Insufficient memory.

Action: Free resources on the connector machine or obtain additional memory.

Level: 1

Type: ERROR

Impact: Security

BDSS-50244: Could not build a certificate chain.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'CertGetCertificateChain'.

Level: 1

Type: ERROR

Impact: Security

BDSS-50245: Failed to verify the validity of the certificate chain.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'CertVerifyCertificateChainPolicy'.

Level: 1

Type: ERROR

Impact: Security

BDSS-50246: Could not open the 'MY' certificate store.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'CertOpenSystemStore'.

Level: 1

Type: ERROR

Impact: Security

BDSS-50247: Could not find the certificate containing a Subject 'CN' of '%s'.

Cause: The certificate is not installed in the 'MY' certificate store.

Action: Use Internet Explorer and install the certificate and then resynchronize the user.

Level: 1

Type: ERROR

Impact: Security

BDSS-50248: Could not create security credentials. Security Error = %s.

Cause: Microsoft API failure.

Action: Refer to Microsoft documentation on 'AcquireCredentialsHandle'.

Level: 1

Type: ERROR

Impact: Security