Sp-dev-docs: Intermittent error: "Connection to SPO DS failed."

[YannickRe]

4682

Category

• [ ] Question
• [ ] Typo
• [X] Bug
• [ ] Additional article idea

This is basically a re-open of ticket #4682, which supposedly was fixed but we've seen the error again.
New tracelog information:

Message: Connection to SPO DS failed.
ServerErrorTraceCorrelationId: 47db099f-90f5-1000-c959-83250bca6159
ServerErrorCode: -1
Source: Microsoft.SharePoint.Client.Runtime
StackTrace:    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 Vooruitzicht.Provisioning.Core.SharePointWorker.CreateSite(CreateSiteRequest requestData, ConnectionSettings settings, ILogger log)
   at Vooruitzicht.Provisioning.AzureFunctions.Functions.CreateSite.<DoWorkAsync>d__2.MoveNext()

cc: @VesaJuvonen , @advdberg

Expected or Desired Behavior

We use SharePoint CSOM and PnP Core C# client side libraries to provision new site collection and configure them. I expect these calls to work.

Observed Behavior

Since a week or so, some of our calls fail sometimes with the error message "Connection to SPO DS failed". This may run for hours without a problem, then fail a couple of times and then start working again.

[msft-github-bot]

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

[VesaJuvonen]

Thx @YannickRe for reporting and we'll look into this right away. If anyone else is seeing similar issues, please do let us know, so that we can investigate the scale of this. Thanks for the additional information advance.

[advdberg]

@YannickRe Haven't seen this issue recently, but the customer which had these kind of issues hasn't been that active in creating new sites as they did before, so I assume that reduces the chance of getting the issue...

[rubenvw]

@VesaJuvonen
We currently experience the same issue. We are using a provisioning engine to provision multiple (communication) sites. Our client is at this moment actively creating new sites.

It fails even after ten retries.

[YannickRe]

@rubenvw thank you for replying, at least I'm not the only one experiencing this.

[advdberg]

@YannickRe @VesaJuvonen we have just re-opened the MS ticket (16467790) while we see the same issue appearing again this morning.

[advdberg]

@VesaJuvonen For what it's worth, an example of the correlation id
ServerErrorTraceCorrelationId: d82f0c9f-0069-1000-c959-89f2cd951ffc

Will also share this with MS support

[VesaJuvonen]

Thanks everyone for the updates. Feel free to share the correlation ID with me from a recent entry, which will help to see what's happening on the server side. Only information needed is the correlation ID - no need for other details.

Also - like seems to be already done, please re-open tickets with official channels as this is not really a dev issue as such... it's just visible in the API as there's a back end connectivity issues, which we need to absolutely fix.

[VesaJuvonen]

@rubenvw - please share the correlation ID which you are getting and happy to have a look on the issue. Thx.

[rubenvw]

Hi @VesaJuvonen , I am a colleague of @advdberg . You could the correlation ID he has mentioned.

[DaytaMOD]

I get this error in PowerShell unless I add the -Wait to the Add-PnPTenantSite command.

[YannickRe]

@VesaJuvonen any updates on this?

[advdberg]

@YannickRe @VesaJuvonen just got a call from MS support about the ticket we created. There's no support from them anymore on this while all teams who investigated the issue and the corresponding correlations ID's we provided were not able to provide more info or a fix for it.

We're advised to contact Dev support to help with the script/code. Not the anwer we hoped for though.

We end up in just retry-ing the New-PnPTenantSite cmdlet a couple of times untill the creation succeeds which will hopefully deal with this issue most of the occurances. It would be nicer if this issue is handled internally and retried without having to implement this retry when calling the API.

Maybe these retries should then be implemented in the PowerShell wrapper cmdlet?

[VesaJuvonen]

Just to follow up on this - anyone seeing this anymore or not? There should have been a fix applied on the farm level to fix this, so we should be good, but would like to get your input and confirmation on this.

[YannickRe]

We’re not seeing this anymore, but you can be sure I’ll reopen if it reoccurs 😉
Thank you for the follow up and the escalation, I’ll wait for some feedback from the others before I close it.

[YannickRe]

No one responded within a week, closing now.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues