Hello I have downloaded and installed the SharePointListAdaptersSetup.msi, loaded the components into BIDS (2008), pulling data from a sharepoint list into SQL, all runs fine in BIDS. Load the package onto SQL Server 2008R2 into MSDB. I then set up a Job under SQL server agent and get the following (note I have also installed the msi above ont he server and restarted the services) Can anyone help? Executed as user: PALTD\SQLSERVER. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 11:30:00 Error: 2011-07-28 11:30:00.53 Code: 0xC00490F7 Source: Export Data Export Data (Timesheet SharePoint List [235]) Description: The managed pipeline component "Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource, SharePointListAdapters, Version=1.0.0.0, Culture=neutral, PublicKeyToken=933a2c7edf82ac1f" could not be loaded. The exception was: Could not load file or assembly 'SharePointListAdapters, Version=1.0.0.0, Culture=neutral, PublicKeyToken=933a2c7edf82ac1f' or one of its dependencies. The system cannot find the file specified.. End Error Error: 2011-07-28 11:30:00.53 Code: 0xC0047067 Source: Export Data Export Data (SSIS.Pipeline) Description: The "component "Timesheet SharePoint List" (235)" failed to cache the component metadata object and returned error code 0x80131600. End Error Error: 2011-07-28 11:30:00.53 Code: 0xC004706C Source: Export Data Export Data (SSIS.Pipeline) Description: Component "component "Timesheet SharePoint List" (235)" could not be created and returned error code 0xC0047067. Make sure that the component is registered correctly. End Error Error: 2011-07-28 11:30:00.53 Code: 0xC0048021 Source: Export Data Export Data (Timesheet SharePoint List [235]) Description: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "". End Error Error: 2011-07-28 11:30:00.53 Code: 0xC004801F Source: Export Data Export Data (SSIS.Pipeline) Description: The component metadata for "component "Timesheet SharePoint List" (235)" could not be upgraded to the newer version of the component. The PerformUpgrade method failed. End Error Error: 2011-07-28 11:30:00.70 Code: 0xC004801F Source: Export Data SSIS.Pipeline Description: The component metadata for "component "Timesheet SharePoint List" (235)" could not be upgraded to the newer version of the component. The PerformUpgrade method failed. End Error Error: 2011-07-28 11:30:00.78 Code: 0xC0048021 Source: Export Data Timesheet SharePoint List [235] Description: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "". End Error Error: 2011-07-28 11:30:00.78 Code: 0xC0047017 Source: Export Data SSIS.Pipeline Description: component "Timesheet SharePoint List" (235) failed validation and returned error code 0xC0048021. End Error Error: 2011-07-28 11:30:00.78 Code: 0xC004700C Source: Export Data SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2011-07-28 11:30:00.78 Code: 0xC0024107 Source: Export Data Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:30:00 Finished: 11:30:00 Elapsed: 0.593 seconds. The package execution failed. The step failed.

did you register them in GAC util? this thread maybe helpful: http://sqlsrvintegrationsrv.codeplex.com/discussions/50481http://www.rad.pasfu.com My Submitted sessions at sqlbits.com

you can check assemblies in the GAC in production machine in this way: http://msdn.microsoft.com/en-us/library/9x295t9k.aspxhttp://www.rad.pasfu.com My Submitted sessions at sqlbits.com

Thanks for your response I actually re-installed the msi as I may have installed as "Just Me" not "Everyone", this seemed to get over the first issue. I am now getting the below, so I went into the SharePoint List Source in BIDs and changed the batch size in the Custom Properties tab down to 300, still no good. There are only 1700 records (will grow) in the list at the moment... Do you have any ideas for the below? Regards Tony Executed as user: PALTD\SQLSERVER. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 12:49:30 Error: 2011-07-29 12:49:33.49 Code: 0xC0047062 Source: Export Data Timesheet SharePoint List [235] Description: Microsoft.Samples.SqlServer.SSIS.SharePointUtility.SharePointUnhandledException: Unspecified SharePoint Error. A possible reason might be you are trying to retrieve too many items at a time (Batch size) ---> System.ServiceModel.FaultException: Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) 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) --- End of inner exception stack trace --- 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, 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) End Error Error: 2011-07-29 12:49:33.49 Code: 0xC0047017 Source: Export Data SSIS.Pipeline Description: component "Timesheet SharePoint List" (235) failed validation and returned error code 0x80131500. End Error Error: 2011-07-29 12:49:33.49 Code: 0xC004700C Source: Export Data SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2011-07-29 12:49:33.49 Code: 0xC0024107 Source: Export Data Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:49:30 Finished: 12:49:33 Elapsed: 3.323 seconds. The package execution failed. The step failed.

seems the message size is problem, but as this is third party component I think best location which you can get help is the component web address discussion board: http://sqlsrvintegrationsrv.codeplex.com/discussionshttp://www.rad.pasfu.com My Submitted sessions at sqlbits.com

I faced the same kind of issue while using a source component which we developed according to our requirement. The issue was fixed by changing the execution options to 32 bit. Job execution options Check the box of Use 32 bit runtime Hope this will help you cheers