Errors Encountered At the Start of an Intelligent Advisor Interview

If an error message appears when you start an Intelligent Advisor interview, you can use the information below to troubleshoot the problem. These errors are logged in the Message log.

"An error occurred trying to process your request" errors

The following table contains the message log codes, the message which appears for each error and the likely cause.

Note: Every Message covered in the following table begins with the header text Error|Warning for policy model [Deployment Name]:[Deployment Version] via Connection: [Connection Name]. For ease of lookup, only the portion of the message which follows the header has been reproduced in the table.

Table 1. Description of web service connector errors encountered on interview start with the message 'An error occurred trying to process your request. For further assistance please contact support'
Message Log Code	Message	Likely cause
OPA-DATA-108	Read timed out	The Service took too long to respond. For example, it may have paused in debug mode for a long period of time.
OPA-DATA-108	No mapping exists for table '[Table Name]'	The Load response contained the mentioned `Table` name, but this does not match the `Table` name which the Intelligent Advisor interview service requested.
OPA-DATA-108	Cannot pop an item from an empty stack	The Load response contains an empty `Body` element. The Load response should at least include an empty `Tables` element within the `Body` element.
OPA-DATA-108	null	The `Root Table` (the `Table` mapped to the Global entity in the policy model) is returned with zero `Rows`. The global table must have one `Row`. OR The connection was renamed or deleted. Check that your web service connection still exists in Intelligent Advisor Hub. For more information, see Connect to a Specific External Application.
OPA-DATA-108	Can not specify multiple rows for table mapped to the global entity: [Root Table Name]	More than one `Row` was included in the Load response for the `Root Table` (the `Table` mapped to the Global entity in the policy model). The `Root Table` must have one and only one `Row`.
OPA-DATA-108	No parent link reference specified for row '[Row ID]' in table '[Table Name]'.	A `Table` (other than the `Root Table`) is including `Rows` which are not referenced by the `Rows` of any other `Table`. See also a similar error documented later in this table when a `Link` is returned which was not specified in the Load request.
OPA-DATA-108	Invalid target for link '[Link Name]' in row '[Parent Table Row ID]' of table '[Parent Table Name]'. The specified target row '[Child Row ID]' does not exist in table '[Child Table Name]'.	Parent `Link Reference` points to a non existent child `Row`.
OPA-DATA-108	Error parsing data: expected the start of an attribute value element.	A `Field` was returned with no value element.
OPA-DATA-108	Error parsing data: Unexpected element. Expected: change-point. Actual: [Received element type, e.g. ‘text-val’].	A `Field` which does not correspond to an attribute with temporal values in the policy model is given a second value. An attribute must have only one `value` element unless it is temporal. For more information, seeSupport Temporal Values .
OPA-DATA-108	No mapping for exists field '[Received Field Name]' in row [Row ID]' of table '[Table Name]'.	The Load response returned a `Field` which did not match the name of a `Field` in the Load request. `Field` name may be incorrect, or an extra `Field` was included.
OPA-DATA-108	No mapping exists for link '[Link Name]' in row '[Row ID]' of table '[Table Name]'.	A `Link` which was not included in the Load request is included in the Load response. `Link` name may be incorrect.
OPA-DATA-108	Invalid target for link '[Link Name]' in row '[Row ID]' of table '[Table Name]'. Expected: [Expected Table Name] Actual: [Received Table Name].	A `Link` was returned with the same name as a `Link` in the Load request, but with a different target `Table` name.
OPA-DATA-108	Table ‘[Table Name]’ already exists.	The Load response contained two `Tables` with the same name
OPA-DATA-108	Row '[Row ID]' already exists in table '[Table Name]'.	The Load response contained a `Table` which had two `Rows` with the same name.
OPA-DATA-108	Field with name '[Field Name]' already exists in row '[Row ID]' of table '[Table Name]'.	The Load response contained a `Row` which had two `Fields` with the same name.
OPA-DATA-108	Link with name '[Link Name]' already exists in row '[Row ID]' of table '[Table Name]'.	The Load response contained a `Row` which had two `Links` with the same name.
OPA-DATA-108	Invalid target for Link '[Link Name]' in row '[Row ID]' of table '[Table Name]'. The specified target row '[Row ID]' is already referenced by another link.	The Load response contained a `Link` with two `ref` elements using the same `id` value.
OPA-DATA-109	Failed to load data from data service Fault code: [Fault code] Fault String:[Title of fault] Message: [More details]	The connector responded with a Request Fault, and this message displays the information it contained. For more information, see Handle errors when loading or saving applications data.
OPA-DATA-110	401 Unauthorized	The URL for the connection configured in Intelligent Advisor Hub appears valid but has responded with a ‘401 Unauthorized’ error. The server may have changed the required authentication details. Check that your web service connection still exists in Intelligent Advisor Hub and that the authentication details are correct. For more information, see Connect to a Specific External Application. For Sales and Fusion service embedded interviews, this may occur when there is an error with the App Composer subtab control. Add the Intelligent Advisor interview as a mashup content subtab instead (which uses groovy script).
OPA-DATA-110	404 Not Found	The URL for the connection configured in Intelligent Advisor Hub has responded with a ‘404 Not Found’ error. The connection may have been taken down or the URL may have been changed incorrectly. Check that your web service connection still exists in Intelligent Advisor Hub and that the URL is correct. For more information, see Connect to a Specific External Application.
OPA-DATA-114	Warning for policy model [Policy Name] via Connection: [Connection Name] The Load response did not contain any tables.	The interview is mapped to load data at the start of the interview, however there was no data returned by the connector. This is not an error since Intelligent Advisor does not require any missing data, but it might indicate an issue with the connector - possibly the connector incorrectly processed the Load request or the connector was unable to find data for the given identifier.
OPA-DATA-115	Rows were missing from tables in the Load response	The response had table elements without any child row elements. If there are no references (ref elements) in any links to rows of this table (thus this table is empty of any rows), there is no reason to have it in the response.

"This value is of the wrong type" errors

The following table contains the message log codes, the message which appears for each error and the likely cause.

Table 2. Description of web service connector errors encountered on interview start with the message 'This value is of the wrong type'
Message Log Code	Message	Likely cause
OPA-VAL-003	Error setting value for attribute '[Attribute Generated ID]' in policy model [Deployment Name]:[Deployment Version] - Temporal value contains bad change point dates after [Date] java.lang.IllegalArgumentException: Temporal value contains bad change point dates after [Date] at [More stack trace]	A `Field` mapped to a policy model attribute with temporal values was given two or more `change-point` values which were not in chronological order by their date attribute values. Include `change-point` elements from earliest to latest dates. For information on how to implement `change-points`, see Support Temporal Values.
OPA-VAL-004	Error setting value for attribute '[Attribute Generated ID]' in policy model [Deployment Name]:[Deployment Version]- Cannot translate object of type class [Received Type] to a [Expected Type] java.lang.IllegalArgumentException: Cannot translate object of type class [Received Type Java Class] to a [Expected Type Java Class] at [More stack trace]	A `Field` was given a value different from the type specified in the Metadata, for example, a `text-val` rather than a `number-val`. Note that all types can alternatively have an `unknown-val` or `uncertain-val`.

Errors relating to references

The following table contains the message log codes, the message which appears for each error and the likely cause.

Table 3. Description of errors encountered on interview start with the message 'Unable to launch deployment' errors'.
Message Log Code	Message	Likely cause
IA-REF-001	Unable to launch [Deployment Name] due to broken decision service references	A Policy Modeling project is referencing a deployed decision service project incorrectly. Check the Deployments page for that deployment in the Hub. See also Deployment validation.