How to Install Discovery Hub or Upgrade to a Newer Version


This document will outline the steps necessary to install Discovery Hub or upgrade your production environment to use a new version of Discovery Hub. It will cover the download and installation of the software, upgrading the project repository (if upgrading), and ensuring that the Discovery Hub Scheduler service for the new version is up and running.

Please see the separate Discovery Hub Prerequisites article for information on the settings and software you need to have on the machine to install Discovery Hub.

Step by Step

Download and Installation

If you are installing Discovery Hub for the first time, i.e. not upgrading from a earlier version, you can ignore steps 12-15.

  1. Download the latest version of Discovery Hub in the edition and bit-version you need.
  2. When the file has been downloaded, unzip the installation package and run Setup.exe.


    If all prerequisites has been met, you should be able to install using the .msi file in the downloaded archive. Using setup.exe is recommended, however, since it checks for the required version of the .NET Framework and installs it if necessary.
  3. On the welcome page, click Next.


  4. On the End-User License Agreement page, review the license agreement and select I accept the terms in the License Agreement if you do. Click Next.


  5. On the Choose Setup Type page, select Typical and click Next.


  6. On the Ready to Install page, click Install. Windows might ask you to confirm that you wish to make changes to the computer. If so, click Install the software. Wait for the installation to finish.


  7. Once the installation is completed, click Finish to close the setup program.


  8. Start Discovery Hub. There will be an icon on the desktop for Discovery Hub that you can doubleclick to launch the program. The first time Discovery Hub is opened it will prompt you for an activation code. Select Activate over the Internet


  9. If your server is located behind a proxy server you can add the credentials here, by activating the Use this proxy server.


  10. On the following screen paste or type in your organization's activation code and click Next. This will synchronize with our licensing server and enable all your licensed features of Discovery Hub.


  11. You will then be presented with this screen. Notifying you that the product have been activated successfully.


  12. After activating the software, you will receive a warning  that the project repository settings are invalid.


    Click OK to dismiss the warning, and on the next screen type in the server name that your current project repository resides on. Click the drop down arrow for the Database and select your current project repository. Click OK.


  13. If you are upgrading, Discovery Hub will recognize the old repository and prompt that it needs to be upgraded to be compatible with the new version of Discovery Hub. It will also show the location where the backup of the repository will be located. Click the Upgrade button.


    While it is running a menu prompt will show you the current progress.


  14. You will then be prompted for the upgrade method. Select Web service.


    The upgrade scripts will be downloaded and processed. Discovery Hub has now been installed and the project repository has been upgraded to be compatible with the new version of the software.
  15. Deploy and execute your project(s) using the new version to have the upgrade reflected in the actual project code. Validate the results before letting your end-users perform reporting on the upgraded projects data warehouse and/or cubes.

Setting Up the Scheduler Service

During the installation of Discovery Hub Server, a service is installed on the local machine that controls the execution packages. These execution packages handle the regular updates made to the data warehouse and the cubes. 

The service needs to be run by a user with sufficient user rights and configured to use the correct repository database. This can either be the same account that you use to develop your projects or a different service account (recommended). How to point that user to the correct repository will be described below.

Follow the steps below to set up a new user account for use with the scheduler service. If you have upgraded to a new version you will still need to start up the scheduler in this new version. You can skip the first bit and go the step where we start the service, if you are using the account you use for development or if you are upgrading and already have a user account set up with the correct repository settings.

  1. Make sure that the account has sufficient permissions.
    • On Analysis Services, Administrator rights (if you use OLAP Cubes).
    • On the msdb database, membership of the db_ssisadmin role.
    • On repository, staging and data warehouse databases, membership of the db_owner role.
  2. Log in with the user account that will be used to run the scheduler service. Go to the installation folder normally on the C: drive and find timextender.exe press Shift+RightClick and choose Run as different user.


  3. Add the user account you want to run the scheduler service as.


  4. You will get the same warning you got the last time you started the program. Point to the same repository as before.


  5. Open the Windows service Setup.


  6. Set the start mode to run as Automatic Delayed.


  7. Press the Change User Name and Password button and add the credentials.


  8. Press Start Service.


  9. If it worked you will be presented with this screen.


  10. If you receive a message that the service started and then stopped the most common cause is that the Discovery Hub configuration files have not been created for the service account that was specified to start the service. Doing it this way should make it not happen.

With the user account configured, there is only one thing missing. Setting up what should be done if the service fails.

  1. Press the Windows button to bring up the start menu/start screen, type "services.msc" and press enter. This brings up a overview of Windows Services.


  2. Right click the Discovery Hub Server Scheduler service and select "Properties".
  3. On the Recovery tab the First failure and subsequent failures should be set to "Restart the service".


If you have started the service, but for some reason the execution gets errors regarding the wrong repository. It could be that the old version of the service is still running. Press the Options menu and choose filters All versions.

You can now see all the installed versions of Discovery Hub scheduler and server. Sort it by status. Only one scheduler service should be running.


To solve it simply stop it.

If you are upgrading from an earlier version, you can uninstall the old version of Discovery Hub once all of the previous steps have been successfully completed.

Was this article helpful?
3 out of 3 found this helpful
Have more questions? Submit a request


  • 0

    Er det korrekt at opsætning af Multiple Environment skal foretages igen efter opgradering til TX DWA ??

  • 0
    Thomas Lørup Duun

    Allow me to translate your question to English.

    Q: Is it correct that you need to reconfigure multiple environments after upgrading to TX DWA?

    A: You need to configure the new TX DWA Server Service to use the same credentials as the old server service did. Then you have to login as that user, start TX DWA, point it to that environments repository database and upgrade the repository. Then start the service, and your multiple environments are back in business.


  • 0
    Chris Shelley

    Do you need to update the SSIS folder options post Upgrade? Currrently I get errors where the SSIS folerd cannot eb found as it has changed names between installs:

    Was: TX2014Server\DevTest

    Now: TX DWA Server\DevTest

  • 0
    Thomas Lørup Duun

    Hi Chris,

    You can change the SSIS Root folder on the Edit Project screen if you need to. When you deploy the project the new folders should be created automatically though - so I wonder if you did not deploy but just executed after the upgrade?

  • 0
    Chris Shelley

    Hi Thomas,

    You are correct I have not redeployed as I was not aware that it was required post upgrade. Do i need to redeploy all elements in the repository? If so that should I feel be in the upgrade instructions.

    Also if I just redeploy will I not end up with 2 SSIS folders and duplicated packages.





  • 0
    Thomas Lørup Duun

    Hi Chris,

    It is the deployment that translates your project into SQL Server code, so if you do not deploy, then the upgrade will not be reflected in the code being executed. And you are correct in your assumption about ending up with duplicate packages. Feel free to delete the old ones, once the upgrade is completed successfully.

    We will add the important deployment step to the instructions. Thanks for pointing our attention to it!

  • 0
    Jörgen Peerik | Victa

    Hi Thomas,

    Thanks for the explanation.

    What about servers which don't have an internet connection. Then the server is not able to download the latest upgrade scripts and I have to click on the button 'Local Files' instead of 'Web Service'. 

    How can I make sure the upgrade is done by using the latest scripts?



    Jörgen Peerik

  • 0
    Thomas Lørup Duun

    Hi Jörgen,

    If the server is not connected to the internet, then you should use local files. If there is an issue with the files distributed with the release, then we have announced it on the support site. Actually version 16.4.2 is missing an upgrade file, which we have announced and released 16.4.3 in order to fix it.

    Kind regards,


  • 0
    Nicolas Cosma

    Hi Thomas,

    I have ugraded the application, but at the moment of choosing "select upgrade methode" by "web service, I had an error, with the choice local file, No problem

    Is it ok ?

  • 0
    Nicolas Cosma

    Thanks :)

  • 0
    Thomas Lørup Duun

    Local files in the latest version (as with most versions) is OK!


  • 0
    Martin OLoughlin

    I am currently looking at upgrading from TX2014 to the current release. As part of the testing i have installed TX2017 on my local machine, which is working fine and has allowed me to build a functional model, i have exported a model from the live system with the idea of importing to a local environment to get a feel for the process and identify any pitfalls. 

    However i am getting an error message "the project xml for generated in TX DWA server 14.2.6 The project can not be imported." 

    Is there something that prevents an upgrade? Is there a work around, ie upgrading to tx2015-tx2016-tx2017? 

  • 0
    Thomas Lørup Duun

    Hi Martin,

    To upgrade your 14.2.6 project you need to point TX DWA to the repository. It is not possible to upgrade using an export / import. 

    In your scenario, you could restore a backup of the repository database from the live system on your local system and then have TX DWA upgrade it. 

    If you need further assistance on this, please contact support; 


  • 0
    Thomas Idelot

    Hi Thomas,

    Do you have any plans on making future upgrades more easy to perform ?

    It's not that complicated but it takes a lot of time nevertheless, I would really like to be able to upgrade In Place, meaning just launch a setup, click next/next/next and be done with it ;)

  • 0
    Thomas Lørup Duun

    Hi Thomas,

    Upgrade is launch setup, click next, next, next, finish. Then start TX DWA and if will perform an upgrade of the repository. To put the upgrade into effect you ofcourse need to deploy and execute the project. I do not see how we could make this simpler while still giving you the option to run side-by-side versions and possibility to perform rollbacks. 

  • 0
    Thomas Idelot


    Thanks for the answer, and you're right as I said it is not that complicated.

    Maybe that's more a feeling as my Deploy&Execute can take a very long time (and i don't need rollback capability as I do a snapshot before the upgrade).

    Anyway, keep up the good work, it's always nice to see your tool evolve in the right direction :)



Please sign in to leave a comment.