When installing SP 2016, no custom managed paths are actually created. The console output shows no error. But when a site collection, which requires a certain managed path to exist, is created, this obviously fails.
I couldn't figure out why the paths are not created. Running the same command manually works.
Also apparently restarting AutoSPInstaller works.
I also noticed, New-SPManagedPath is executed a second time with the -HostHeader switch. This doesn't work because you can't have both a HNSC and non-HNSC managed path with the same name. It's one or the other.
```
New-SPManagedPath -RelativeUrl $managedPath.RelativeUrl -WebApplication $url -Explicit -ErrorAction SilentlyContinue | Out-Null
# Let's create it for host-named site collections too, in case we have any
New-SPManagedPath -RelativeUrl $managedPath.RelativeUrl -HostHeader -Explicit -ErrorAction SilentlyContinue | Out-Null
```
Comments: ** Comment from web user: brianlala **
I couldn't figure out why the paths are not created. Running the same command manually works.
Also apparently restarting AutoSPInstaller works.
I also noticed, New-SPManagedPath is executed a second time with the -HostHeader switch. This doesn't work because you can't have both a HNSC and non-HNSC managed path with the same name. It's one or the other.
```
New-SPManagedPath -RelativeUrl $managedPath.RelativeUrl -WebApplication $url -Explicit -ErrorAction SilentlyContinue | Out-Null
# Let's create it for host-named site collections too, in case we have any
New-SPManagedPath -RelativeUrl $managedPath.RelativeUrl -HostHeader -Explicit -ErrorAction SilentlyContinue | Out-Null
```
Comments: ** Comment from web user: brianlala **
Can you confirm that this is still happening for you? I've created a bunch of farms myself in the last few days with custom managed paths, no issues. Maybe you can share the relevant lines of your input XML, too.
Brian