Error Handling

As soon as something goes wrong when processing a request, an error is generated and put into the response document. The status of the response will be set to "Error" or "Warning" depending on the severity of the error. In case of an error, processing will abort immediately, while in case of a warning processing continues.

An error has the following format:

<Error Id=”12345”>
  <Severity>Error/Warning</Severity>
  <Description>Short description</Description>
  <ExternalDescription>An external error text if available</ExternalDescription>
</Error>

Example response when trying to connect to a non-existent data source.

<ProLinga>
  <Data Version="1.0">
    <Command Name="OpenDataSource" Mode="Response" SessionId="PD-f8l5rowk7414eif077963ooqoicz" Status="Error">
      <Object DataSource="non_existent">
        <Error Id="70001">
          <Severity>Error</Severity>
          <Description>Can not open GDA connection.</Description>
          <ExternalDescription/>
        </Error>
      </Object>
    </Command>
  </Data>
</ProLinga>

The "External" element will contain any error text passed on from the O/S or 3rd party products.

The following errors are defined:

Table 1. Errors

Error Id	Severity	Description
70000	Ok	No Error
70001	Error	Can not open GDA connection
70002	Error	GDA connection does not exist
70003	Error	Error processing query
70004	Error	Data Model does not exist
70005	Error	Invalid value RowId
70006	Error	Other transaction already in progress
70007	Error	No transaction in progress
70008	Warning	UNDEFINED
70009	Warning	Invalid Session ID
70010	Error	UNDEFINED
70011	Error	Error parsing file
70012	Error	UNDEFINED
70013	Error	Invalid Build Option
70014	Warning	GDA connection already open