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

Exception value can't be null #98

Open
WilliamZheng opened this issue Sep 11, 2020 · 13 comments
Open

Exception value can't be null #98

WilliamZheng opened this issue Sep 11, 2020 · 13 comments
Assignees

Comments

@WilliamZheng
Copy link

When I expand the a site collection node, it throw "Value cannot be null. Parameter name: key".

@sidper
Copy link

sidper commented Sep 14, 2020

Same issue. It worked until recently

@gszdev
Copy link

gszdev commented Sep 17, 2020

Hi @bramdejager,

I'm also faced with the same issue.
The issue is not reproducable for all my site collections. I think the issue only happens on "newer" site collections.

Steps to reproduce:

  • Create a new communication site
  • Add the new site to SPCB

Here are some details from the SPCB log:

Microsoft.SharePoint.Client.ServerException: Value cannot be null.
Parameter name: key
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()
at SPBrowser.Extentions.SiteExtentions.IsCurrentUserAdmin(Site site)
at SPBrowser.NodeLoader.LoadWeb(TreeNode parentNode, Web web, MainForm form)
at SPBrowser.NodeLoader.LoadSite(TreeNode parentNode, ClientContext ctx, Site site, MainForm form, List`1 subwebs)

I don't know wether you can do something.
Maybe some checking for NULL or RootWeb, CurrentUser, ... is initialized correctly may help.
Thx.

@imir-hoxha
Copy link

I am facing the same issue here.

@ismikhaylov
Copy link

Hi!
I have same issue, it works well two weeks ago

@bramdejager
Copy link
Owner

bramdejager commented Sep 18, 2020 via email

@patrikhellgren
Copy link

I'm also seeing the same issue. @bramdejager you might want to have a look at the issue reported over in pnp/sp-dev-docs to see if this is related: SharePoint/sp-dev-docs#6281
At least it is the same error message and seems to have started on the 9th of september so the timing is also the same.

@slavag
Copy link

slavag commented Sep 19, 2020

Same issue here, we see this in lot of our customers, not all , but many (thousands).
Started at Sep 9.

@bramdejager
Copy link
Owner

Checked a bunch of conditions, but I'm not able to track back any weird incorrect conditions. I have the same issue and error message on different tenants. But not all. Some tenants seem to work fine and don't cause any issues. I updated the CSOM to the latest version (August) but did not resolve the issue. I validated server/farm versions, but all were on version 16.0.20509.12005.

@jansenbe
Copy link

@bramdejager : I'm also seeing this issue and can reproduce with creating a private channel in Teams and then connecting to that site using SPCB. Doing a Fiddler trace showed the 4th CSOM call after connecting a site collection fails with a server error. I did pull the ULS logs for that error and noticed a server side JSON serialization issue (which clearly is a bug). Looking at the stacktrace in the ULS log the error seems to originate from loading the ThemeInfo property: can you try to exclude that property and see if it fixes things?

@jansenbe
Copy link

@bramdejager : internal thread started on this, will keep you all posted of the outcome

@bramdejager
Copy link
Owner

@jansenbe it lookes excluding the ThemeInfo object is solving the issue. I'll release an intermediate release as a workaround.

@phill29
Copy link

phill29 commented Sep 28, 2020

Any movement on this? Is _api/web/ThemeInfo expected to work again anytime soon?

@bramdejager
Copy link
Owner

Released a temporary release as a workaround, please see release SPCB v4.10.1. This release excludes the ThemeInfo object from loading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants