pnp
A connectiTimeout Error when Applying Provisioning Template using PnP Framework 1.15 on .NET Core 8 on attempt failed
I am encountering a persistent issue when attempting to apply a provisioning template to SharePoint Online using the PnP Framework version 1.15, implemented in a .NET Core 8 environment written in C#. The specific method call causing the problem is web.ApplyProvisioningTemplate(template);. Whenever this command is executed, the process fails with a timeout error, indicating a failure to establish a connection to SharePoint Online. Error Message: sql Copy code Microsoft.Azure.WebJobs.Host.FunctionInvocationException: Exception while executing function: Functions.ApplyXmlToProjectWeb ---] Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcException: Result: Failure Exception: System.Net.WebException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [::ffff:52.105.42.27]:443 (onlinemontazebroz.sharepoint.com:443) ---] System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond... Steps to Reproduce: Create a .NET Core 8 application. Implement PnP Framework 1.15 to apply a provisioning template to SharePoint Online. Execute the web.ApplyProvisioningTemplate(template); method.
Thank you for taking the time to read my post. If anyone has any insights or suggestions on how to address the issue I've described above, I would greatly appreciate your assistance. Please let me know if there's any additional information I can provide.
Looking forward to your helpful responses.
Hi all,
I've run into timeout issues with ApplyProvisioningTemplate from PnP Framework when creating many client pages. It reminds me of past experiences where using ExecuteQuery() instead of ExecuteQueryRetry() caused similar problems, possibly due to the lack of retry mechanisms.
Could it be that ApplyProvisioningTemplate is using ExecuteQuery() somewhere without retries, leading to these timeouts? Anyone else noticed this or has insights?
Hi, I've encountered a similar issue regarding the ApplyProvisioningTemplate method. Did you resolve your issue in any way? If so, could you please share?
Thanks, Frank
