In-place upgrade TEKLYNX CENTRAL 4.0 to 4.5 – TEKLYNX CENTRAL Instructions
Summary
This Instruction Article explains how to perform and in-place upgrade to TEKLYNX CENTRAL from v4.0 to v4.5. This can be a very quick and efficient way to upgrade a TC system. Running an in-place upgrade does bring with it some inherent risks however. We recommend you call EBI for advice on if this is the best for your operations.
Preparation
Server:
- Windows Server 2008 SP2(x32, x64)
- Windows Server 2008 R2 (x64)
- Windows Server 2012/2012 R2
- .NET Framework 3.5 SP1 and 4.5.2 (installed automatically)
- ASP.NET 4.0
- LAS 2014.01 with UMSS 2014.01 (versions from TEKLYNX CENTRAL 4.5 package)
- SENTINEL 2014.01
- CODESOFT 2014.00
- IIS 7.0 or higher
- SQL Server 2008/2008R2/2012 or Oracle 11 (Oracle Client 32-bit is recommended on both 32/64 bit systems)
- Compatible with Virtual Machines: VMWare 7.1 and higher, Parallels 6.0 and higher.
Client:
- Windows Vista SP2 (x32/x64)
- Windows 7 SP1 (x32/x64)
- Windows 8/8.1 (x32/x64)
- Internet Explorer 10, 11, Firefox 35.0 or higher, Google Chrome 40.0 or higher
- Disable Windows Firewall, User Account Control and Antivirus – should be disabled before installation.
- Turn Off User Account Control – modern server systems like Windows Server 2012 should be also turned off in Local Group Policies.
- Windows Server 2012/Win 8: IIS should have the following features enabled: ASP.NET 4.5, и .NET 4.5 Extensibility.
- Windows 8.1/2012 R2: Microsoft .NET 3.5 installation requires changes of Local Computer policy according to screenshot below.
- SQL Server 2012: Sysadmin server role should have NT AUTHORITY\SYSTEM membership.
- SQL Server password should not have hash sign # in the password (Installshield bug). Also it’s highly recommended to not use other special characters. The best is alphanumeric and underscore.
- Windows 8.1/2012 R2: Microsoft .NET 3.5 installation requires changes of Local Computer policy according to screenshot below.
- In case of connectivity issues (LocalPrint cannot add driver, cannot print etc.) it’s recommended to try turning IPv6 off in network adapter settings.
- LocalPrint connectivity may also be affected by network traffic optimizers hardware or firewalls. These devices should be turned off or adjusted to let printing traffic pass
5. Follow TEKLYNX CENTRAL 4.5 PRINTING INTERFACE – IIS 7.0 CONFIGURATION GUIDE (attached) before installation.
6. Check that you have local administrator privileges – needed as the login when launching the installer
Instructions
- Reboot (insures uninstall from v4.0 is complete)
- Extract all the files from Central_4.5.zip – put into a folder
- Run the program TkcInstaller.exe – pulled from the Central 4.5\Software\TKCENTRALPACKAGE folder.
- Select English – or preferred language
- Enter Organization Name – must be done before you can proceed
- Check the Install TEKLYNX CENTRAL Online Printing Interface – Next
- Select the Website to Install the Printing Interface (Default Web Site) – Next
- Enter the Virtual Diretory (TKCENTRAL) – Next
- Enter Admin name (TCADMIN ) – Next
- Select database type (MS SQL) – Next
- Enter SQL authentication (e.g. [Server Name]\[SQL Instance Name] and password)
- Let Installer run (15 – 20 min.) – you will see the following tasks completed by the installer:
- Installing TEKLYNX Central
- Sharing License Folder
- Starting License Service
- Installing Users Management
- Installing Label Manager Server
- Installing Label Manager Client
- Installing Printing Manager
- Installing Printing Interface
- Configuring application
- Starting Sentinel Service
- Installation Completed Successfully
- Click Close
- Find the Application Pools settings in IIS – Start, Administrative Tools, Internet Information Services (IIS) Manager
- Verify that the Advanced Settings – should be set for the ASP.NET v4.0 Classic as pictured below.

- Right click on the TEKLYNX CENTRAL 4.5 Command Center shortcut and select Properties
- Select the Compatibility tab
- Select the “Run this program as an administrator” checkbox

Additional Comments
Known Limitations
- CODESOFT consumes 2 licenses: 1 Designer User and 1 Report User for LAS. Remotely installed CODESOFT via Command Center prompts login screen twice.
- Google Chrome will stop NPAPI plugins support in September 2015. LocalPrint plugin will become unavailable and will need the patch or workaround. Starting from version 42 it’s needed to turn on plugin support manually. Type chrome://flags/ in browser string and press “Enable NPAPI”.
- Upgrade is possible from previous version only (Oracle from TC 4.0, SQL Server from TC 4.0/4.2).
- Refresh browser cache after TC update. It’s needed to clear cache via Settings menu of the browser or press Ctrl + F5 on web page.
- Activation of expired software requires server restart.
- Google Chrome will stop NPAPI plugins support in September 2015. LocalPrint plugin will become unavailable and will need the patch or workaround.
Compatibility with other TEKLYNX Software
TEKLYNX CENTRAL v4.50.00 RC1 is compatible and fully tested to work with the following TEKLYNX software packages:
- LABEL ARCHIVE 2014.01 (TC 4.5 package version)
- UMSS/MSGS 2014.01 (TC 4.5 package version)
- CODESOFT 2014.00
- SENTINEL 2014.01
Author
Related Articles
- Loftware Redirect Print to PDF action using multiple printer seats
- License is failed – TEKLYNX CENTRAL Error Message
- Loftware Web Designer vs Desktop Designer
- Loftware Workday API Splitting Print Jobs
- Planning a BarTender Server Migration and Upgrade – BarTender Instructions Article
- Deciding on an In-Place Upgrade, Test Server, or Migration – BarTender Reference Article
