TimeXtender Prerequisites


This document covers the software requirements needed to run Discovery Hub. It does not cover hardware requirements or recommendations on server configuration. Refer to Microsoft’s recommendations for Microsoft SQL Server sizing when deciding on your hardware needs and configuration.

Software Prerequisites

Shown below are the minimum software requirements needed to run Discovery Hub. These are split into two areas: Application and Database. If Discovery Hub is going to be installed on a server that does not house the Microsoft SQL Server Installation, then those requirements must manually be installed. If Microsoft SQL Server and Discovery Hub reside on the same server then all but the .NET Framework will be installed during the Microsoft SQL Server installation.


Application Server

When data will be hosted in on-premise SQL Server

When installing Discovery Hub on a separate server from Microsoft SQL Server, the following components need to be installed:

  • .NET Framework 4.6.2 or higher
  • Core XML Services (MSXML) 6.0
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server System CLR Types
    • Install version that corresponds to the version of SQL Server, though not necessary for SQL 2017 editions and above.
  • Microsoft SQL Server Management Objects (SMO)
    • Install version that corresponds to the version of SQL Server, though not necessary for SQL 2017 editions and above.
  • Microsoft SQL Server Integration Services (SSIS)
    • Only necessary if SSIS will be utilized. See SSIS section for further details.
  • Microsoft Analysis Management Objects (AMO), ADOMD and AS_OLEDB

When data will be hosted in Azure SQL or Azure SQL Managed Instance

Using a Microsoft Azure SQL server requires the application server to be installed with the following components:

  • .NET Framework 4.6.2 or higher
  • SQL management studio. Here is a link to the newest edition Download and install. Because Azure SQL dbs are SQL 2017 and we, for versions newer than this, apply the necessary dlls during installation of Discovery Hub.
  • When using managed instance and Tabular it is necessary to use a Gateway as explained here.
  • You will also need the Client libraries for connecting to Azure Analysis Services

When using developer client workstations

The application server requirements also apply to a scenario where Discovery Hub is not installed on a dedicated application server but has multiple installations on each developer’s workstation as a client application. In this case, any machine that has Discovery Hub on it without SQL Server itself is considered an application server and will need to comply with the software prerequisites for the application server.

Database Server

On the Microsoft SQL server, the above requirements (except the .NET Framework), are installed during the SQL installation. In addition to those, the following minimum requirements must be met:

  • Microsoft SQL Server 2008/2008 R2/2012/2014/2016/2017/2019. Minimum edition is Standard with the following components installed:
    • DB Engine
    • Integration Services (SSIS)
      • Only necessary if SSIS will be utilized.
    • Analysis Services (SSAS)
      • Only necessary when using OLAP Cubes or Tabular Models.
  • Microsoft Azure SQL Server (DB Engine only)

Advanced Feature Requirements

Most of Discovery Hub functionality can be accomplished using the Standard version of Microsoft SQL Server; however, there are some features that require the Enterprise addition.

The following Discovery Hub features require Microsoft SQL Server Enterprise Edition or SQL Server 2016 SP1 or later:

  • Compression of tables and indexes
  • Partitioning on tables
  • Non-Physical Cube Perspectives (Standard Perspectives on SSAS)
  • Incremental Load on Cubes
  • OLAP translations where you translate dimension member display values

Verify Requirements

This section will help you make sure you have met the necessary requirements.

.NET Verification

The .NET version can be verified by:

  1. Click on the Windows Start button.
  2. Type “run” (without the quotes), and click enter.
  3. Type “%windir%\Microsoft.NET\framework” (without the quotes), and click enter.

Microsoft SQL Components Verification

Microsoft SQL Server Native Client, Microsoft SQL Server System CLR Types, Microsoft SQL Server Management Objects and Microsoft SQL Server Integration Services (SSIS) can all be found by checking the list of installed programs.

In Windows, navigate to the Control Panel and then Programs and Features.

The image below shows the necessary requirements listed above have been met. It also shows that Microsoft SQL Server 2016 (64-bit), is installed. This is due to having SQL Server Installation Services (SSIS), a component of the Microsoft SQL Server installation, installed. 

SSIS Verification

To verify the installation of SSIS, click on the Windows Start button, type “services.msc” (without the quotes), and hit enter.

The image below verifies the installation of SSIS.

Remote SSIS Execution

When using SSIS for data transfer, Remote SSIS Execution is recommended when installing Discovery Hub on a separate server. You still need to install SSIS on both Database and Application server. Additionally, you install the Discovery Hub Remote SSIS Execution package on the Database server. This allows SSIS service running on the Database server instead of the Application server, potentially reducing network delay between separate servers in data transfer.

MSXML Version Verification

To verify the version of MSXML on the server, navigate to C:\Windows\System32 folder. In the search field, type in “MSXML*” (without the quotes). The results should look similar to the image below.

TimeXtender Activation

To use Discovery Hub, you will need a valid activation code, which is provided by your TimeXtender partner. If you don't have a TimeXtender partner, visit our partner directory to find a partner in your region or contact us.

The easiest way to activate Discovery Hub is over the Internet. If your machine does not have an active internet connection, contact support to obtain an offline activation file.


Shown below are a few of the most common errors found when using Discovery Hub without all of the prerequisites met. If you encounter a problem and it’s not listed below, please contact support or visit the knowledge base.

Problem 1 - Error writing to file.

  • Issue: Microsoft .NET 4.6.2 or higher is not installed.
  • Resolution: Install Microsoft .NET 4.6.2 or higher or, using the Discovery Hub installer, run the setup.exe (not the msi), and DWA will download and install it automatically. See the image below for reference.

Problem 2 - Error creating DTS package for…

  • Issue: SSIS is either not installed or running.
  • Resolution: Verify SSIS is installed and running. See SSIS Verification above to check.
    • If SSIS is missing, it can be installed using the Microsoft SQL Server installation.
    • If you encounter the following image then SSIS is not running. Click on Start in the upper left to start the service.

Alternatively, right-click SQL Server Integration Services and choose Start Service.

Problem 3 - Error could not load file or assembly

  • Issue: SQL Shared Management Objects or Analysis Management Objects is not installed.
  • Resolution: Install the appropriate version of Microsoft’s SQL SMO that corresponds with the version of Microsoft SQL Server, or the AMO version. Follow the link below for more information and links to download. Link to SMO and AMO

Problem 4 - Discovery Hub will not launch after installation

  • Issue: Missing the appropriate .NET Framework.
  • Resolution: Reinstall Discovery Hub using the setup file or download Microsoft’s .NET Framework 4.6.2 or higher.

Problem 5 - An Error Occurred while loading a list of projects from the database

  • Issue: The user does not have appropriate permissions to access the project repository.
  • Resolution: Verify the user has at least read access to the project repository.

Problem 6 – There was no endpoint listening at…

  • Issue: This occurs during activation of a license or trial when there is no internet connection on the machine.


  • Resolution 1: Verify the machine has an active internet connection. If needed, email to obtain an offline activation file.
  • Resolution 2: If direct internet access is not allowed, perhaps access by proxy is. Try configuring the proxy and reactivate the license.
Was this article helpful?
0 out of 0 found this helpful


Article is closed for comments.