How to view error messages for the Get A Room Appconnector or Overview Screen Server – Biamp | Evoko Support

To get error messages when troubleshooting the Appconnector or Overview Screen server you can attempt to run the service from the command line on both Windows or Linux servers.

A common cause for issues with the Appconnector or Overview Screen is usually related to invalid details entered in the configuration file (which can be found in /etc/evoko/config.toml on Linux or C:\ProgramData\Evoko\config.toml on Windows). Attempting to run the service via the command line can give you some hints to what the issue may be or if it's is seemingly working fine.

The process vary slightly for Windows and Linux so please see the appropriate section for you below:

On Windows servers
On Linux servers

On Windows servers

Make sure the service you want to troubleshoot (i.e. Evoko Overview Screen or Evoko App Connector) is stopped under services.msc.
Next open the start menu and press Start in foreground for the appropriate application.
- For the Overview Screen (2.0.3 and above):
- For the Appconnector (2.0.2 and above):
In case of errors starting the service it should be output in the shell otherwise it should continue to run as long as the window stays open and the command isn't aborted (e.g. ctrl + c). Below is an example for wrong Evoko Home admin credentials being entered in the configuration.

On Linux servers

Make sure the service you want to troubleshoot is stopped.
- For the Overview Screen run:
```
sudo service evoko-overview-screen stop
```
- For the Appconnector run:
```
sudo service evoko-appconnector stop
```
Then attempt to start the service.
- For the Overview Screen run:
```
sudo evoko-overview start
```
- For the Appconnector run:
```
sudo appconnector start
```
In case of errors starting the service it should be output in the shell otherwise it should continue to run as long as the window stays open and the start command (i.e. sudo evoko-overview start or sudo appconnector start) is not aborted (e.g. ctrl + c). Below is an example for wrong Evoko Home admin credentials being entered in the configuration file.