New Document List '|0' does not exist at site with URL '|1'.

[Stefaan De Vreese]

When trying to create a new document, from a custom content type (which has a template), starting from the Documents Webpart, Sharepoint opens the following link:

https://tenant.sharepoint.com/sites/100000042/_layouts/15/CreateNewDocument.aspx?id=https%3A%2F%2Fte...

this throws an error:

Error: List '|0' does not exist at site with URL '|1'.

But the list does exist and the dotx is in this list. So why do we get this error? and how to fix this?

If we try to do the same, but from within the document library, another link is generated by sharepoint:

ms-word:nft|u|https://tenant.sharepoint.com/sites/100000042/SiteAssets/Template_ESC_Change_Request.dotx|s|https://... documenten

and this works like a charm...

So why the difference? and how to solve the error?

[#2]

I guess you are using both the modern document library WebPart and the modern UI for document libraries so the error seems to be in the modern document library WebPart. Adding @Lincoln DeMaris

[#3]

That is correct, this error happens when using the modern Doc Library Webpart.

[#4]

Has anyone found a solution? Or is this a known bug in the new Document Library webpart in SharePoint Online? I am encountering the same exact issue when attempting to create a new document from the webpart.

[#5]

Getting the same error here.  Also noticing that several functions for the document library do not work in the Web Part but do in the App Web Part like Move To, Save To, Version History, Preview, Flow, Workflow, Compliance Details, and File Details.

[#6]

Found this URL that says the 'Documents' Library is missing and to create a new one or restore the old one.

https://support.office.com/en-gb/article/-list-0-does-not-exist-at-site-with-url-1-error-when-you-tr...

Didn't work for me.

My situation is that we are converting our Classic Site Collection to a Modern experience.  If I use a classic page with the web part to the Document Library it all works fine.

[#7]

Solved it for me by switching the Default open behavior for browser-enabled documents: setting under Advanced Settings to use the Default which in this case is the Browser client.

Working now.