Pentana Audit: Logged error "Could not fetch business rules because query of type Behavior could not be executed"
The Pentana Audit main service applies various business rules to data as it is written to the database (e.g. adding child records, concatenating values in rows, maintaining counts).
In certain (and not yet understood) circumstances it is possible for the service to get stressed such that it functions partially for a time, but doesn't apply all business rules.
The problem may not immediately be noticed by users, but will likely be apparent from strange errors or missing values. The reliable fingerprint is this error in the file Service\PentanaTngService.log:
Could not fetch business rules because query of type Behavior could not be executed |
This error may follow these two other messages:
Exception of type: TngException[Fatal] - Message: Msg 701, Level 17, State 123, Line 1: There is insufficient system memory in resource pool 'internal'to run thisquery. |
Exception of type: IndexOutOfRangeException - Message: Cannot find table 0 |
Returning to normal operation
Restoring normal operation is simple - just restart the application pool - but it can leave records that aren't quite formed properly (e.g. contain blank calculated values).
Identifying and fixing resulting data issues
This article lists known resulting issues, with queries to identify problem data and guidance on fixing issues:
Pentana Audit: Sign Off state cannot be changed – Pentana Audit (ideagen.com)
Pentana Audit: Errors appear when changing Sign Off state – Pentana Audit (ideagen.com)
Pentana Audit: Record with Ref and Title has a blank Name – Pentana Audit (ideagen.com)