Error: The connection manager '' is not properly installed on this computer

20 August 2014
Daniel Cai

We have received a few reporting of "The connection manager '' is not properly installed on this computer" error from our customers who are using SSDT-BI for Visual Studio 2013. The following are the entire error message reported by Visual Studio if you try to create a connection manager developed a third-party vendor or yourself (if you are writing a homegrown custom integration solution).

===================================
 
The new connection manager could not be created. (Microsoft Visual Studio)
 
===================================
 
The connection manager '' is not properly installed on this computer. (Microsoft.DataTransformationServices.Design)
 
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%C2%AE%20Visual%20Studio%C2%AE%202012&ProdVer=11.0.50727.1&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ConnectionManagerNotInstalled&LinkId=20476
 
------------------------------
Program Location:
 
   at Microsoft.DataTransformationServices.Design.DtsBasePackageDesigner.GetConnectionInfo(String creationName, IServiceProvider serviceProvider)
   at Microsoft.DataTransformationServices.Design.ConnectionManagerDesigner.InitializeConnectionManagerUI()
   at Microsoft.DataTransformationServices.Design.ConnectionManagerDesigner.OnNewConnectionAdded(ConnectionManagerUIArgs connectionUIArg)
   at Microsoft.DataTransformationServices.Design.DtsConnectionService.CreateConnection(String connectionType, ConnectionManagerUIArgs connectionUIArg)

This is a bug of the initial release of SSIS 2014 design time bits. The solution for this problem is simple, you just have to uninstall the SSDT-BI software that you have previously installed, and use the following link to download and install a newer release which should fix the problem.

http://www.microsoft.com/en-ca/download/details.aspx?id=42313

For SSIS 2014 run-time, you should at least get its cumulative update 2 installed (we noticed that the cumulative update includes some other important fixes, and it is highly recommended).

This error happens to any third-party or custom SSIS connection managers, we are luckily one of such vendors being affected by this bug.

Hope this helps.

 SQL   SSIS 
comments powered by Disqus