Preparation:

• Read the upgrade instructions fully BEFORE attempting the upgrade. If you have any questions, please call Syrinx support on 0118 956 9577.  If you require Point of Rental to completely perform this upgrade on your behalf, please note that this is a chargeable service.
• Most current Syrinx modules and add-on components require .Net 4.8 or later.  The latest available version of the .Net Framework should be installed on any client/server machines prior to upgrading Syrinx.
• Syrinx version 4.34 and onwards are version 4 only upgrades, you will no longer be able to use Syrinx version 3 clients after the database has been upgraded.
• Note: After upgrading you will need to enter a version code before you will be able to access Syrinx again. This will be printed on the top right of the System Changes sheet attached to your upgrade email, otherwise call Syrinx support prior to upgrading to obtain this code.  You will not be able to connect to the upgraded database without applying this code.  
• Note: SQL Server versions older than 2008 R2 are no longer supported with Syrinx.  You can check which version of SQL you are using from within the Syrinx program by selecting Help / About Syrinx & selecting the ‘context’ tab in version 3 or by pressing the button in the upper left corner of Syrinx version 4 and selecting the ‘system’ tab of the ‘About Syrinx SP’ screen:
  
  If you have SQL Vsn: 8.xx.xxx, 9.xx.xxx or 10.xx.xxx, please call Syrinx support BEFORE attempting this upgrade.
• When performing the upgrade, you will need to know the specific names of your Syrinx database(s).  This information can be found on the ‘Context’ tab of the ‘About Syrinx SP’ screen which can be accessed via Help/About Syrinx in Syrinx version 3 or by pressing the button in the upper left corner of Syrinx version 4.  If you have more than one Syrinx database, you should connect to each database in order to verify this information.
• You will require the Syrinx ‘sa’ administrator user password.

• Shutdown all Syrinx sessions on all PC's and instruct users that they should not attempt to use Syrinx while the upgrade is in progress.  If all users do not log off the database properly, you will not be able to perform the upgrade.
• A database backup will be created automatically as part of the upgrade procedure, and will be saved as \SQLDataSp\Backup\SyrinxXX_Pre_Upgrade_4_x_0.bak
• Version 4 of Syrinx is not compatible with the 64bit version of Office 2010.  If the 64bit version of Office 2010 is installed on the server or any of the client PCs, you will not be able to install Syrinx version 4 on those systems until the 64bit version of Office 2010 is uninstalled and replaced with the 32bit version.
• If the Syrinx clients are hosted on a terminal server additional steps may be required.  Please contact Syrinx support (0118 956 9577) before proceeding.
• If you have additional products such as SyrinxWS, SyrinxRW, Syrinx Task Scheduler, Syrinx Mobile, Syrinx Driver/Workshop Apps these might also require upgrading before they will work with the upgraded version of the Syrinx database.  Please contact Syrinx support (0118 956 9577) before proceeding with the upgrade to verify that your add-on modules are compatible with the new version of Syrinx.

Upgrading to Syrinx v4.x - Stage 1:  Updating Database Server Software

• Login to the Server PC as the Windows administrator user (or a Windows user with administration privileges).
• Run the Server Upgrade Full.exe program on the computer that hosts the Syrinx database. A link to download the program should have been provided to you in the upgrade email.  Alternatively, the file can be downloaded from:

https://www.syrinxusers.co.uk/download/Syrinx%20Releases/Current/Server%20Upgrade%20Full.exe

username: download password: c0nc3pt

**Should you be unable to download the .exe version of the file due to restrictions in your web browser, a zipped version is available for download at the below link:

https://www.syrinxusers.co.uk/download/Syrinx%20Releases/Current/Server%20Upgrade%20Full.zip

username: download password: c0nc3pt

• Once the installer has been downloaded simply double click on it to run the program and upgrade the Syrinx software and installation files on the database server.  You simply have to press the ‘Upgrade’ button to initiate this process and then press ‘Install’ when prompted:

*This may take a few minutes as the installer unpacks and copies the new installation files to your server.

Upgrading to Syrinx v4.x - Stage 2: Connect to Syrinx Database

