Troubleshooting
This page includes information on using the Connexion logs to troubleshoot.
Event log
Troubleshooting in Connexion generally starts with the channel and/or device experiencing the problem. When the channel/device does not work properly, Connexion will display a message on the channel/device UI. Sometimes this message is sufficient allow resolution of the problem.
If it is not, the next step in troubleshooting is go to the Event Log. The Connexion event log lists all errors, warnings, and informational messages for the system. You can view messages for today, the last two days, the last 7 days, the last 30 days, or a custom date range. Click on the Event Log icon in the top toolbar (the rectangle with the lightning bolt) to view the log.
The Event Log button at the top of the Connexion UI shows events for all channels and devices. You can also see an event log for a specific channel by clicking the Event Log button in the channel title bar (at the far right-hand side of the UI).
Use the drop-down and text fields at the top of the table to filter the results. If you use a text field (such as ID), press ENTER to filter the log. In general, you will want to filter the table by the channel and/or device that is experiencing the problem.
In the Severity column, warnings are shaded in yellow, errors are shaded in red. To refresh the list, click Query.
Each type of message is assigned it's own ID. In the example above messages with the ID of 5083 are database connection failures to a specific database. All of those messages have the same ID. If a database connection error had been generated for a different database, it would have a different ID. You can exclude messages by ID from alert emails (see Overview > Event Log for additional information).
To see the full event text, select it in the table.
This message will often provide enough information to resolve the issue. For example, if the problem is a database failure, this fact will be captured in the Event Log and a system administrator can take steps to re-establish communication with the database server. Connexion must be running to be able to capture log system events. If it is not running, errors may be written to external text files.
If the information is not sufficient, you can check the external error logs generated by Connexion or contact Inner Harbor support.
Clearing the event log
As messages build up in the Event Log, you may want to clear them to make the list more readable.
You can:
- Remove today's events: removes all events for the current date as defined by the system clock;
- Remove all events: removes every message in the Event Log for all dates;
- Remove specific events: click to select an event and remove it. You can select multiple events by holding down SHIFT or CTRL when you click.
Each remove option will prompt you for confirmation. This action cannot be undone.
Log files
Connexion will also write to various log files. To view to files, go to the Event Log in Connexion. At the top of the log screen, click the Log folder button.
A Windows Explorer window will open showing the various log files available (text files). These files are intended for use by Inner Harbor for advanced troubleshooting.
Depending on the experience and knowledge of the individual user, these files may or may not be helpful and you may need to contact Inner Harbor for additional assistance.
When you create a Bug Report within Connexion, these text files are attached to the report and sent to Inner Harbor as supporting information.