New Post: SharePointListAdapter for SQL2014 (beta) is released!

Hi fan130,

here are the results of my testing:

Environment:
Windows Server 2008 R2, running on VMware Workstation

Step 1:
I have installed:
SQL Server 2012, including Integration Services, Visual Studio 2010
SharePoint Foundation 2013
SharePoint List Adapters 2012 (2012-01-28)

I made a little SSIS-Package, just writing some data into a simple SharePoint-List.
Development in Visual Studio: ok
Running in Visual Studio: ok
Publish: ok
Running in SQL Agent: ok

Step 2:
Remove SharePoint List Adapters 2012
Install SharePoint List Adapters 2014 (2015-06-25)
Still running SQL 2012.
Restart Server.

Open Visual Studio, open Package.

And I get the NTLM-Error! (Also when I try to run the package in SQL Agent.)

Step 3:
Install SQL Server 2014 – Integration Services (not the DB-Engine)
Install SQL Server Data Tools for VS 2013
Remove SharePoint List Adapters 2014
Install SharePoint List Adapters 2014 (2015-06-25)
Restart Server.

Open VS 2013, create new Project / package …
create SharePoint List Destination in my dataflow
fill out SiteListName etc., klick on “Refresh” – I get the NTLM-Error.

Open Visual Studio 2010, open my package – I get the NTLM-Error.

Step 4:
Remove SharePoint List Adapters 2014
Install SharePoint List Adapters 2012 (2012-01-28)
Restart Server.

Open Visual Studio 2010, open my package.
No Error, I can run the package in Visual Studio and in SQL Agent.

Open Visual Studio 2013, open my package.
I get a different error, because the SharePoint List Adapters and the SPCred Connector are no longer available.
This is funny, because this works on my production server. The production server is now running SQL 2014, Visual Studio 2010, SharePoint List Adapters 2012, where I can develop and run my package in Visual Studio without any problem, but I am running into an error when trying to publish the package (for running it in sql agent). The main difference: my production machine is just running SQL 2014 with VS 2013, while the server I’ve been testing now is running SQL 2012 and SQL 2014 and VS2010 and VS2013.

I hope this helps.

If you need more information just let me know.

Looking forward to read from you soon.

Mikel