SharePointListAdapters For SqlServer2005 fail with timeout

Jul 8, 2010 at 7:46 AM

SQL job fail with message: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. Workflow associated with list, without workflow, everything seems OK. Thank you for assistance!

Jul 14, 2010 at 10:10 PM
Edited Jul 14, 2010 at 10:16 PM

In the debug mode of SSIS, run your project & find the component that is timing out.  If it the component is either a SharePoint List Destination or SharePoint List Source (stuff from this codeplex project), change the property of batch size to 1 (a "worst case") and see if you still get the issue.  I find that SPList updates take a good amount of time, and if you have a WF associated with that list, lots of WF code may be slowing down the processing even further.  You can trigger WF code in many ways, so your list might be doing that while the SSIS adapter is trying to update or delete or insert.  Find a batch size that works by experimenting.

 

Pritish

 

 

 

 

http://pritishwrites.blogspot.com
Aug 3, 2010 at 7:43 AM

Grab the beta version - all wcf timing constraints have been removed.

Great points on the WF behind the scenes, thanks pjacob - great points there on optimizing this.

Oct 14, 2010 at 9:32 AM

After upgrade to new betaversion, I can't create or modify project with Sharepoint List Source or Sharepoint List Destination (WIN7 Pro, Visual Studio 2005, MS SQL 2005 STD)

The component could not be added to the Data Flow task.
Could not initialize the component. There is a potential problem in the ProvideComponentProperties method.
Additional information:
Error at Data Flow Task [DTS.Pipeline): Component "component"" (1)" could not be created and returned error code 0x80131600. Make sure that the component is registered correctly.

Jan 13, 2011 at 12:48 PM
kevinidzi wrote:

Grab the beta version - all wcf timing constraints have been removed.

Great points on the WF behind the scenes, thanks pjacob - great points there on optimizing this.

Kevin, we are running into the issue as well with this timeout message.  We are using the released "june 2010" version.  You mention on Aug 3, 2010 to get the beta version since the timing constraints have been removed.  Looking through the source check in notes, there is a comment of "Increased Timeouts for WCF Proxies" on 6/2. Is this the timeout that causes this issue?  If so, was it in the released build for June or does this fix only exist in the beta build?

Thanks!

Feb 22, 2011 at 5:14 AM

The timeout issue was only resolved in the beta version.