New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to create Communication site via PnP PowerShell #1542

Open
mag210 opened this Issue May 2, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@mag210

mag210 commented May 2, 2018

Reporting an Issue or Missing Feature

When trying to create a new communication site via PnP Powershell I receive an error noting that the site url is blank. I include the error below under actual behaviour. Note this always use to work and I have not changed any of my code. I include a code sample below. Interestingly, we have a dev tenancy and the same command ran against this tenancy does work as expected. The issue appears to be confined to our production tenancy: uob.sharepoint.com. However, to my knowledge nothing has changed which could results in this error. We have checked with multiple Global admin accounts on different machines and with services running on Azure. In all cases we get the below error when attempting to create sites in the Production tenancy. Has anyone come across this before?

-Max

Expected behavior

Communication site created and url returned.

Actual behavior

Following error:
New-PnPSite : {"d":{"Create":{"__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},"SiteStatus":3,"SiteUrl":""}}}

Steps to reproduce behavior

$title = "Sandpit site"
$descritpion = "test"
$classification = "Confidential"
$site_url = "https://uob.sharepoint.com/sites/uob-sandpit4"

$communicationSiteUrl = New-PnPSite -Type CommunicationSite -Title $title -Description $description -Url $site_url -Classification $classification -SiteDesign Topic

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

  • PnP PowerShell for SharePoint Online

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

2.24.18

How did you install the PnP-PowerShell Cmdlets?

  • Installed through the PowerShell Gallery with Install-Module
@FitzDbA

This comment has been minimized.

FitzDbA commented May 11, 2018

$descritpion = "test"
description is not well typed so it can´t be used?

@andreasblueher

This comment has been minimized.

andreasblueher commented Jun 12, 2018

Hey,
I'm running into the same SiteStatus 3 error message, when trying to use New-PnPSite. For me it happens during deploy.ps1 of sp-starter-kit. I've installed pnp PowerShell using the standalone installer.

@andreasblueher andreasblueher referenced this issue Jun 13, 2018

Open

New-PnPSite @hubParams fails #19

2 of 3 tasks complete
@andreasblueher

This comment has been minimized.

andreasblueher commented Jun 14, 2018

@mag210 can you confirm that this issue appeared for an url you have used before and deleted the site to recreate it? This seems to be related to it.

@mag210

This comment has been minimized.

mag210 commented Jun 27, 2018

Hi all, I raised this ticket with Microsoft Support and apparently the issue was down to a Microsoft problem which effected the creation of site collections on certain tenancies. This has now been resolved in my tenancy and my PnP provisioning engine is now working correctly.

@simonagren simonagren referenced this issue Dec 5, 2018

Closed

createCommunicationSite created bug #406

1 of 4 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment