SYMPTOM
After upgrading to Strategy Secure Enterprise 10.4, error messages received do not contain the SQL when report or document executions run into SQL execution errors. This behavior is different when compared with Strategy versions prior to 10.4 where part of the report SQL is seen along with the error message.
The error message in Strategy version 10.4 is shorter and the SQL that ran into the error and other ODBC details are not displayed and only the error code is given as shown below:
Status: Execution failed Error: SQL Generation Complete Query execution encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [42000:0 on SQLHANDLE]. Error in Process method of Component: QueryEngineServer. Prject XXXX, Job 1234, Error Code = -2147212544 Starting time: HH:MM:SS
CAUSE
This is working as designed in Strategy Secure Enterprise 10.4. The change is driven by security concerns regarding the previous behavior where the DB user name, DB name etc., were displayed in the error message and visible to the end users.
ACTION
The complete error message containing the SQL is still available in DSSErrors.log and administrators can use that to troubleshoot errors.
The Strategy Internal Reference Number for the issue discussed in this technical note is DE37252 and DE42408.
