In preparation for a SQL upgrade from 2008 to 2016, I am attempting to upgrade the SSIS SharePoint Adapter used in our BIDS project to the latest adapter version, which supports 2016. After following instructions on the site which refer to updating the version in the XML (update VERSION=1.0.0.0 to VERSION=1.2008.0.0), I am not able to open the existing SPCRED connection manager or create a new one. The error received is: The connection manager user interface specified by type name 'Microsoft.Samples.SqlServer.SSIS.SharepointListConnectionManager.CredentialConnectionManagerUI, SharepointListConnectionManager, Version=1.0.0.0, Culture=neutral,PublicKeyToken=f4b3011e1ece9d47' could not be loaded. (Microsoft.DataTransformationServices.Design).
Im guessing Im missing updating the version number somewhere, but I cant find it in the package. Is there a setting in the project itself or somewhere else on the computer?
When I leave the version number as 1.0.0.0, I get 7 other errors when an existing package loads that uses the adapter. When I update the version number to 1.2008.0.0, the package loads without errors, but I can not create or edit SPCRED connection managers.
I should also mention, I am attempting to use the most recent adapter while still using SQL 2008 and BIDS. My hope was to get this working with our current version and have it transparent as it can be when we migrate to SQL 2016. If the version of SQL/BIDS is the cause of the errors, I am unable to tell at this time.
Any guidance in resolving this would be greatly appreciated.
Im guessing Im missing updating the version number somewhere, but I cant find it in the package. Is there a setting in the project itself or somewhere else on the computer?
When I leave the version number as 1.0.0.0, I get 7 other errors when an existing package loads that uses the adapter. When I update the version number to 1.2008.0.0, the package loads without errors, but I can not create or edit SPCRED connection managers.
I should also mention, I am attempting to use the most recent adapter while still using SQL 2008 and BIDS. My hope was to get this working with our current version and have it transparent as it can be when we migrate to SQL 2016. If the version of SQL/BIDS is the cause of the errors, I am unable to tell at this time.
Any guidance in resolving this would be greatly appreciated.