Murphy's law applies everywhere including to dbFront. Because of this, we built in fairly accessible logging and diagnostics.
Log Viewer and Logging
dbFront includes a builtin Log Viewer that can be accessed from the [Help] / [Log Viewer] menu. This Log Viewer will display two tables. The top table will contain the logs from the dbFrontUI. This log should normally be near empty since all logs are normally forwarded to the application server. The bottom table should contain all of the current log entries from the dbFrontService. You can use the filter on both tables to search for specific keywords.
If you log in as an admin user, the bottom of every screen will contain a small area that provides some basic information about how dbFront is running. Included is the name and location of the current log file and how many errors are currently written or waiting to be written.
Changing the Logging Location
Both the web.config for the dbFrontUI and the config file for the dbFrontService contain a key named LogPath which can be used to specify the folder where they will create their log files.
You should never set dbFrontUI and dbFrontService to log to the same location. This will cause conflicts.
The logging location should also not be to a network location because this will affect the application performance.
Log files for the dbFrontUI Web Application should generally be empty except for a single line indicating that all Log requests are normally sent to the dbFrontService. The only time that the dbFrontUI log file should contain any messages is if it can't contact the dbFrontService.
If the dbFrontUI can't talk to the dbFrontService then the specific issues might be:
- The dbFrontService is not running.
- The server name or port is incorrect. The log file for the Service and the UI should both indicate the port they are using.
- A firewall on the application server is blocking the incoming requests.
- A firewall on the Web server is blocking the outgoing request.
- Something about the network such as a firewall or router is preventing or blocking communication.
Once you have a specific log message or error message then you can look in the Knowledge Base or the Questions & Answers site. We ask that you search our Knowledge Base and check out the Questions & Answers site before sending a specific support request. Using these two resources first means that you will likely get your answer faster because your problem is unlikely to be unique to you.
If you still can't find the answer you need and you think that others might benefit from the question then please create a new question in the Questions & Answers site. We will do our best to answer the questions there.
If you prefer more individual help or you think you have found a bug then feel free to submit a support request, and we will be happy to respond.