Strategy for Upgrading TEKLYNX CENTRAL 4.x to 5.0 – Reference

Target Audience: Advanced User, IT Manager
Article #: 9590


This article provides strategy for upgrading TEKLYNX Central from Version 4.5 or later to Version 5.0.

The process of upgrading complex software, such as TEKLYNX CENTRAL, always provokes some sense of fear and anxiety. It can feel like a step into the unknown to go from a program which you are comfortable and familiar with – especially one that works well on your system – and change to a version that you have no experience with. While there are a number of things that could go wrong, most are avoidable if you make a plan.

Version 5.0 of TEKLYNX CENTRAL is a significant update from the previous version. Many new features have been added, so do not assume that everything will work the way it has. Existing features may have been fixed, altered or relocated. For that reason, we strongly recommend that testing the software on a designated test server be part of your plan before proceeding with the actual install on the production server.



  1. Should I use the existing server to perform the upgrade? Most organizations will avoid this method as it can disrupt the production system. Additionally, if the upgrade fails, important data may be hard to recover.
  2. Should I use a new server with newer OS? This will depend on the direction of the IT department for the organization. Best practice is to use the latest version of the OS supported by the application. This will reduce the chance of having to perform the software migration/upgrade process again later due to the OS no longer being supported by Microsoft.
  3. Should I use a newer version of SQL? Again, this answer will largely be driven by IT. Cost and organizational support will dictate which version of SQL to use. Although SQL Express is free, many organizations refuse to use it due to internal IT policy.
  4. What will happen to my existing data? Generally speaking, there should be no data loss. The procedure described below will ensure that you are never working without a safety net. We NEVER run upgrades on the only copy of the database.


You will need to have the following ready before beginning:

  • Server for TEKLYNX CENTRAL – we recommend Windows 2016
  • Server for the Database – if it will be running on a separate server
  • The version of SQL you will use – We recommend SQL 2014 or later
  • A backup of the TEKLYNX CENTRAL SQL production databases – This includes UMSS, MSGS, LABELARCHIVE and LABELNET.


The upgrade process is broken down into three parts: Testing, Installation and Switching Over. The steps will be shown in Procedure, below:

PART 1: Setting up a test system for both TEKLYNX CENTRAL and SQL

  1. Installing TEKLYNX CENTRAL 5.0 on a test system using the procedure below .
  2. Testing the features of TEKLYNX CENTRAL to make sure that they perform to your expectation
  3. Exploring the new features of TEKLYNX CENTRAL to determine if they will be beneficial to your organization as well as how to use them.

IMPORTANT: DO NOT USE the production SQL server to run your tests!

PART 2: Installation

  1. Installing TEKLYNX CENTRAL and the SQL database onto a new server (if desired) using the procedures below.
  2. Configuring the new production server with the features and options tested in Part 1.
  3. Testing all features until you are satisfied with the results.

PART 3: Switching Over

  1. Halting the production system
  2. Backing up production databases
  3. Upgrading the databases the procedure in Upgrading Databases, below.
  4. Testing the functionality of the system
  5. Resuming production



  1. Install TEKLYNX CENTRAL onto the new server. Follow the instructions on the screen until you arrive at the database section. For TEKLYNX CENTRAL 5.0, Teklynx has separated the databas setup and configuration. This allows for more flexibility, giving the user control over database names and locations. We will be using this feature to our advantage.
  1. Click Next>
  1. Your screen may looks slightly different – the Delete Database and Save database options may be grayed out.  Select Create/Update database and click Next
  1. Select SQL Server and click Next.
  1. This is where you’d define the name and location of the database (UMSS). Enter appropriate Server name, select the Authentication method, User name and Password.  As for Database name, for UMSS, the default is UMSS.  However, we recommend that you change it to something different – ie UMSS-MT (UMSS empty).  This will allow you to make distinction between empty database and the one from production system.  Make sure you check the Save connection options box.  Click Next.
  1. You will then be prompted for the same information for MSGS, LABEL ARCHIVE and Printing Interface (LABELNET).  Use similar naming convention as UMSS.
  2. Click NEXT after filling out the fields.
  3. Select the sites you need (select All) and click Next
  4. On the next screen click Next. The database setup and configuration will start.
  1. Follow the steps on the screen until TEKLYNX CENTRAL’s installation is completed.
  2. Apply any TEKLYNX CENTRAL updates or patches as necessary. Follow instruction(s) accompanying the patches.

At this point, you have completed installing the base TEKLYNX CENTRAL 5.0.

Our next step is to bring the 4.x database up to 5.0 version.  While this could have been done this during Step 3 of the installation process we felt this way was the preferred method to allow you to focus on installing and upgrading the two parts individually.


  1. Restore the backup of the production database to the SQL server.
  2. From the TEKLYNX CENTRAL installation media, go to folder  Software\TKCENTRALPACKAGE\ConfigTool. Right-click on InstallDB.exe and select Run as Administrator.
    This will start the database configuration program seen in Step 2 of the TEKLYNX CENTRAL installation procedure, above. 
  3. Follow the same instructions above except when it comes to the database names.  
  • UMSS for UMSS
  • MSGS for MSGS
  • LABELNET for Printing Interface

NOTE: all of the database names are defaults.


Was this article helpful?

Related Articles