Skip to content
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

[BUG] Error in Get-PnPContainer : "The attempted operation is prohibited because it exceeds the list view threshold" #3970

Closed
MSFT-klpinhac opened this issue May 23, 2024 · 9 comments · Fixed by #3990
Labels
bug Something isn't working

Comments

@MSFT-klpinhac
Copy link

Reporting an Issue or Missing Feature

while the cmdlet Get-PnPContainer works fine in most tenants, the attempt to retrieve the Loop-Workspaces in a large tenant has returned the error "The attempted operation is prohibited because it exceeds the list view threshold"
error_get-pnpcontainer

Expected behavior

I would expect a list of containers / Loop Workspaces to be returned, no matter how large or small the tenant

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

PnP.PowerShell 2.4.0
image

Which operating system/environment are you running PnP PowerShell on?

  • Windows / PowerShell 7.4.2
    image
@MSFT-klpinhac MSFT-klpinhac added the bug Something isn't working label May 23, 2024
@reshmee011
Copy link
Contributor

@MSFT-klpinhac , can you please try get-spocontainer using SharePoint Online PowerShell to see if you get the same behaviour? I am unable to test your scenario as I don't have so many Loop workspaces on my environment.

@MSFT-klpinhac
Copy link
Author

yes, Get-SPOContainer using SharePoint Online PowerShell returns the same error
get-spocontainer

@reshmee011
Copy link
Contributor

@MSFT-klpinhac : Thanks for testing with SPO PowerShell, there is a parameter -Paged which you can use to return the pagingtoken which you can use to return the next batch, give it a try and let me know. The same would work for the Get-PnPContainer -OwningApplicationId a187e399-0c36-4b98-8f04-1edc167a0996 -Paged .

@gautamdsheth
Copy link
Collaborator

@MSFT-klpinhac - as mentioned above, please use the approach @reshmee011 mentioned above which should work with large tenants.

@MSFT-klpinhac
Copy link
Author

MSFT-klpinhac commented May 31, 2024

The cmdlet Get-PnPContainer used with parameter "-Paged" does return the same error:
image

The cmdlet Get-SPOContainer used with parameter "-Paged" is returning the same error as well:
image

How can i retrieve a PagingToken (i.e the Token String), so that i can use it with parameter "-PagingToken" of the cmdlets used above ?

@gautamdsheth
Copy link
Collaborator

@reshmee011 @MSFT-klpinhac - have updated the cmdlet , it will now return the pagination token as well if -Paged is specified. Will be available in tomorrow's nightly build as well as the next major release whenever we do that .

Please let us know how it works you now with this update/fix.

@MSFT-klpinhac
Copy link
Author

that nightly build is returning another error:
image (1)

@reshmee011
Copy link
Contributor

@MSFT-klpinhac : can you please a microsoft case for microsoft to look into the issue using -Paged parameter with cmdlet Get-SPOContainer returning the error exceeding list view threshold. Most like if the underlying endpoint is fixed by Microsoft, PnP PowerShell cmdlet will work too as they call the same endpoint in the background.
Unfortunately I don't have a proper set up to test the issues you are facing. Out of curiosity , how many Loop workspaces you have in total?

@MSFT-klpinhac
Copy link
Author

Support case has been created, @reshmee011
How many Loop workspaces are in that tenant is unknown - apparently more then 5000 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants