SSIS 2012 package with Odata source-failure (part 2)

Deployment failure

In my previous post SSIS 2012 package with Odata source–failed to deploy project I have encountered a deployment problem with an SSIS project created in project deployment mode with VS2012 and deployed to SQL 2012.

In this package I have an OData connection to a SharePoint Odata service. I put the connection under the connection managers so that I could share the same connection amongst several packages in the project. The deployment failed on the system on which I was developing, as well as on another SQL 2012 server.

This a project connection

Maybe the OData should not be in the project connection managers, but defined each time as a package connection. I decided to create a new SSIS project with one package with the Odata connection defined in the package.

This is a Package connection

Change OData from Project to Package connection

The project with the Package connections deploys without errors in project deployment mode.

The project and package can be seen in the Integration Services catalog:

Package deploys but Executes with runtime errors

When I Execute the package, it fails with error

‘Error: The connection type "ODATA" specified for connection manager "OData Incidents" 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 shall have to investigate further.