This article will cover the installation of the Syrinx 365  Desktop which is the main client component of the Syrinx 365 system.

Topics included in this article

• Prerequisites
• Installation
• Troubleshooting

Prerequisites

• Syrinx AppInstaller - The latest version of this program should be downloaded on to the computer where the Syrinx 365 Desktop client will be installed.  The APP Installer’s download location is available in the AppInstaller Installation and Upgrade guide.
• Syrinx 365 API URL – The URL for the Syrinx 365 API will be required during the installation process (e.g. http://servername/Syrinx365Api/api/v2). 

Installation

To begin the Syrinx 365 Desktop installation, select “Syrinx 365” from the list of available programs in the Syrinx AppInstaller and press the “Install” button at the bottom of the screen:

After the AppInstaller finishes installing/configuring any required components such as the 64 bit Access 365 Runtime (if a copy of Office 2016 or later is not already installed), SAP Crystal Reports Runtime 13 and the Visual C++ 2015-2022 redistributable, the user will be presented with the following installation option:

Enter the appropriate URL for the Syrinx 365 API or simply replace “localhost” in the example URL with the appropriate server name and press the “Install” button to begin the installation.  No further input is required and the “Syrinx 365” installation option will move to the “Installed” tab of the AppInstaller once the installation is complete.

*Please note, after the installer has completed the URL for the Syrinx 365 API can also be manually set or updated in the “appSettings.json” file found in C:\ProgramData\Higher Concept\Syrinx\Desktop.

.

Troubleshooting

If the program fails to install, the Syrinx AppInstaller logs are found in the logged on user’s home directory, C:\Users\username\AppData\Local\Temp, and will be prefixed with “Syrinx_APP_Installer” and are suffixed with the time and date.  

Connection issues to the Syrinx database and or Syrinx 365 API can potentially be diagnosed by opening the “DevTools” menu option in the Syrinx 365 Desktop client and then viewing the calls made by the app to the API via the “Network” tab: