Hi @Kikot, Pavel ,
Just wanted to check, have you got the solution for this issue.
we are also facing the same issue.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi there, I installed 'Microsoft connector for Teradata' to use 'teradata Source' component within dataflow task but its not working when I try to add this :
TITLE: Microsoft Visual Studio
The component could not be added to the Data Flow task.
Could not initialize the component. There is a potential problem in the ProvideComponentProperties method.
ADDITIONAL INFORMATION:
Error at Data Flow Task [SSIS.Pipeline]: The module containing ", clsid {A21403DF-47CD-4066-A4AD-035C53DAE8E9}" cannot be located, even though it is registered.
Error at Data Flow Task [ [1]]: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
Exception from HRESULT: 0xC0048021 (Microsoft.SqlServer.DTSPipelineWrap)
BUTTONS:
OK
Current version of software:
VS2019 16.10.3 + SSDT 16.0.62106.24090
VS2017 15.9.36 + SSDT 15.1.62002.01090
In the beginning:
I had already installed Teradata TTU 17.00.00
Steps I tried to remediate that error but no positive result
1) Installed latest Teradata TTU 17.10.06.00 - didn't help
2) Re-Installed Microsoft Connector Version 4.0 for Oracle and Teradata by Attunity targeting SQL Server 2017 - no luck
3) Re-installed 'Microsoft connector for Teradata' -no luck
4) Uninstalled both 'Microsoft Connector Version 4.0 for Oracle and Teradata by Attunity' and 'Microsoft connector for Teradata' and
Installed 'Microsoft connector for Teradata' - didn't help
5) Tried to reinstall 'Microsoft Connector Version 5.0 for Oracle and Teradata by Attunity' and 'Microsoft connector for Teradata' - didn't help
Tried both x64 and x86 versions - get the same error all time.
6) Tried to switch SQL server targeted version from 2016 => 2019 and back. DIdn't help
7) Tried to switch run64bitruntime debugging option to false - didn't help
In both VS 2017 and VS 2019 I get the same error.
Any ideas how I can resolve this?
Hi @Kikot, Pavel ,
Just wanted to check, have you got the solution for this issue.
we are also facing the same issue.