April 29, 2015 at 8:39 am
I can't create any Data Flow Task. Once I create (tested and working) Connection (it doesn't matter if it is Excel, Flat File or other) and try to use it with a Source Assistant, I get the following messages:
===================================
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. (Microsoft Visual Studio)
===================================
Error at Data Flow Task [SSIS.Pipeline]: Component ", clsid {C4D48377-EFD6-4C95-9A0B-049219453431}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.
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)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()
at Microsoft.DataTransformationServices.Design.PipelineTaskDesigner.AddNewComponent(String clsid, Boolean throwOnError, Boolean select)
===================================
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. (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. (Microsoft Visual Studio)
===================================
Error at Data Flow Task [SSIS.Pipeline]: Component ", clsid {C4D48377-EFD6-4C95-9A0B-049219453431}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.
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 "".
Error at Data Flow Task [SSIS.Pipeline]: Component ", clsid {C4D48377-EFD6-4C95-9A0B-049219453431}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.
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)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()
at Microsoft.DataTransformationServices.Design.PipelineTaskDesigner.AddNewComponent(String clsid, Boolean throwOnError, Boolean select)
Exception from HRESULT: 0xC0048021 (Microsoft.SqlServer.DTSPipelineWrap)
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()
at Microsoft.DataTransformationServices.Design.PipelineTaskDesigner.AddNewComponent(String clsid, Boolean throwOnError, Boolean select)
Any ideas?
Thank you
April 29, 2015 at 2:53 pm
April 29, 2015 at 3:02 pm
Hmmmm..... Not really. Checked the PC, OS, all 64-bits.
February 17, 2016 at 7:25 am
Same issue found. Any fix?
June 27, 2017 at 5:33 am
I had the same issue. Turns out MS SQL 2012,MS SQL 2014 and MS SQL 2016 does not like to work side by side. I had 2012 and 2016 installed on my pc and when working in SSIS on visual studio 10 got the same issue. Had to do a repair on the MS SQL2012 datatools to get the problem sorted out.
December 25, 2017 at 9:17 am
henkvl - Tuesday, June 27, 2017 5:33 AMI had the same issue. Turns out MS SQL 2012,MS SQL 2014 and MS SQL 2016 does not like to work side by side. I had 2012 and 2016 installed on my pc and when working in SSIS on visual studio 10 got the same issue. Had to do a repair on the MS SQL2012 datatools to get the problem sorted out.
I also facing the same problem..i try this option is not working fine..please let me know other workaround possible for it
December 28, 2017 at 3:22 pm
Is this a solution that was created on another machine that you are now trying to run on yours? DO you have the Integration service running (not just the SSDT or BI solution open) ?
To check do :
Window+R
Type "services.msc" in the run window.
Look for SQl Server integration service in the console list
Report back on the status (running? Stopped? )
----------------------------------------------------
May 10, 2018 at 9:55 am
For me this happened when I installed SSMS 2017 on my machine using VS 2010 to build SSIS packages for a SQL 2012 server. I believe the issue came out of some conflict caused by that installation. Good news is that once I repaired my SQL Server 2012 (management tools only) the issue went away. Hope that helps someone.
September 13, 2018 at 6:53 pm
Have same issue, How do you repair SQL*Server 2012 management tools ? I will Google .. Does anyone know the name of the MSI involved re. this ? or some screen captures ?
November 26, 2018 at 5:22 pm
If you use the most recent version of MS Visual Studio ... e.g. Visual Studio 2017 .. you may find, like I did, that this issue goes away.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply