Web Report Viewer Troubleshooting

This article applies to Presage Web and ITrack Chromium. The web Report Viewer will give a general error, error details are logged to the reportqueue table and can be viewed in the "History" (web) or "Print Queue" (desktop) tab of the Report Viewer screen.

Terms

• Crystal Server - the Node.JS application that uses Report Commander to generate the report PDF. Runs on Bunnahabhain
• Report Commander - command line application used to generate report PDFs by the Crystal Server (and Report Queue)
• Report Queue - python application that reads from reportqueue table to send emails and print to a printer. Report Queue is separate from Crystal Server, and the two systems do not interact.
• reportqueue - a table in the database that logs report runs.
• reportparameter - a table in the database that associates parameters to reports

Common Errors

Error Running Report

This means that Report Commander encountered an error running the report. If you get this error, check the reportqueue error for a more detailed error message. Listed below are some common ones.

"Missing parameter values" or "Double check the parameters..."

This means that Report Commander did not receive all required parameters for the report. Often times, the report will run fine on desktop, because the Crystal SDK can "fill in the gaps", while the web Report Viewer cannot, and needs a row in reportparameter for every parameter.

Solution

Since this is caused by missing rows in the reportparameter table, re-running the adder scripts will generally fix the issue.

If it doesn't, the adder script could be out of date or otherwise missing parameters.

Parameter not found in report: <parametername>

This means that a report was passed a parameter it doesn't expect.

Solution

Make sure the report is up to date

(I can't remember the error message)

Missing / invalid ODBC configuration. I think this presents as "could not connect to the database" or something to that effect.

Solution

Brian can make sure the ODBC connection is valid, and give Charles the name to check that the ODBC connection name in the Crystal Server config is correct.

Invalid Value for <parameter>

Report Commander received an invalid value for the specified parameter

Invalid Session

This error is caused by the Crystal Server failing to verify the session token it was passed.

Solution

Most likely, if logging out and back in doesn't fix it, this means that the Crystal Server configuration is either missing, or configured with a different database host URL than the API. Charles can check the logs to double check, as well as update the config file. Brian can then restart the Crystal Server service to load the updated configuration.

Invalid Report

The Crystal Server failed to find the report with the specified name/type.

The file or directory is corrupted and unreadable

Once or twice the cached .rpt file on Bunnahabhain was corrupted or something. We fixed it by reuploading the report to the customer's db and deleting the cached .rpt file from \\192.168.5.18\Node\crystal-reports-server\cache

Other Errors

Error: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. - Disable "Auto Reconnect" on ODBC. Presents as "Unkown Error" or "Internal Server Error" in the UI

Common Errors (Table Mode)

Common Errors

Error	Description	How to Fix
Invalid Session. Try logging out and logging back in.	This means that the report server was not able to verify your session. Either your session has expired, or the Crystal Server is not configured for that database. The most likely cause of this is, if logging out and back in doesn't fix it, is that the (generally Presage) customer hasn't been set up on the Crystal Server, or some configuration has changed.	If the config for that customer is missing, then add it matching the template. If it is present, make sure that the Crystal Server and Chromium/Presage API are configured with the same DB URL. Otherwise, check the ODBC connection and DB credentials. Charles can check the logs to double check the URLs are good, as well as update the config file. Brian can then restart the Crystal Server service to load the updated configuration.
Error running report. Double check the report parameters and try again.	This means that Report Commander did not receive the correct amount of parameters for the report. Often times, the report will run fine on desktop, because the Crystal SDK can "fill in the gaps" or ignore extra parameters, while the web Report Viewer cannot, and needs a row in reportparameter for every parameter. Check the Report Viewer > History tab for more error details	Generally, update the report and re-run adders, but See Below for more details, and check Report Viewer > History for more parameter and error details. If updating the report and adder doesn't fix it, it's possible that they are out of date and need fixed.
	"Invalid value for <parameter>" means Report Commander received an invalid value for the listed parameter. Usually this just means you forgot to fill a parameter out, but could be caused by by an outdated report / adders.	Make sure all parameters are filled out.
	"Parameter not found in report: <parameter>" means that a parameter was passed to the report that the report doesn't expect.	If caused by an out-of-date report (more common), update the report. If caused by out-of-date adders, re-run adders.
	"Missing parameter values" means that the report was not passed all expected parameters. Normally, this is because a parameter was added to the report, and the adders are out of date.	Re-run adders.
(I can't remember the error message)	Missing / invalid ODBC configuration. I think this presents as "could not connect to the database" or something to that effect.	Brian can make sure the ODBC connection is valid, and give Charles the name to check that the ODBC connection name in the Crystal Server config is correct.
Invalid Report	The Crystal Server failed to find the report with the specified name/type.	Make sure the report exists in the customer database with the given name and type. In Presage, there used to be a bug where running reports with a non-English language selected would fail with this error.
The file or directory is corrupted and unreadable	The Crystal Server failed to find the report with the specified name/type.	Once or twice the cached .rpt file on Bunnahabhain was corrupted or something. We fixed it by reuploading the report to the customer's db and deleting the cached .rpt file from \\192.168.5.18\Node\crystal-reports-server\cache