SharePoint Document Library in Teams - Cannot have two HTML5 backends at the same time.

Shane Gibeault 16 Reputation points
2022-10-04T13:45:21.72+00:00

My entire company recently started having issues viewing previously established SharePoint document libraries form within teams. When we try to view a document library in teams we receive the error message below stating "Something went wrong Cannot have two HTML5 backends at the same time."

We had originally added it into the teams channel as a "SharePoint Document Library", but we didn't like that it sorted folders by edit date instead of alphabetically.

Document Library View
247385-a11-documentlibrary.jpg

So I removed it from Teams and re-added it as a "Sharepoint Site". I have each departments Document library setup in their team this way. Plus it worked as we wanted, while sorting alphabetically.

SharePoint Site View (Alphabetical)
247398-a11-sharepointsite.jpg

Nothing has changed since then. Last week it just started generating the error message below for all users. If we click "Retry" it automatically comes back up, but it's a pain to have to "Retry" every time a user switches channels/chats and comes back to that error again.

We don't have any Webparts added to our SharePoint site. We solely have a site setup for each department and they only use the document library function. We don't use it for team sites, company communications, etc. I say that because I saw another user had this issue, but republishing the unpublished web part seemed to help them. I checked (Just in case) but we don't have anything unpublished or any webparts other than the document library.

I appreciate any help or similar experiences you may have had.

247357-a11.jpg

Microsoft 365 and Office | SharePoint Server | For business
Microsoft 365 and Office | SharePoint | For business | Windows
Microsoft Teams | Microsoft Teams for business | Other
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Saskia van de Ven 11 Reputation points
    2022-10-17T08:43:26.757+00:00

    We are facing the exact same issue. Did anyone find a solution for it yet?

    2 people found this answer helpful.
    0 comments No comments

  2. Andy 6 Reputation points
    2022-10-19T18:41:23.297+00:00

    I may have fixed it... If you click the drop down for the Document Library in Teams, and then go to Settings, Add Content--> Document Libraries and then select the Document Library in question. Let me know if this works for anyone else, otherwise I'll keep using it this way and see if it sticks.

    1 person found this answer helpful.

  3. Xuyan Ding - MSFT 7,601 Reputation points
    2022-10-05T05:55:41.147+00:00

    Hi @Shane Gibeault ,

    I tried to reproduce your problem in a test environment without success. I suggest opening a ticket for more direct help and asking Microsoft engineers to do more in-depth research.
    Microsoft 365 admin center: Support->New service request
    247721-image.png


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  4. Shane Gibeault 16 Reputation points
    2022-10-05T12:20:58.883+00:00

    Hi @Xuyan Ding - MSFT

    I figured that would be the case, but thought I'd check. Unfortunately we have a CSP so it takes a week of them guessing until they finally escalate it to Microsoft so we can get some real support.

    Thank you very much for trying though, I do appreciate that!

    0 comments No comments

  5. Zac Osburn 1 Reputation point
    2022-10-06T16:35:52.267+00:00

    My team's Team channels have been experiencing this exact issue for about 1-2 weeks now using the same functionality originally described (adding a tab as a SP site instead of Library).

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.