Forum Discussion
Unable to create a connected SharePoint site
- Oct 28, 2021
Paul_Mather thank you for responding! We found out that the subsite creation settings in SharePoint tenant settings where set to "Subsite creation is disabled for all sites". It occurred to me to check that only later as creating a new project did create a site without any issues. We have to request the SharePoint admins to address that.
To answer your questions Paul, yes it is a manual migration and there are 3 EPTs, so its custom and they all are set to automatically create a site on next publish. If you don't mind Paul, can you help me understand why it was ok to create a new project with a project site inspite of the SP setting for subsites being disabled? Thank you for your time!
Hello jenyalex ,
How are you doing the migration manually, just saving the Projects from Project Server 2013 as an MPP file then opening that MPP file while connected to Project Online then saving and publishing it to Project Online? Is the default EPT site creation set to "Automatically create a site on next publish" ? What is the error that is thrown? When creating a new blank project from Project Desktop, does that create a Project Site?
Paul
- jenyalexOct 28, 2021Copper Contributor
Paul_Mather thank you for responding! We found out that the subsite creation settings in SharePoint tenant settings where set to "Subsite creation is disabled for all sites". It occurred to me to check that only later as creating a new project did create a site without any issues. We have to request the SharePoint admins to address that.
To answer your questions Paul, yes it is a manual migration and there are 3 EPTs, so its custom and they all are set to automatically create a site on next publish. If you don't mind Paul, can you help me understand why it was ok to create a new project with a project site inspite of the SP setting for subsites being disabled? Thank you for your time!
- Paul_MatherOct 28, 2021MVP
jenyalex I'm not sure why PWA can bypass that setting but once the SharePoint admins have updated it, the issue should be resolved.
Paul
- jenyalexOct 28, 2021Copper ContributorThank you & appreciate it Paul!