Use the version of Task Factory where the package is working across all of your environments. Download the version of Task Factory where the package was developed and ensure that this version is installed across all of your machines. Run the package on the version of Task Factory where it was originally created and delete the corrupted package. 
To fix the SSISReplacementTask error in your package(s), you can take one of the following actions:
For example, you're package was created targeting SQL Server 2017, and when you've opened the package on your current machine, the package is targeting SQL Server 2019.
You're using the same version of Task Factory that was used to develop the package, but you are targeting a different SQL Server version. For example, you developed the package in version 2020.0, and opened it in version 2019. You've opened a package that was developed on an higher version of Task Factory in an older version. You may run into the SSISReplacementTask error if you've done the following: When SSIS can't find your Task Factory components, it replaces the components with generic components, resulting in the SSIS.ReplacementTask error. The SSIS.ReplacementTask error occurs when SSIS is looking for your Task Factory components and can't find them (your component(s) may look online for assemblies, which can take a while). Important: SolarWinds recommends having backups of your packages, and storing these backups in a safe and accessible location.
0 kommentar(er)
