Installing Task Factory

 Task Factory users running version 2020.1.4 or older (released prior to May 27, 2020): There's an important Task Factory update. Please visit here for more details.

Download: For more information about Task Factory pricing or downloading a trial, see the Task Factory product page.


Additional Information: See the System Requirements article for details on what's needed to install Task Factory.

Additional Information

Installing Task Factory

Note:  Task Factory must be installed on the server where the packages will be executing.

Complete the following steps to install Task Factory:

1. Start the Task Factory installer by running the TaskFactory.exe file. Select your install destination from the drop-box, then select the checkbox to agree to the license terms and conditions. Select Next to continue.

SentryOne Task Factory Installer

2. Select the Typical or Custom setup type, then select install.

Note:  The Typical setup is recommended for most customers.

Important:  If you choose the Custom installation for the 2016 version, you must include the 2012 and 2014 installations (which are selected by default).

SentryOne Task Factory Typical setup
Typical Install

SentryOne Task Factory Custom setup
Custom Install
SentryOne Task Factory Custom Setup components
Select Custom Components

Note:  The installation process may take several minutes. You can monitor the status through the installer.

SentryOne Task Factory Installation status

3.  After the installation is complete, the confirmation window displays. Select Finish to complete the installation.

SentryOne Task Factory Installation select Finish

Success: The Task Factory installation is complete. 

What's next?

Task Factory in SSIS Toolbox

See the Task Factory Connection Managers article for instructions on adding new connection managers in Visual Studio.

Task Factory in the Visual Studio SSIS Toolbox and SSIS Connection ManagerExample of Task Factory in the Visual Studio SSIS Toolbox and SSIS Connection Manager available for SSIS packages.

Note:  If you do not see these options in Visual Studio, ensure you have installed Task Factory to an environment that meets the system requirements.

If your Task Factory components aren't displaying in the SSIS toolbox after installation, you may not be targeting a supported version of SSIS. See the Task Factory Items not showing up tab in the Common Errors article for more information.

Adding Task Factory components in BIDS/Visual Studio 2010 or lower

Before you can use the Task Factory components in BIDS, you must add them to your toolbox. 

Note:  Adding Task Factory components in BIDS is not necessary with SQL Server Data Tools (2012 or higher).

Complete the following steps to add the Task Factory components to your toolbox:

  1. Open an SSIS package, then open your toolbox (View > Toolbox).
  2. Right click the toolbox window and select Choose Items...Add Task Factory components to your toolbox
  3. Select the SSIS Control Flow Items tab and select all deselected tasks that begin with TF. Next, follow the same step with the SSIS Data Flow Items tab.
  4. After you have selected all Task Factory Control Flow and Data Flow items, select OK to save and confirm your selections. Add Task Factory Components to your toobox


Another installation is in progress

If you receive this popup while installing Task Factory:

  1. Check Task Manager to see if another installation of Task Factory is running. If so, choose End Task.
  2. Restart the machine.

Installation error message

Task Factory Installer Fails To Complete Due To Invalid Digital Signature

See the article above for information about resolving issues related this error message:

A file that is required cannot be installed because the cabinet file C:\Users\ has an invalid digital signature. This may indicate that the cabinet file is corrupt.Invalid Digital Signature error message

Creating a Task Factory Installation Log

If you're experiencing other errors while installing Task Factory, see the article above for instructions to create a log file to determine where the installer is failing.