Other error messages in the server log file
The server.log file contains error messages that relate to Form Builder, Report Manager, user error, HTTP protocols, and currency conversion.
DataConnect errors
For possible errors, see the Common Issues section in the DataConnect chapter of Application Building for the IBM TRIRIGA Application Platform: Data Management.
WFA:3340769 - 2289501
- Log Type: Exception Header
(WFA:3340769 - 2289501 Associate:26451634)- Issue
- This information can be included in any error.
- Suggested action
- Decode the error snippet.
- Example
(WFA:3340769 - 2289501 Associate:26451634)To locate the information in the database, use the following SQL:
select * from user_credentials where user_id=3340769; select * from ibs_spec where spec_id=2289501; select * from wf_event where event_id=26451634;If no rows are returned, try the following SQL:
select * from wf_event_history where event_id=26451634;
Invalid Object ID for dispatch
- Log Type: Exception Header
ERROR Invalid Object Id specified for dispatch. Object Id was null.- Resolution area
- User training
- Issue
- User clicked inside a window before the Java™ code finished loading.
- Suggested action
- Users need to wait for the Java to load before they click inside a window.
- Example
ERROR [com.tririga.web.process.ProcessRouter] Invalid Object Id specified for dispatch. Object Id was null.
HTTP protocol error
- Log Type: Exception Header
INFO - [com.tririga.web.filter.AuthenticationFilter]- Resolution area
- HTTP protocol
- Issue
- A user process caused an issue with IBM TRIRIGA HTTP security. For example, the user might navigate to a link when not logged in or when a session is expired. Causes might include timeout or attempting to log in more than once with the same user account.
- Suggested action
- Log back in to the IBM TRIRIGA application and go through the steps that were followed before this error.
- Example
- A request was made for templateScriptsCached.jsp through some process but the session expired and the page is no longer accessible.
Cannot parse parameter in formula
- Log Type: Exception Header
WARN Could not parse parameter in formula:- Resolution area
- Report Manager
- Issue
- An extended formula is trying to use a query to resolve a parameter, but the query or field in the query cannot be found.
- Suggested action
- Add the query or the field to the query.
- Example
- An extended formula is attempting to use the query
triInvoiceLineItem - Advanced Formula - triPaid - Associated to Current Record, in the triNewInvTotalNU field.
GUI field has a different field type than business object
- Log Type: Exception Header
Gui field has a different field type than backing bo. Using field type of BO.- Resolution area
- Form Builder
- Issue
- A form has a field that no longer exists.
- Suggested action
- Identify the forms for the business object that uses the listed field. Revise the form. In Form Builder, remove the field from the tree view of the form layout. Add the field back to the form. Publish the form.
- Example
- The Note field, on the triBSIFailureImpactA business object, is identified as a text field in a form but another field type in the Data Modeler.
Backing business object field does not exist
- Log Type: Exception Header
WARN Not adding field, '$$$', to GUI Section because backing Business Object field does not exist:- Resolution area
- Form Builder
- Issue
- A form has a field that no longer exists.
- Suggested action
- Identify the form and field. Revise the form. In Form Builder, remove the field from the tree view of the form layout. Add the field back to the form. Publish the form.
- Example
- The Active Start Date field, on the Key GUI, General tab, KeySpecification section, is invalid.
Invalid query filter
- Log Type: Exception Header
WARN Not using invalid query filter:- Resolution area
- Report Manager
- Issue
- A query has a filter for a field that does not exist.
- Suggested action
- Identify the query and filter. In Report Manager, remove the filter. Save the query.
- Example
- The filter for the triPaidDA field, on
the
triPaymentLineItem - Display - Received Accounts Receivable records associated as Has Paymentquery, in the triCostItem module, is invalid.
triTesting column does not exist
- Log Type: Exception Header
WARN Adding DB column, triTesting, since it does not exist and the BO expects it to be there.- Issue
- This warning is logged during a publish.
- Suggested action
- The message in the log entry indicates what needs to be enabled in order for that entry to exist.
- Example
- The example shows logging that occurs during a publish. To see the DEBUG events, enable the Business Object Publish option on the Platform Logging object in Administrator Console, on the server where the BO Publish Agent is running.