Deploy.ps script fails at configuring sharepoint site

[damianmayer]

Description

Scipt fails at Applying provisioning template... to the SharePoint site.

Tried amending the wait timeout in the script from 60 to 120 and even 180 seconds - in each case it fails at this point with:

Failed to configure the SharePoint site {0} The remote server returned an error: (404) Not Found.
At C:\provision-assist-m365\Source\Scripts\deploy.ps
1:682 char:9

•     throw('Failed to configure the SharePoint site {0}', $_.Excep ...
  

•     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (System.Object[]:Object[]) [], RuntimeException
  • FullyQualifiedErrorId : Failed to configure the SharePoint site {0} The remote server returned an error: (404) Not Found.

When timeout was set to 120 seconds or greater I am able to see the site being created in the SharePoint admin centre prior to the timeout error

Steps to reproduce

Expected results

site should be configured by the script

Actual Results

Script fails and I have a partial deployment - site is created but not configured.

Solution component

Deployment Script

Operating system (environment)

Windows

Additional Info

No response

[alexc-MSFT]

Hi @damianmayer we've seen some issues with the PnP module in the past so this could be one of them. Can you please check the SPO site and see if any of the lists are present?

Also did you see this message in the PowerShell window? "Applied template"

I'm trying to ascertain whether it was the PnP template that failed or the part after that which is where it configures columns and creates list items.

The other thing you can try which will give us a better idea of the error is to turn on the PnP log before running the script, you will need to run this cmdlet:

Set-PnPTraceLog -On -LogFile "C:\log.txt"

Feel free to amend the path to the log file, after running the script again you can check the contents of the log file and it may give us a better error message.

Thanks

[damianmayer]

Lists not present in the SharePoint site. Applied template did not show in Powershell. error message in the logs appears to say that it gets a 404 (not found) error when trying to find the SharePoint site. Can share detailed logs privately. URL anonymised below. 2 critical lines in the logs: powershell.exe Error: 0 : 2023-08-03 15:54:24.4730  [PnP.Framework]   [0]   [Error]     ExecuteQuery threw following exception: Microsoft.SharePoint.Client.ServerException: Cannot get site https://domainname.sharepoint.com/sites/PASite. powershell.exe Error: 0 : 2023-08-03 15:56:27.1926  [PnP.Framework]   [0]   [Error]     ExecuteQuery threw following exception: System.Net.WebException: The remote server returned an error: (404) Not Found. I can confirm that the site was present and visible in the SP admin centre PRIOR to the error occurring.

…

________________________________ From: Alex Clark ***@***.***> Sent: 03 August 2023 15:44 To: pnp/provision-assist-m365 ***@***.***> Cc: Damian Mayer ***@***.***>; Mention ***@***.***> Subject: Re: [pnp/provision-assist-m365] Deploy.ps script fails at configuring sharepoint site (Issue #5) Hi @damianmayer<https://github.com/damianmayer> we've seen some issues with the PnP module in the past so this could be one of them. Can you please check the SPO site and see if any of the lists are present? Also did you see this message in the PowerShell window? "Applied template" I'm trying to ascertain whether it was the PnP template that failed or the part after that which is where it configures columns and creates list items. The other thing you can try which will give us a better idea of the error is to turn on the PnP log before running the script, you will need to run this cmdlet: Set-PnPTraceLog -On -LogFile "C:\log.txt" Feel free to amend the path to the log file, after running the script again you can check the contents of the log file and it may give us a better error message. Thanks — Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZTMAHNLDAN5WVTNX5HZVCLXTO2MHANCNFSM6AAAAAA3CVEHYU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[alexc-MSFT]

@damianmayer hmm very odd, I'll try and deploy it again here and see if I receive the same error.

[ilyhel]

@damianmayer Hi are you using the https://domainname.sharepoint.com/sites/PASite with domainname as spoTenantName? If yes try to check the parameters.json file, it may that you missed something

[ilyhel]

@damianmayer @alexc-MSFT I just change the provisioning xml schema with older FrameWork engine '2021/03' like this and it's work fine.
<pnp:Provisioning xmlns:pnp="http://schemas.dev.office.com/PnP/2021/03/ProvisioningSchema"> <pnp:Preferences Generator="PnP.Framework, Version=1.10.2.0, Culture=neutral, PublicKeyToken=0d501f89f11b748c" /> <pnp:Templates ID="CONTAINER-TEMPLATE-1B3C2327DFE74A12A0C492DD708CB5DB"> <pnp:ProvisioningTemplate ID="TEMPLATE-1B3C2327DFE74A12A0C492DD708CB5DB" Version="1" BaseSiteTemplate="GROUP#0" Scope="RootSite"> <pnp:WebSettings RequestAccessEmail="" NoCrawl="false" WelcomePage="SitePages/Home.aspx" SiteLogo="{site}/_api/GroupService/GetGroupImage?id='71e18ff0-3e0a-469b-982b-41da61771d21'&amp;hash=638267757601246977" AlternateCSS="" MasterPageUrl="{masterpagecatalog}/seattle.master" CustomMasterPageUrl="{masterpagecatalog}/seattle.master" CommentsOnSitePagesDisabled="false" QuickLaunchEnabled="true" MembersCanShare="true" SearchScope="DefaultScope" SearchBoxInNavBar="Inherit" /> <pnp:SiteSettings AllowDesigner="true" AllowCreateDeclarativeWorkflow="true" AllowSaveDeclarativeWorkflowAsTemplate="true" AllowSavePublishDeclarativeWorkflow="true" SearchBoxInNavBar="Inherit" SearchCenterUrl="" />

[alexc-MSFT]

@ilyhel interesting, I've not had the XML fail for me but this could be due to PnP updates. @damianmayer did @ilyhel 's suggestion work for you?

[alexc-MSFT]

@ilyhel any updates on this please?