Stonefield Query has built-in "diagnostics" that's very helpful for determining the cause of errors or other problems. When the user runs Stonefield Query, information about each stage of application startup, setup, database connection, report runs, and shutdown is logged to a file called AppLog.txt in the Logs subdirectory of the SQWeb folder. Also, errors are logged to a file named AppLog.glp in that same folder. If the information in these files doesn't help you track down the problem, contact Stonefield Technical Support; we can likely help you track it down. If you don't have access to the web server to retrieve the log file, use the Download Application Log function in the Tools menu.
Although the log file just contains text and could be examined using an application like Notepad, it's more convenient to read it using a Log4Net log file viewer. We recommend the free Loupe Desktop Viewer from Gibraltar Software; it can use to view both AppLog.txt and AppLog.glp files.
Studio also has diagnostic files. One is SQWeb\Logs\StudioLog.txt; this is the diagnostic file containing information about calls from Studio to the engine in Stonefield Query. Another is Data\Diagnostic.txt; this is the file for Studio itself.
You can create your own custom log files using a CustomLogger.config file. If that file is present in the Logs folder, it's used instead of Logger.config file for settings. The benefit of using such a file rather than modifying Logger.config is that it won't be overwritten when a new version of Stonefield Query is released. Stonefield Query uses the Log4Net library for diagnostic logging; see the Log4Net documentation for information on the settings to user in CustomLogger.config to customize the log file as desired.