search

pnp / PnP-PowerShell

SharePoint PnP PowerShell CmdLets
https://pnp.github.io/powershell
Other
987 stars 665 forks source link

Lcid parameter causes New-PnPSite to fail #2645

Closed teylyn closed 4 years ago

teylyn commented 4 years ago

Reporting an Issue or Missing Feature

error when using New-PnPSite with Lcid parameter

Expected behavior

New-PnPSite creates a site with Lcid 5129

Actual behavior

New-PnPSite fails to create the site

Steps to reproduce behavior

This has been reproduced on three different tenants.

New-PnPSite -Type TeamSite -Title "Foo Bar Test Three" -Alias "foobar3" -Wait:$false -Lcid 5129

This sits for about fifteen minutes, then returns the error:

New-PnPSite : OfficeDevPnP.Core.Sites.SiteCollection.CreateAsync: Could not create team site.
At line:1 char:1
+ New-PnPSite -Type TeamSite -Title "Foo Bar Test Three" -Alias "foobar ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [New-PnPSite], Exception
    + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.NewSite

The Office 365 group is created, but the site isn't.

Which version of the PnP-PowerShell Cmdlets are you using?

What is the version of the Cmdlet module you are running?

3.20.20

How did you install the PnP-PowerShell Cmdlets?

ghost commented 4 years ago

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

jackpoz commented 4 years ago

Hi @teylyn , it could be that only the LCID available in SharePoint Admin Center can be used in New-PnPSite , even if the LCID can be changed later on.

image

teylyn commented 4 years ago

Hi @jackpoz . Your screenshot shows the selection for the site language, i.e. if the user interface is using French or German or whatever. The site language cannot be changed later on. The LCID is about formats for dates etc., not the user interface language. The LCID can be changed at any time. If there is a parameter to set it at when the site is created, I see no reason why it should not work. If your suspicion is true, then the documentation needs to reflect that and list the LCIDs that CAN be used for the command.

KoenZomers commented 4 years ago

Valid point that this is confusing @teylyn. I have created a wiki page detailing all the supported locale IDs you can use at https://github.com/pnp/PnP-PowerShell/wiki/Supported-LCIDs-by-SharePoint and have updated all cmdlets which make use of LCIDs to point to this same wiki page. The June 2020 release taking place next Tuesday will contain the updated cmdlets containing the reference.