Custom ConnectionManager always returns null at runtime

Question

I have written a very simple custom connection manager inheriting from ConnectionManagerBase. My acquireconnections and release works as it should in design time on my source component. The issue is when I try and execute it in Visual Studio. I associate my connection with my component in design time and the value persists as it should. But when my source component calls acquireconnection and then checks the RuntimeConnectionCollection[0].ConnectionManager, it is always null. During design time it is there and establishes a connection fine but for the life of me I can't figure out what I am missing to make it work during run time. I know it has to be something simple but I have read code for ssis connection managers and source/destination components until I am blue in the face and can't see what I am missing. Does my savior exist on this forum? I am running Visual Studio 2019 with 3.12 of SSIS plugin. Framework version is 4.7.2 to compile on any cpu. Please let me know if anyone has any questions about anything and I am happy to answer.

Answer 1

I have a similar issue with a custom source component, still haven't found an answer. Any update?

Answer 2

Unfortunately, I was not able to figure this one out. I am confident it has something to do with my development installation/setup and not a code issue as it was a bit of a maze trying to figure out what components to install to get it all working. Since I didn't hear back from anyone with any information that was helpful, and it was more than painful making SSIS do something it probably shouldn't in my circumstance, I decided to abandon that customization and handle it a different way. Good luck on your finding a solution!

Answer 3

Hi,

We are facing exactly the same issue trying to create our own ConnectionManager with a VS 2019 and VS2022.

Did anyone found a solution ?

Regards

Gautier

Answer 4

I was able to reproduce the issue using ManicFarmer's example, throwing an error like so:

Error: 0xC001000E at Package: The connection "{AE90240C-4F45-46BB-9710-42EE473E2EF1}" is not found.

My environment was set up as follows:

• Visual Studio 2022
• SQL Server Integration Services Projects 2022 v1.5 extension
• TargetServerVersion = SQL Server 2022
• SQL Server 2019 was installed locally

As I was running everything in Visual Studio, I did not think the installed SQL Server version would matter. I even confirmed in the task manager that it was using DtsDebugHost.exe in the SQL 2022 (160) folder:

C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\CommonExtensions\Microsoft\SSIS\160\Binn

However then I upgraded SQL 2019 to SQL 2022 (v16.0.1000.6) and suddenly the "cannot find the connection manager with ID..." error went away and the package ran successfully. Perhaps there is a dependency missing in the Visual Studio SSIS Projects extension - or it was erroneously referring back to something installed with SQL 2019 instead of what is included in the extension.