Matthew Campbell - BI, Spatial, Temporal, etc.

On a recent client implementation, I was upgrading a client to use the Eldos BizCrypto Transport library which includes a few SFTP components that we were using.  I had been doing remote development on a virtual machine for a few weeks and was at the stage of dropping off the final deliverables.  The Eldos software had been installed on the production box.  I had tested an SSIS package with the new components on the production box to verify everything looked good.  I finally decided to verify that the components would work when called from a job when I started getting job failures.  I opened up the job history and found a most ugly error message:

The connection type "SFTP.BizCrypto" specified for connection manager "SFTP" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.

I was stumped.  I knew that the components had been installed.  I had tested them interactively via running a test package in BIDS.  Why in the world was it not able to find the connection manager type?

This was oversight on my part in not verifying whether there was a 64-bit version of the components installed.  It turns out that the BizCrypto transport library is only a 32-bit library.  As such, I needed to make sure that any packages that would be utilizing these libraries ran in the 32-bit runtime.  Simply open the job, then open the job step that calls a package utilizing these controls, switch to the Execution Options tab and check the ‘Use 32 bit runtime’ checkbox.  Once that’s done, you should be good to go.

I’d seen this issue pop up before when working with Excel data sources since in the past there was no 64-bit driver there either.  I was able to breathe much easier once I realized this was the issue and the job started running as expected.