Script halted when creating root site collection in SP2019

[alisterlouis]

When installing SP2019 single server the script is failing when creating site collection. This does not occur with SP2016.

Creating Site Collection "http://"

Script halted! Exception Microsoft. SharePoint. SPException: Provisioning did not succeed. Details: The site template was not provisioned successfully. Delete this site collection in Central Administration, and then create a new site collection. OriginalException: Provisioning did not succeed. Details: Failed to create the 'Cache Profiles' list. OriginalException: Invalid field name. {d8f18167-7cff-4c4e-bdbe-e7bØfØ1678f3} /Cache Profiles

[enriccarrion]

Hi! The same happened to me. I tried to created manually a Publishing Portal from Central Admin, which finished successfully. Then I launched AutoSPInstaller again and this time it could complete the site collection creation without problems.

[UmrG]

Another way to resolve this is reboot machine and restart script if you don't want to create manually.

[chheim]

I just faced this issue on a new SharePoint 2019 Installation on Windows Server 2019 Std. It was not possible to create a Publishing Portal. I can confirm that rebooting the server is resolving the issue.

Error message for me, before rebooting (using a german webtemplate) was:

Exception: Microsoft.SharePoint.SPException: Fehler bei der Bereitstellung. Details: 'Die Websitevorlage wurde nicht erfolgreich bereitgestellt. Löschen Sie diese Websitesammlung in der Zentraladministration, und erstellen Sie dann eine neue Websitesammlung.' 

OriginalException: 'Fehler bei der Bereitstellung. Details: 'Fehler beim Erstellen der Liste 'Cacheprofile'.' OriginalException: 'Ungültiger Feldname. {d8f18167-7cff-4c4e-bdbe-e7b0f01678f3}  /Cache Profiles'.'. ---> Microsoft.SharePoint.SPException: Fehler bei der Bereitstellung. Details: 'Fehler beim Erstellen der Liste 'Cacheprofile'.' OriginalException: 'Ungültiger Feldname. {d8f18167-7cff-4c4e-bdbe-e7b0f01678f3}  /Cache Profiles'. --->

[jn-bedag]

Had the same problem with a SharePoint 2016 installation. In my case I just restarted the script, no reboot needed.

Debugging: I tried to restart all possible services before New-SPSite (with pause in the script), nothing worked. I tried to wait for a long time, but it's not a timing issue. The problem also occurs if you just start the script again in the same PowerShell window. But, if you restart the script (close PowerShell and open a new one), the error does not appear. Further, if you restart the script just after New-SPConfigurationDatabase the error does not appear. If you restart the script before, the error appears. It seems as PowerShell does cache something, which has a bad impact on the New-SPSite. But New-SPSite does not use a previous variable or so, created by New-SPConfigurationDatabase. This is very awkward, I have no idea what PowerShell or SharePoint is doing here. Couldn't figure it out. Just stick to the workaround. It should only be a problem in some new installations. In my forked project I added some simple error handling.