You might experience issues with the SQL Server Integration Services (SSIS) packages when downloading data from your Project Online OData feeds. The following error message is received:
The operation has timed out.
We are currently investigating the issue.
To work around this issue, increase the number of allowed connections to SharePoint and Project Online on the server that your SSIS package is configured to run. To do this, you need to edit the .NET Framework machine.config files and increase the number of allowed connections.
- Edit the following the following two files on the server that is running the SSIS package:
Note For the [version] folder, in most cases it'll be the most recent version of the .Net framework such as v4.0.xxxxx. However, if you have configured your SSIS package to use a different .NET Framework version, you need to update that version accordingly.
- Make a copy of the machine.config file as backup.
- Open each machine.config file and scroll all to way to the bottom of the file. At the very end of the file, add a space between the </system.web> and </configuration> tags and paste in the below snippet:
<system.net><connectionManagement><add address = "https://contoso.sharepoint.com/ " maxconnection = "30" /></connectionManagement></system.net>
- You must replace the address with your SharePoint domain. If your PWA site is "https://contoso.sharepoint.com/sites/pwa", then the address should be "https://contoso.sharepoint.com/".
- You can consider increasing or decreasing the maxconnection value suggested in this step, depending on how your SSIS package is configured. For example, if you have a larger number of feeds that you’re pulling concurrently that may require a larger number of connections. If it’s only a few, you can set it to a smaller value. For more information about the .NET Framework Connection Management setting, see Element for connectionManagement.
- Once you're done adding the snippet, the edited file should look like the following:
- Save the changes, and then close the file.
- Make sure that the edit is done on both machine.config files listed in step 1.
- To make sure that the setting takes effect, you can either stop and restart the application that the SSIS package runs under such as SQLAgent, or restart the server.
Article ID: 4043104 - Last Review: 14 Sht 2017 - Revision: 24