Forum Discussion
Hi everyone, when i create a new pwa site in project online. I am getting error?
- Jul 05, 2022
I got off the phone with Microsoft
I just got off the phone with Microsoft support.
Seemed that the GUI for setting this up didn't work and after running a few PowerShell commands it showed that PWA was disabled - PWAEnabled : Disabled
We ran these in PowerShell (we changed the name here to YOUR tenant name, and YOUR site):
Connect-SPOService -url https://M365TenantNameHere-admin.sharepoint.com
Get-SPOSite -Identity https://M365TenantNameHere.sharepoint.com/sites/PWASiteNameHere |fl
#PWAEnabled : Disabled
Set-SPOSite -Enable $true -identity https://M365TenantNameHere.sharepoint.com/sites/PWASiteNameHere
I am also having the same issue with one of our clients. This is the first time.
We created a POL site in the O365 Admin Portal. The site was okay and can be accessed. But after less than 10mins we got the "No PWA instance was found" error. I am one of the site collection Admin.
- Anil_kumar_AnakalaOct 20, 2021Copper Contributor
I had tried this, It worked for me.
Download and open the SharePoint online management shell
paste the code in shellIn strike off place type your tenant URL. In circle place type your account name. In underline place type your PWA site name.
After completion of cmds refresh the browser.
Test it in internet explorer, edge.
- Cathylou_BarbadoOct 20, 2021Copper ContributorHi Anil, thank you very much for this. Will try this one out. But may I know what causes this setting to be off? Based on what we experienced with other clients, the POL sites created remains accessible after creation. I'm thinking whether there are any configurations in the O365 Admin Portal that causes this setting to change automatically.
- Anil_kumar_AnakalaOct 20, 2021Copper ContributorAs you said the site is still visible in site collection. Actually I am also faced the same issue earlier. In SharePoint admin center, After creation of PWA site, I changed the primary admin and site owner. After 10 mins , then I faced this error.