"Unknown Render Failure" for Read Access in SharePoint Large Document Library

Question

We are encountering an issue in our SharePoint site when attempting to share a folder from a document library with a user assigned read access. The user receives the following error message:

"Unknown render failure. This item isn't available. It might have been moved, renamed, deleted, or you don't have access. Contact the owner for more information."

We observed that the document library contains approximately 154,888 items, which exceeds the 5,000-item threshold limit. Interestingly, the issue occurs only when the user has read permissions. When higher permission levels such as Edit, Contribute, Design, Restricted View, or Full Control are granted, the folder is accessible without any errors.

For read they have following permissions in it.
List permission: view application pages
Site permission: use self service site creation, view pages, browse user information, use remote interfaces, use client integration features, open

Error screenshot:

When we change the library view to classic experience, it is loading without any error but there is no files are showing in the folders.

Answer 1

Hello Selvakumar K

Based on my research, the issue you are experiencing may be related to the size of the document library exceeding the SharePoint List View Threshold limit (approximately 5,000 items).

When a list or library view attempts to retrieve more than 5,000 items in a single query, SharePoint may apply system‑level query throttling in order to maintain overall service performance. As a result, certain operations - particularly those involving Read‑only access where item‑level permission evaluation is required - may fail to render content properly and display errors such as: Unknown render failure. This item isn't available. You may refer to the official Microsoft documentation here: List View Threshold for large lists and libraries Additionally, optimizing large libraries by using indexed columns and filtered views may help SharePoint retrieve a smaller subset of data rather than querying all items at once, which can improve performance and reduce the likelihood of rendering issues when working with large libraries.

I found the following article that may be helpful in mitigating this behavior by creating indexed columns: Indexing columns in lists/ libraries – how to avoid "unknown render failure"

Note: This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

Hope this information is helpful. If you have any further questions, please feel free to let me know.

---

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.

Answer 2

The behavior is caused by SharePoint limits being exceeded in a very large library and by how permissions and sharing work at scale, especially for low‑privilege (Read) users.

Key points from the scenario and limits in the documentation:

1. The library has ~154,888 items.
2. SharePoint has practical and supported limits for large lists/libraries and for unique permissions:
   • When a folder, library, or list contains more than 100,000 items, permission inheritance cannot be broken or re‑inherited at that level.
   • A list or library supports up to 50,000 items with unique permissions, with 5,000 as the recommended general limit for performance.
3. There is also a limit of 50,000 items that can be shared in a folder or any subfolders.

In large libraries that approach or exceed these limits, operations that depend on evaluating item‑level security for low‑privilege users (such as Read) can fail in the modern experience, resulting in generic errors like “Unknown render failure” or empty views, while higher‑privilege users (Contribute/Edit and above) can still render the view because they bypass some of the fine‑grained checks.

To mitigate and resolve the issue, use the supported patterns for large libraries and permissions:

1. Reduce items in the affected folder/library
   • If the folder or its parent library contains more than 100,000 items, move items into additional libraries or sub‑libraries so that no single library or folder exceeds this boundary.
   • Keep the number of items that are shared within a single folder (including subfolders) under 50,000.
2. Reduce unique permissions
   • If the library is using extensive item‑level or folder‑level unique permissions, redesign so that:
     • The total number of uniquely permissioned items stays well below the supported 50,000 limit, and ideally below the recommended 5,000.
     • Permissions are applied at higher levels (site, library, or a small number of top‑level folders) instead of many individual items.
   • Where possible, re‑inherit permissions on items/folders that do not need unique access.
3. Restructure content for large‑scale read access
   • For scenarios where many users need Read access to a subset of content in a very large library, consider:
     • Creating separate libraries for different audiences or business areas.
     • Moving heavily shared folders into their own libraries with fewer total items and simpler permissions.
4. Validate sharing and access patterns
   • Ensure that the folder being shared does not exceed the “items that can be shared in a folder or any subfolders” limit (50,000 items). If it does, move some items out or share individual files instead.

Once the number of items and unique permissions is brought back within the documented limits, Read‑only users should be able to access the folder in the modern experience without the “Unknown render failure” error, and items should appear correctly in both modern and classic views.

---

References:

• "You can't share this folder because there are too many items in the folder" error when trying to share or break inheritance
• "Unable to reach the server" error when sharing files or folders in SharePoint or OneDrive