# Downgrading CData SSIS edition drivers

**URL:** <https://community.cdata.com/t/downgrading-cdata-ssis-edition-drivers/717>\
**Category:** Editions\
**Tags:** article, ssis, connection-manager\
**Created:** [May 15, 2024, 7:01pm UTC](https://community.cdata.com/t/downgrading-cdata-ssis-edition-drivers/717 "2024-05-15T19:01:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_H](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@Andrew\_H](https://community.cdata.com/u/Andrew_H)\
**Post date:** [May 15, 2024, 7:01pm UTC](https://community.cdata.com/t/downgrading-cdata-ssis-edition-drivers/717/1 "2024-05-15T19:01:38Z")

</div>

Customers may have issues with preexisting connection managers for their packages if they downgrade without performing the proper steps. This fix should theoretically apply to non-CData drivers as well.

Common issues include: A newly added connection manager would be the same version as the uninstalled driver, A pre-existing connection manager returns something like “…is not recognized as a valid connection manager type”.

**Notes for downgrades:** Before completing any downgrade, make sure you backup your SSIS Package / the installers for the used SSIS Components so that you can continue working on another machine in case you make a mistake. We DO NOT advise users to downgrade without properly documenting everything they are doing for that downgrade.

STEPS:

1. Uninstall the current version of the SSIS driver you have.

- Windows: Add/Remove Programs

OR

- Navigate to the driver installation directory (“C:\Program Files\CData” by default) and run the “Uninstall” application from the driver’s folder.

2. Install the version of the SSIS driver you want.

3. (Optional if still having issues) \*\*Caution: improper configuration here can lead to major issues\*\*

Manually add the DLL we provide in the driver’s ‘lib’ folder to “\<\< Microsoft SQLServer Installation Folder \>\>\xxx\DTS\ PipelineComponents” and the Windows GAC “C:\Windows\Microsoft.NET\assembly\GAC\_MSIL”.

 ![162a02cb-8960-4c4e-b13e-e5c1700dc3ab.png](https://us1.discourse-cdn.com/cdata/original/1X/6d500f441a8651622dd3a0decc578e58d75673a7.png)

Please read this for more info before doing step 3: [https://stackoverflow.com/questions/47268587/for-a-custom-ssis-component-why-do-i-have-to-put-it-into-gac](https://stackoverflow.com/questions/47268587/for-a-custom-ssis-component-why-do-i-have-to-put-it-into-gac).