Troubleshooting Connexion V14

Components

Connexion has several components, please take a minute to review the general architecture. This will help you understand the various troubleshooting tasks.

There are three components which need to be checked when Connexion isn't functioning:

  1. SQL Server - this is the database which stores both configuration information and messaging data for the Connexion service. If the database is not accessible to Connexion, it will not function.
  2. Connexion Services - this set of services host channels and devices. If these services are stopped, Connexion is not loaded.
  3. Management UI - the application used to configure and monitor the Connexion services.
General Checklist

The first step in troubleshooting is to determine if the Connexion service(s) are running. To do this, open Task Manager on the machine on which the Connexion service is installed, and check that the Connexion service is started. If it isn't, attempt to start it by right-clicking on the ConnexionV14 row and selecting 'Start'.

Note that on slower hardware, the service may take some time to fully start. It has a startup type  of 'delayed start' in order to give other processes time to start.

Service doesn't start, check logs:

If the service will not start, you must open the log files and view errors. The log files are located in \ProgramData\ConnexionV14\logs (there is a shortcut installed on the desktop). There are two logs to check:

  • Connexion.txt
  • ConnexionCriticalError.txt

You may be able to determine the issue from the content of the logs. Many issues can be solved by running the 'Install Wizard' (see below).

Run the Install Wizard:

If the service will not start, or it will start but you are unable to connect with the management UI, the service may not be correctly configured. In these cases, run the 'Install Wizard' and ensure your Connexion configuration is correct. The Install Wizard application is available from the start menu (under the Connexion folder) or can be launched from the system tray.

Typically you do not need to alter the configuration (which is remembered from the last time it was run) and can simply 'next' through the wizard. Please see the Install Wizard page for detailed instructions. It can be useful to make note of the service port since this is required by the management UI to successfully connect.

Service Runs but client won't connect

If the service shows as running, and the log files are not showing any errors, then you may have incorrect connection information in the Management UI. This typically shows as below:

If you see this error, you must double check the host and port matches that of the Connexion service. You can determine the service port by running the Install Wizard (see above) or by checking in the system tray icon context menu (RC2 and above) where it is displayed next to the 'Start Connexion Service' item. If the host or port do not match, you must click the Edit Connections button and enter the correct endpoint.

If you see the above screen but the displayed message is different, you may be running incompatible management UI and service versions, or there may be a port conflict where another application is using the port the Management UI is connecting to.