Overview

The SyrinxSP and Syrinx SP Configuration program can only be opened once on any given computer. If you try to open either of these programs while there is already an instance of that program running you will receive the error message "You can't open 'C:\ProgramData\Higher Concept\SyrinxSP v4\syrprgmn.adp' for exclusive use because another user has the database open or because you do not have the permissions to open exclusively":

The same holds true in a terminal services environment. If you try to set up Syrinx normally and try to access it from multiple client sessions, only the first client will be able to connect. Any other clients will receive the above error message when trying to log on as they are effectively trying to run the Syrinx program twice on the same computer.

To address this, you must create unique copies of the SyrinxSP and SyrinxSP Configuration program files for each user who will require them:

Server 2003:

C:\Program Files\Higher Concept\Syrinx SP v4\syrprgmn.adp

C:\Program Files\Higher Concept\Syrinx SP v4\syrprgcf.adp

Server 2008 and Server 2012:

C:\ProgramData\Higher Concept\SyrinxSP v4\syrprgmn.adp

C:\ProgramData\Higher Concept\SyrinxSP v4\syrprgcf.adp

Program Files

If there were three users who required access to just the main Syrinx program, you would create three copies of the syrpgrmn.adp and then rename them as follows while keeping the original program files for administrative use. These copy files should be renamed with the original filename as the prefix, followed by a unique suffix.  We recommend using the user’s Windows logon name that they will use when accessing the terminal server as the file suffix. For example, if the user Joe Bloggs will connect and authenticate to the terminal server as jbloggs, you can create a copy of the Syrinx program file named:

syrprgmnjbloggs.adp

The users will then need to be linked to the correct program file. There are two possible ways to do this depending upon what level of access the user has to the terminal server.

Setup

After creating copies of the Syrinx program file using the user’s Windows logon name, you simply have to modify the Syrinx shortcuts found in C:\Users\Public\Desktop (or C:\Documents and Settings\All Users\Desktop on Server 2003) so that they point to each user’s unique copy of the Syrinx program file. For example, the shortcut target path on Server 2008/2012 normally reads:

"C:\Program Files (x86)\Common Files\Sagekey Software\StartAccess3_2010.exe" -wait=0 /excl /runtime /profile "SyrinxSP v4" /wrkgrp "C:\ProgramData\Higher Concept\SyrinxSP v4\System.mdw" "C:\ProgramData\Higher Concept\SyrinxSP v4\syrprgmn.adp”.

This should be modified so that it points to the copies that were created following the example earlier, by using the windows system variable %USERNAME%:

"C:\Program Files (x86)\Common Files\Sagekey Software\StartAccess3_2010.exe" -wait=0 /excl /runtime /profile "SyrinxSP v4" /wrkgrp "C:\ProgramData\Higher Concept\SyrinxSP v4\System.mdw" "C:\ProgramData\Higher Concept\SyrinxSP v4\syrprgmn%USERNAME%.adp”.

When the user double clicks on the shortcut, Windows will replace the %USERNAME% system variable with the user’s logon name and thus open their unique copy of the Syrinx program file.

Terminal Services Load Balancing

If running load balanced terminal servers, an additional step will be required for licensing purposes.  On each server in the terminal services cluster, you will need to create a file named TSLicence.ini (this is just a text file named TSLicence.ini, it has no content) in the directory C:\ProgramData\Higher Concept\SyrinxSP v4 .  If that does not exist on each terminal server in the farm, then the same user connecting from different servers will take up two Syrinx licenses instead of one.

Upgrades

One final thing to be aware of is that when the system is upgraded to a newer version of the Syrinx program, the upgraded Syrinx program files “C:\ProgramData\Higher Concept\Syrinx SP v4\syrprgmn.adp” and “C:\ProgramData\Higher Concept\Syrinx SP v4\syrprgcf.adp”  (or “C:\Program Files\Higher Concept\Syrinx SP v4\syrprgmn.adp” and “C:\Program Files\Higher Concept\Syrinx SP v4\syrprgcf.adp” on Server 2003) will need to be recopied for each user to update their versions of the program files to the upgraded version. If you do not do this then copies of the program file will still be the old version of the Syrinx program file that was in place before you performed the upgrade and will not work with the upgraded version of the database.