Install TEKLYNX CENTRAL 4.5 on Windows Server 2008 R2 with .Net v4.7.1 – TEKLYNX CENTRAL Instructional Article


This Instruction Article explains how to install TEKLYNX CENTRAL (TC) version 4.5 on a modern Windows Server 2008 R2.  Some of the pre-defined images of the Server 2008 has .NET software already installed.  This can cause unexpected issues during installation.


Starting point:

  • Windows 2008 R2 Datacenter version
  • Microsoft .Net Framework 4.7.1 (pre-installed)


  1. Enable Windows Feature: Web Server IIS with the following options
    1. Static Content
    2. Default Document
    3. Directory Browsing
    4. HTTP Errors
    5. HTTP Redirection
    6. ASP.NET
    7. .NET Extensibility
    8. ISAPI Extensions
    9. ISAPI Filters
    10. HTTP Logging
    11. Logging Tools
    12. Request Monitor
    13. Tracing
    14. Customer Logging
    15. Windows Authentication
    16. URL Authorization
    17. Request Filtering
    18. Static Content Compression
    19. IIS Management Console
  2. Add Feature: .NET Framework 3.5.1 Features (.NET Framework 3.5.1 only)
  3. Install SQL 2008 Server
  4. In Programs and Features, repair the Microsoft .NET Framework 4.7.1 – This will place options in ISAPI restrictions and filters.
  5. In IIS Manager Console, select server on the left window
  6. Double-Click ISAPI and CGI Restrictions on the Right window pane
  7. Make sure that all the restrictions are set to Allowed
  9. TC will insist on installing .NET 4.5 – It will fail. Ignore the error message and proceed. Reboot as requested by the installation program.
  10. During the interviewing process, the installation program may present you with a warning message about “IIS is not configured properly. Please, make sure that ISAP restrictions are valid.”. Ignore the message and proceed with the software installation. See Additional Comments below.

Additional Comments

We have speculated that the false error message in step 10 above may be due to TC v4.5 installer not seeing an expected .NET version of 4.5 even though the .NET repair process successfully installs the missing files.


Was this article helpful?

Related Articles