search

OfficeDev / microsoft-teams-emergency-operations-center

The Microsoft Teams Emergency Operations Center (TEOC) solution template leverages the power of the Microsoft 365 platform to centralize incident response, information sharing and field communications using powerful services like Microsoft Lists, SharePoint and more.
MIT License
95 stars 40 forks source link

Deployment Script Fails #149

Closed tjackson-bcg closed 12 months ago

tjackson-bcg commented 1 year ago

While deploying the app, it creates the SP site but fails at what looks like List creation. The path to the XML is not long nor contains double quotes like most of the issues I see. I've deleted the site and rerun the script several times. I've also re-registered the PNP app accepting all permissions. Running as a global admin. What next?

image

image

v-asshrirao commented 1 year ago

@tjackson-bcg, Thank you for reporting this. Can you please confirm if you are in GCC or GCCH tenant? If its GCCH tenant you will have to run provisioning script for GCCH which will ask for PNP App Client ID which you have registered as mentioned.

Please do let us know if this helps.

tjackson-bcg commented 1 year ago

We have a GCC tenant, not GCCH.

v-asshrirao commented 1 year ago

@tjackson-bcg, We hope you are running the script with SharePoint Administrator user.

Can you please confirm which version of PnPPowershell you are using?

tjackson-bcg commented 1 year ago

When we are prompted for Azure login, we are specifying a global admin user which will have Sharepoint permissions by default. We are using version 2.2.114 of the PnP.PowerShell module in Powershell

v-asshrirao commented 1 year ago

@tjackson-bcg , Request you to kindly update the PnP version. Please run below commands and then try to run provisioning script again. Uninstall-Module -Name PnP.PowerShell -AllVersions -Force

Install-Module PnP.PowerShell -RequiredVersion 1.12 -Force

Please let us know if this help.

tjackson-bcg commented 1 year ago

Downgraded PnP to 1.12 and re-ran the script. Same issue occurs. I was also using Powershell 7 originally and am now using Powershell 5.2. There is a slightly different error now.

image

v-asshrirao commented 1 year ago

@tjackson-bcg, Looks like permission issue. Please allow us some time to analyse this and we will update you ASAP. Meanwhile can you please try to open the site which is created and let us know if you are able to access that with the account you are trying to run the script?

microsoft-github-policy-service[bot] commented 1 year ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.