Error when activating the "SharePoint Server Publishing Infrastructure" site collection feature inside my online team site collection

Question

i am working on an office 365 project. and i have created a new team site collection. but when i tried to activate the "SharePoint Server Publishing Infrastructure" site collection feature , i got the following error, after waiting for a couple of minutes:-

now i checked if the feature has been activated or not, and i can see that it is activated as follow:-

also inside my site collection, i have noted that new libraries have been created, where these libraries are created as part of activating the publishing site collection feature. but now i am not sure what does the above error indicate? should i remove the site collection, and create a new one? as i do not want to start working on my new site collection while it have hidden errors or problems, since i got the above error while trying to activate the publishing feature?

Answer 1

If your site is still empty, personally I'd recreate it after such an error, just to feel 100% safe.

It's hard to tell if any Feature Activation steps were missed / incomplete due to the error you got. Since SharePoint tells you the Feature is "Active" now everything should be OK. The error might have happened while reloading the Features page after pressing pressing the "Activate" button while everything else went just fine.

Answer 2

We had faced the same issue multiple times and this was the check list that we used:

1) Deactivate and Reactivate this feature.

2) If there was error in the first step, recreate the site collection and then attempt to activate the feature again.

3) If the error still persists, then open a ticket with Microsoft support. It usually means, there is something wrong with the tenant

Answer 3

Is this a modern Communications Site? If so, SharePoint Server Publishing cannot be activated, which also means cannot create Enterprise Search subsite which requires this functionality. Cannot find a hack or workaround. Check back in 2030, might be resolved by then...