I had a similar problem. To get the job done with no error I added the account that runs the package to the administrator group of the server that runs sharepoint. Also this account needs to have at least read access on each list.
↧
New Post: SharePoint List Adapter Source Not Working
↧
New Post: Can i use this with Sharepoint 2010?
Yes, it works with SP 2010
↧
↧
New Post: Can i use this with Sharepoint 2010?
When i look at the the component tyoe i have installed its version 1.0.0.0.
Is this what i should be using for Sp 2010 on Sql server 2008 r2 64 bit.
As i have been trying it but i keep getting error
Error: 0xC0047062 at Data Flow Task, SharePoint List Destination [364]: Microsoft.SqlServer.Dts.Pipeline.UnsupportedBufferDataTypeException: Column data type DT_I4 is not supported by the PipelineBuffer class. at Microsoft.SqlServer.Dts.Pipeline.PipelineBuffer.GetDouble(Int32 columnIndex) at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListDestination.ProcessInput(Int32 inputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket) Error: 0xC0047022 at Data Flow Task, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "SharePoint List Destination" (364) failed with error code 0x80131600 while processing input "Component Input" (371). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. Error: 0xC0047062 at Data Flow Task, SharePoint List Destination [16]: Microsoft.SqlServer.Dts.Pipeline.UnsupportedBufferDataTypeException: Column data type DT_I4 is not supported by the PipelineBuffer class. at Microsoft.SqlServer.Dts.Pipeline.PipelineBuffer.GetDouble(Int32 columnIndex) at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListDestination.ProcessInput(Int32 inputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket) Error: 0xC0047022 at Data Flow Task, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "SharePoint List Destination" (16) failed with error code 0x80131600 while processing input "Component Input" (23). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. Information: 0x40043008 at Data Flow Task, SSIS.Pipeline: Post Execute phase is beginning.
Any ideas hat i'm doing wrong?
Thanks in advance
↧
New Post: SSIS is not using the provided custom Sharepoint credentials
Look at the SQL Server Agent (MSSQLSERVER) user in the Sql Server Configuration Manager. Make sure that user has been added to the sharepoint site you are trying to write to.
↧
New Post: SSIS is not using the provided custom Sharepoint credentials
This was impossible in the context. The goal of providing the sharepoint credentials to the SP Source/Destination plugin was to avoid this issue. But obviously, that feature is bugged.
I ended up scripting the whole thing by hand without using the plugin and it worked.
↧
↧
New Post: Can i use this with Sharepoint 2010?
All fixed.
Very good tool indeed.
Sql server 2008 prefereed type DT_WSTR instead of DT_STR for some reasons :(.
Not after fixing that had issue with the Sql List Adapter stating couldn't load the componenets....... another horror.
Tip when using the Sql List Adapter components make sure the public tokens match.
Noticed the one i have on the dev is different from the one in production.
Also if you move packages from one server to the other make sure you use EncryptSensitiveWithPassword.
Thats all for that.
Cheers
↧
Commented Issue: EzAPI: Set EzExecuteSqlTask.Connection Error (with answer) [15164]
EzExcutables.cs LN: 813
Error on set the Connection when you create a ExecuteSqlTask :
(host.InnerObject as ExecuteSQLTask).Connection = value.Name;
i fixed it also with this code :
host.Properties["Connection"].SetValue(host, value.Name);
Comments: ** Comment from web user: agilmore **
Error on set the Connection when you create a ExecuteSqlTask :
(host.InnerObject as ExecuteSQLTask).Connection = value.Name;
i fixed it also with this code :
host.Properties["Connection"].SetValue(host, value.Name);
Comments: ** Comment from web user: agilmore **
Hi
This problem can also be solved by adding the configuration mentioned in this post - http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/a85ec120-eec6-438d-aef4-55f82d14a869
The issue is a problem with the cast in this line of code (host.InnerObject as ExecuteSQLTask).Connection = value.Name; and incompatibility with .NET 4.0.
Thanks - Adam Gilmore - Dimodelo.com
↧
New Post: HTTP Request is unauthorized - claims authentication & kerberos
I know it has been asked several times, but I'm having a problem using the adapter with a SP 2010 site that is configured with claims authentication and Kerberos. I'm not even able to get this to run in BIDS using my account which is a site collection admin. We have just switched from classic based authentication to claims.
If I go into my web application, and change the authentication under "claims authentication types" from "Negotiate (Kerberos)" to NTLM, it works. If I switch back, to using kerberos, it doesn't work.
Any ideas?
The component has detected potential metadata corruption during validation.
Error at Update Warehouse [SharePoint List Source 1 [2304]]: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Ntlm'. The authentication header received from the server was 'NTLM'. --->
System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory factory)
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.ViewsService.ViewsSoap.GetViewCollection(GetViewCollectionRequest request)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.ViewsService.ViewsSoapClient.ViewsService_ViewsSoap_GetViewCollection(GetViewCollectionRequest request)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.ViewsService.ViewsSoapClient.GetViewCollection(String listName)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.Adapter.ViewsAdapter.GetSharePointListViews(String listName)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.Adapter.ViewsAdapter.GetViewList(String listName)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.Adapter.ListsAdapter.LookupViewName(String listName, String viewName)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.ListServiceUtility.GetFields(Uri sharepointUri, NetworkCredential credentials, String listName, String viewName)
at Microsoft.Samples.SqlServer.SSIS.SharePointUtility.ListServiceUtility.GetFields(Uri sharepointUri, String listName, String viewName)
at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource.GetAccessibleSharePointColumns(String sharepointUrl, String listName, String viewName)
at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource.ValidateSharePointColumns()
at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource.Validate()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostValidate(IDTSManagedComponentWrapper100 wrapper)
↧
New Post: Really slow performance when extracting from SharePoint
Hi,
Does any one have some suggestions to improve performance when just extracting data from a SP list? I'm using the adapter to extract data from our Diary solution, and when I extract our list of contacts, it takes several hours. I don't know the exact record count of the list, but my guess would be that it's around 500.000 records.
Other smaller lists works ok. I have another list with 22.000 records and that extracts within a few minutes.
I have tried to set the batch size to different values, but I can't really see it makes any big difference. The annoying thing is also that when I run the package, the step is just "yellow" for most of the times where it seems like there are no activity.
I can't be the only one that are struggeling with performance, so what have others done? Are the any "best practice" for setting the adapter for best performance?
Regards
Steen
↧
↧
Commented Issue: Adapters fail in Claims environment. [18463]
When trying to connect the adapters to SharePoint lists in a SharePoint farm configured to use Claims authentication, the following error message is return when Visual Studio attempts to validate the SSIS package, and also when attempting to run the package.
System.ServiceModel.Security.MessageSecurityException: The HTTP request was forbidden with client authentication scheme 'Ntlm'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
The same package, with the adapters pointing to lists in a SharePoint farm that does not use Claims works perfectly.
Comments: ** Comment from web user: ChadC **
System.ServiceModel.Security.MessageSecurityException: The HTTP request was forbidden with client authentication scheme 'Ntlm'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
The same package, with the adapters pointing to lists in a SharePoint farm that does not use Claims works perfectly.
Comments: ** Comment from web user: ChadC **
I'm running claims and kerberos, and I ran into these same errors. I think it is because the Security being set in the SharePoint Utility ListsAdapters and ViewsAdapter class are using a ClientCredentialType = HttpClientCredentialType.Ntlm. This is forcing the services to try and negotiate an NTLM based authentication. If you switch the type to Windows, then it seems to be able to negotiate the appropriate protocol to authenticate (at least this fix worked for me in my environment).
ViewsAdapter.VB, make the change on line 77 to:
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Windows
ListsAdapter.VB, make the change on line 79 to:
binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Windows
↧
Created Issue: Add the DLLs for SSIS to the source code [18703]
When you grab the source and make a change and try to build, it is a PITA. I don't have all of the appropriate SQL client tools installed, so I was unable to actually run the makeinstall.cmd successfully. I had to go in and strip out all of the versions of SQL that I didn't need, then fix all of the references. It was a pain.
Or, if you are unable to distribute the DLLs, then can some instructions be added to tell end users how to easily download and install the appropriate files and make it easier for them to do a build.
It is a great tool when you only have to install the MSI :)
Or, if you are unable to distribute the DLLs, then can some instructions be added to tell end users how to easily download and install the appropriate files and make it easier for them to do a build.
It is a great tool when you only have to install the MSI :)
↧
Commented Issue: Add the DLLs for SSIS to the source code [18703]
When you grab the source and make a change and try to build, it is a PITA. I don't have all of the appropriate SQL client tools installed, so I was unable to actually run the makeinstall.cmd successfully. I had to go in and strip out all of the versions of SQL that I didn't need, then fix all of the references. It was a pain.
Or, if you are unable to distribute the DLLs, then can some instructions be added to tell end users how to easily download and install the appropriate files and make it easier for them to do a build.
It is a great tool when you only have to install the MSI :)
Comments: ** Comment from web user: mmasson **
Or, if you are unable to distribute the DLLs, then can some instructions be added to tell end users how to easily download and install the appropriate files and make it easier for them to do a build.
It is a great tool when you only have to install the MSI :)
Comments: ** Comment from web user: mmasson **
Which component do you mean? (Sharepoint List connectors?)
No, in general we can't redistribute the product DLLs. The components should be buildable if you have a SQL installation... all SSIS dependencies will be found in the GAC (and most will be also be under the <product>\SDK folder).
↧
New Post: SSIS is not using the provided custom Sharepoint credentials
Can someone clarify the true intent of the Custom Credentials? Is this expected to work with AD domain accounts? What trusts must be in place for the credentials to work?
↧
↧
New Post: Data Missing in SP List Destination
Having the same problem with latest adapters. When using Destination adapter and loading decimal numbers from SQL - data is missing in SP List. Integers are fine. Any advice?
Thanks
↧
New Post: Data Missing in SP List Destination
wasilow wrote:
Having the same problem with latest adapters. When using Destination adapter and loading decimal numbers from SQL - data is missing in SP List. Integers are fine. Any advice?
Thanks
it turned out to be data conversion problem...needed to conver from numberic to double precision float before loading int SP List Destination
↧
New Post: download location
I went to the download page for EzAPI - Package Generation API (SQL 2012) but I see no download link. It says there are no downloads available...why?
↧
Source code checked in, #94876
Checked in by server upgrade
↧
↧
Source code checked in, #94877
Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563
↧
New Post: Upgrading my SSIS package for SQL 2012 Server
Hi,
I am upgrading my SSIS package to SQL 2012 Server. My SSIS package connects to a SharePoint 2010 list to read/update data.
Once I upgraded my SSIS package to SQL 2012 BIDS (Visual Studio 2010), the component is not working. Its giving me the following error:
"Error 4 Validation error. Transfer SQL Data to SP: Transfer SQL Data to SP: The component metadata for "Step 1, clsid {874F7595-FB5F-40FF-96AF-FBFF8250E3EF}" could not be upgraded to the newer version of the component. The PerformUpgrade method failed."
Do you have a version that works with this version?
Thanks a lot,
Regards,
Bhaskardeep Khaund
↧
New Post: SharePoint List to SQL transfer - How to eliminate duplicate data?
I have been asked to see if I can create a way to send a SharePoint list to an SQL table. So I downloaded and installed the SSIS SharePoint List Adapters for SQL Server Integration. Setup a new project in Visual Studio 2008.
I then setup the Data Flow where I have the SharePoint List as the source and OLE DB as destination. I mapped the columns I wanted. Made sure the data types match, etc...Ran the project and everything was fine. No errors or warnings. I saw the data in the SQL table. Then I ran the project again and it seems like everything gets duplicated. So initially SSIS sent 80 records from SharePoint to SQL then the second time I ran it it sent the same ones again so I now have 160 records in SQL.
Is there any way to only transfer new entries or ones that have been updated?
I tried searching but do not see that option anywhere.
This is my first time using VS2008 and SSIS.
Thanks
↧