This post was most recently updated on February 10th, 2019.< 1 min read.
There’s maybe a thousand things that can throw an “Microsoft.SharePoint.Client.ServerException”, but a bit smaller amount of things, that are ambiguous enough to be called “Unknown error”. This post describes one, fairly usual fix for this issue!
But let’s get back to the beginning for a second – you get what and when now?
When running any code, that provisions new sites (much like https://www.koskila.net/new-pnpsite-fails-with-sitestatus3/), you get an error like this almost immediately:
Microsoft.SharePoint.Client.ServerException: Unknown Error at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream) at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse() at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServer(ChunkStringBuilder sb) at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery() at ...
What to do?
Solution to “Unknown error”
Okay – this sounds bold. Let’s find a silver-bullet solution to unknown errors, right?
You might be in luck, though – in my experience, most of the times you get this error while provisioning new sites, this is actually just yet another example of the URL being already reserved for a deleted site. And that’s usually easy to fix!
This one’s fairly straightforward to fix. You’ll just have to make sure to either use another URL for your new site, or remove the existing (but deleted) site from the recycle bin.
I’ve written about the topic before, so I’ll just be citing myself. You can check this page below out for instructions on how to fix this issue!
- How to fix a Logic App deployment that failed with error “ApiNotFound”? - April 22, 2021
- Experiment: DateTime formats - April 21, 2021
- How to fix “LinkedAuthorizationFailed” when deploying an Azure Logic App? - April 15, 2021