• Select the Syrinx v4 Database Administration program from the main Start menu by clicking on the windows ‘Start’ button and selecting All Programs / Syrinx SPv4 / Syrinx SP Database Administration or by selecting the Syrinx SP Database Administration option from the Syrinx SP v4 program group in the Windows 8/Server 2012 apps area of the start menu.  You must verify that you are opening version 4 of the Database Administration program as the version 3 Database Administration program cannot be used to perform this upgrade.
• Login as the Syrinx 'sa' user, and connect to your SyrinxXX database.  **You will have noted down your database name during the preparation steps at the beginning of this guide.  Your database will not be named SyrinxXX.
• If a small ‘Logon’ window appears, rather than the ‘Connect Database’ window as below, click on the ‘Cancel’ button. The ‘Connect Database’ window should now appear.

• You may see a message warning you that you are not connected to the master database. This can be safely ignored by pressing ‘OK’.
• The Database Administration program will then open and the available administration options will appear:

Upgrading to Syrinx v4.x - Stage 3: Upgrade Syrinx Database

• Select the 'Upgrade Database' option.

• Read the warning and press 'OK' to proceed.

• The ‘Upgrade Syrinx Database’ window will appear. The Folder field should automatically detect the correct path to the folder containing the upgrade files on your server (e.g. C:\SQLDataSP\Install\Upgrade435). 
• Press ‘OK‘ to continue after verifying that the ‘New Version’ field correctly lists the new upgrade version.

• If you are upgrading to Syrinx 4.36 or greater you may receive the below message during the upgrade process:

The driver schedule from Syrinx 4.36 onwards is now a stand-alone application where all trips are organised by transport vehicle.  The message is indicating that you have current driver trips that are not linked to a transport vehicle. If you say “Yes” to the above prompt the upgrade will proceed as normal but these trips will not be visible in the new driver schedule.  A patch can then be run against the upgraded database which will create dummy vehicle entries for the drivers which will then be linked to the trips so that they will then be visible in the driver schedule. Please contact Syrinx support (0118 956 9577) if you would like to run this patch.  If you say “No” to the message, the upgrade will be cancelled and you will be expected to go into Syrinx and link a transport vehicle to any open/current trips that are not linked to a transport vehicle before attempting to upgrade the database again

• If you are upgrading from a release prior to v3.28, you will get the following information message:

If you understand the message and wish to continue with the upgrade, click on ‘Yes, I would like to continue with the upgrade now’, and then press the Close button.

If you need to postpone the upgrade, until you have addressed the points made in the message, then leave ‘No, I will do the upgrade later’ selected and press the Close button. This will abort the upgrade, and you may close the Syrinx SP Database Administration program.  Users can still connect to and use the Syrinx database as long as they are not using the database server as a Syrinx client.

If you are unsure what this message means please call Syrinx support (0118 956 9577) before proceeding.

• If you have proceeded with the upgrade, you will see an upgrade confirmation screen. Press 'Yes' to upgrade your system.

• A backup will now be taken of your database. Please wait for this to complete.

• On completion of the backup, a confirmation box will appear. Press 'OK' to continue.

• The upgrade process will now commence.

Note: If you receive an error message during this stage, do not click on any further buttons. You should call Syrinx support (0118 956 9577) immediately, and you will be advised how to proceed from this point.

• If you have the add-on modules Syrinx Mobile or Syrinx Driver/Workshop Apps and have saved any photos to the Syrinx database with those devices and are currently running a database version earlier than 4.34, you will be presented with the below prompt when the initial upgrade stage is complete.  

After pressing OK, on the subsequent  ‘Browse for Folder’ screen, select the folder C:\SQLData\Docs\Mobile Images (this may be on another drive such as D:\, E:\, etc.) which will have been created automatically when running the Server Upgrade Full.exe installer:

The upgrade will now attempt to archive any photos held in the Syrinx database to the ‘Mobile Images’ directory.

• When the ‘Upgrade Finished’ message appears, press OK to continue.

• You may be asked to print off the system reports. Please ensure your printer has paper or print the error/event logs to a PDF printer, then press 'OK'.  If this box does not appear, then close the ‘Syrinx Database Administration’ program. The upgrade of the server has now completed. Continue to stage 5.

• You will see the report in print preview mode, press the ‘Print’ icon on the main window bar, and when completed, close the preview screen.  **It is not necessary to print the logs to complete the upgrade.  We simply use them to gain visibility of any unreported system issues in an effort to correct them in future versions.
  
• Press ‘Close’ on the Upgrade Syrinx Database window.
• A ‘Print completed?' confirmation box will appear, please answer ‘Yes’ or ‘No’.

• If you reply ‘Yes’ to the above, an error log is generated and saved onto your hard drive, press 'OK' to continue.

Or, if informed that the error log already exists, press ‘Yes’ to append the new details to the file.

• Finally, close the Syrinx Database Administration program if you have no other Syrinx databases to upgrade.
• The upgrade is now complete on the Server PC.

Upgrading to Syrinx v4.x - Stage 4:  Upgrade Any Other Syrinx Databases

• If you have any other companies, then click the ‘Connect Database’ icon on the ‘Syrinx Database Administration’ program, and connect to the other SyrinxXX databases. Then repeat Stage 3 to upgrade these company databases. Ensure that you enter the correct database name for each company database.
• If you have the add-on modules Syrinx Mobile or Syrinx Driver App linked to your additional company databases, you should create an additional mobile images folder in the \SQLDataSP\Docs directory for the specific database(s) before beginning the upgrade process so that the archived photos for each of your databases will be held in separate locations.

Upgrading to Syrinx v4.x – Stage 5: Apply Upgrade Code to Database

• Log into the Syrinx SP Configuration program as an administrator user such as ‘sa’ and select Registered PCs option on the “Administration” tab.
• On the Registered PCs screen press the ‘Version’ button and enter the upgrade code which you have obtained from Syrinx support.
• Press OK. You can now exit from the Syrinx SP Configuration program.
• If you do not perform this step, you will receive the following error message when attempting to connect to the upgraded database from the main Syrinx client:

Upgrading to Syrinx v4.x - Stage 6:  Upgrade Syrinx Client Computers

• If the Syrinx client computers are already running version 4 of Syrinx, they simply need to be upgraded to the latest version.  There is in most cases a shared folder hosted on your Syrinx database server named ‘SPInstall’.  This folder should contain a file named SpV4ReinstallProgram.exe which can be run to upgrade the client PCs.  So, for example if your server is named ‘server1’, you could attempt to browse to \\server1\SPInstall from the client PC and see if you can find the program SpV4ReinstallProgram.exe and then double click on it to run it.  Verify the version number displayed is the correct new version number before running the reinstall program on the client PC:

**If the Syrinx clients are hosted on a terminal server additional steps may be required which have been detailed in the “Upgrading Syrinx V4 Terminal Services Client” section at the end of this guide.  If unsure of how to proceed please contact Syrinx support (0118 956 9577).

• Alternatively, you can use the syrinx Version 4 client “Update” utility found in the Syrinx V4 program group on the Windows start menu on each Syrinx client PC:

When run, the tool will prompt for current database connection details to check the current database version number.  If it detects a difference between the database and client versions, it will prompt to download and install the Syrinx SP V4 client version that matches the current version of the database.

• If you are unable to find the SpV4ReinstallProgram.exe on your network, it can be downloaded from the below link and run on the Syrinx client computers:

https://www.syrinxusers.co.uk/Syrinx%20Releases/Current/SpV4ReinstallProgram.exe

username: download password: c0nc3pt

**Should you be unable to download the .exe version of the file due to restrictions in your web browser, a zipped version is available for download at the below link:

https://www.syrinxusers.co.uk/Syrinx%20Releases/Current/SpV4ReinstallProgram.zip

username: download password: c0nc3pt

• If Syrinx version 4 is not installed on the client computers, you will need to run the full client installer on those PCs.  The full installer, SpV4Setup.exe, can be found in the ‘SPInstall’ shared folder on the database server or can be downloaded from the following location:

https://www.syrinxusers.co.uk/Syrinx%20Releases/Current/SpV4Setup.exe

username: download password: c0nc3pt

**Should you be unable to download the .exe version of the file due to restrictions in your web browser, a zipped version is available for download at the below link:

https://www.syrinxusers.co.uk/Syrinx%20Releases/Current/SpV4Setup.zip

username: download password: c0nc3pt

When you run the SpV4Setup.exe file, you simply need to click “Install” to begin the installation process:

• As mentioned at the beginning of this guide, Version 4 of Syrinx is not compatible with the 64bit version of Office 2010.  If the 64bit version of Office 2010 is installed on any of the client PCs, you will not be able to install Syrinx version 4 on those systems until the 64 bit version of Office 2010 is uninstalled and replaced with the 32 bit version.

Upgrading to Syrinx v4.x - Stage 7: Database and Client Upgrade Complete

• If you do not have the add-on modules Syrinx Mobile or Syrinx Driver/Workshop Apps, the upgrade is now complete.  If you have either of these add-on modules, please proceed to the next section of the guide in order to complete the upgrade process.
• Please return any printed logs to HCS for review or email PDF copies to support@pointofrental.co.uk.

Upgrading to Syrinx v4.x - Stage 8: Syrinx Mobile\Driver App Additional Steps

• Additional Modules
  • If you have Syrinx Mobile, Driver, Operator, 365, Sales App, CWS or Transfer Tool installed, these will also require updating.
  • As with the above these can all be download from:
    • https://www.syrinxusers.co.uk/Syrinx%20Releases/Current/SpV4Setup.exe
    • Username: download 
    • Password: c0nc3pt
  • These should all install with no user interaction other than to reply in the affirmative to any questions asked (this ensures the existing settings are carried forwards).
  • Once the upgrade is complete for all Web based modules, you should either manually recycle all Application Pools in use by the web services or perform an IISReset.
• If you have the add-on modules Syrinx Mobile or Syrinx Driver/Workshop Apps and have saved any photos to the Syrinx database with those devices and were prompted to archive those photos during the upgrade process, you should note down the UNC path (network path) to the folder C:\SQLData\Docs\Mobile Images (this may be on another drive such as D:\, E:\, etc.) which will have been created automatically when running the Server Upgrade Full.exe installer.  The C:\SQLData\Docs  folder is normally shared as SPDocs.  So, for example if your server name is server1, the UNC path to the ‘Mobile Images’ folder would be \\server1\SPDocs\Mobile Images .  If the directory that contains the ‘Mobile Images’ folder has not been shared, you should set the appropriate share and security permissions on that directory so that the folder is accessible to all Syrinx users on the network.
• After Identifying the UNC path to the ‘Mobile Images’ folder, connect to the Syrinx SP V4 Configuration program and login as the ‘sa’ administrative user
• Click on the ‘Documents tab and then click on the ‘Root Folders’ menu option on the ‘Document Management’ section of that tab:

• Enter the UNC path to the ‘Mobile Images’ folder in to the ‘Mobile Images Folder’ root folder path and then click ‘Close’ to save your changes:

You can exit the Syrinx SP V4 Configuration program after making this change.

• The archiving of Mobile Images also requires an additional tool, The Syrinx Task Scheduler, to be installed on the database server.  This tool runs as a service and will periodically archive any photos that have been saved to the database by copying them to the ‘Mobile Images’ folder on a daily basis.  If this service is not run periodically, the database can grow in size until it is larger that the physical limit allowed by SQL Server 2008 Express R2 which is currently set at 10GB.  When this limit is reached, users will be prevented from writing new information to the database until the size of the database file is reduced.
• You can download the Syrinx Task Scheduler installer from the following location:

https://www.syrinxusers.co.uk/Task%20Scheduler/TaskSchedulerInstaller.msi

username: download password: c0nc3pt

**Should you be unable to download the .exe version of the file due to restrictions in your web browser, a zipped version is available for download at the below link:

https://www.syrinxusers.co.uk/Task%20Scheduler/TaskSchedulerInstaller.zip

username: download password: c0nc3pt

• Run the TaskSchedulerInstaller.msi file on the Syrinx database server to install the Syrinx Task Scheduler.  The installer will not prompt for any user input.  If you are already running an earlier version of the Syrinx Task Scheduler on the database server for the automation of customer reports, this process will upgrade the tool so that it is compatible with the latest version of the Syrinx database.
• After the installer has completed, there will be a new program named ‘Configure Task Scheduler’ available in Start / All Programs / Syrinx SPv4 or in the ‘Syrinx SP v4’ program group in the Windows 8/Server 2012 apps area of the start menu.  
• You should right click on this icon and select ‘Run as Administrator’ and enter valid connection details to the Syrinx database:

• If the Task Scheduler had previously been installed on the database server, the tool will open and display any scheduled tasks that are available to run: 

You should click on the edit button and verify that the below settings have been configured on the “Details” tab of the “Configuration Settings” screen.

• If the Task Scheduler was not previously installed on the database server, the tool will open and prompt for additional configuration settings.  The database connection settings should already be populated.  You will want to browse for the local path to the “Mobile Images” folder and set this value in the “Mobile Images” field (this value will normally be C:\SQLData\Docs\Mobile Images but may be on another drive such as D:\, E:\, etc.).  You will also need to enter in a path to a folder for saving the scheduler log files.  This can be any folder on the Syrinx databae server.  In the below example, a ‘SchedLogs’ folder was created in the C:\SQLDataSP\Docs directory and entered in to the ‘Log Files’ field: 

After specifying the path to the Log Files folder you can additionally specify smtp server/account details on the ‘Email’ tab of the ‘Configuration Settings’ screen:  

These details will be used for sending informational emails about the status of the Task Scheduler to a defined user.  This information is not required for the tool to run soleley for the purpose of archiving mobile images.  If you decide to enter this information and if you are only using the tool to archive mobile images, you do not need to specify a value for the ‘HTML Template File’ field as this is not required.

• Once the configuration information has been entered the Syrinx Task Scheduler service should be started by going to Control Panel \ Administrative Tools \ Services and right clicking on the ‘Syrinx Task Shceduler’ entry and selecting ‘Start’

• The Syrinx Task Scheduler should now be running and will archive photos stored in the database on a daily basis.
   

Upgrading Syrinx V4 Terminal Services Client (Only applicable if Syrinx V4 is already running on the Terminal Server):

Updating the Syrinx Shortcuts

The upgrade installers will replace the Syrinx V4 shortcuts.  If the Syrinx client has been upgraded on a terminal server the amended Syrinx shortcut which points to the user specific versions of the Syrinx program file will have been overwritten. You simply have to modify the Syrinx V4 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.  This is accomplished by using the windows system variable %USERNAME% and appending it to the name of the Syrinx program files in the ‘Target’ path of the shortcut’s properties.  For example, the shortcut target path on Server 2008 normally reads: 

"C:\Program Files (x86)\Common Files\Sagekey Software\StartAccess3_2010.exe" –wait=0 /excl  /runtime /profile "Syrinx SP"  /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 user specific copies that were created as part of the initial terminal server setup, by using the windows system variable %USERNAME%: 

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

This process should be performed on all of version 4 Syrinx icons that exist on the public desktop.

Updating the User Specific Files

The upgrade installers will not replace the user specific versions of the program files.  Therefore, after running the Syrinx client upgrade installers on the terminal server, you will need to browse to C:\ProgramData\Higher Concept\SyrinxSP v4\ (or C:\Program Files\Higher Concept\SyrinxSP v4\ on Server 2003) and make new user specific copies of the syrprgmn.adp and syrprgcf.adp files found in that directory.  A tool is available for download from our website that will copy these files automatically if you do not wish to do it manually.  The tool can be downloaded from the following location:

https://www.syrinxusers.co.uk/Support%20Tools/TS%20copy.zip

username: download

password: c0nc3pt

You simply need to run the TS copy.exe found in the zip file and then press the ‘Scan Directory’ button to search for any user specific copies of the Syrinx program files and then press the ‘copy’ button to update any of the files that it finds to the latest version.

Configuring Syrinx V4 Client for Terminal Services (Only applicable if the Syrinx V4 is client is new to the Terminal Server):

If version 4 of the Syrinx client has not previously been installed on the terminal server, it will require additional set up to work properly in this environment.  The Syrinx SP and Syrinx SP Configuration programs 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 following error message:

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.  

**If version 3 of the Syrinx client was previously installed on the terminal server you can check the version 3 program directory, C:\ProgramData\Higher Concept\SyrinxSP, to get a list of the current filenames in use and then make equivilant copies of the version 4 program files.

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.