SharePoint Support Hub

SharePoint Support Hub: Troubleshooting and Expert Help

This SharePoint support hub covers the most common enterprise SharePoint problems — permissions errors, migration failures, SPFx issues, search problems, and sync failures — with specific troubleshooting steps and resolution guidance. For issues that need expert intervention, EPC Group provides emergency SharePoint support with same-day response for critical production issues.

Key facts

• EPC Group provides 24/7 emergency SharePoint support — call (888) 381-9725 for critical production issues.
• Most common SharePoint issues: permissions errors, 5,000-item threshold, search indexing delays, sync failures, migration blockers.
• The 5,000-item list view threshold is the #1 SharePoint performance complaint — fix it by indexing columns used in filters.
• Migration failures most often caused by: API throttling, unsupported file names, missing pre-migration assessment.
• EPC Group: 29 years Microsoft consulting, 6,500+ SharePoint implementations.

Permissions Errors

Permissions errors are the most common SharePoint help desk ticket category. Here are the most frequent causes and fixes.

"Access Denied" on a SharePoint site

• Check whether the user's Azure AD account is in the correct security group for the site.
• Check whether the site has unique permissions (broken inheritance) — the user may have access to the parent hub but not the spoke site.
• Check whether a sensitivity label or conditional access policy is blocking access (e.g., requires managed device).
• Check whether the user is an external guest — guest access must be explicitly enabled at the site level.

"You need permission to access this item"

• The item has item-level permissions set differently from the library — check "Manage access" on the specific item.
• The user accessed a direct link to a file and does not have library-level access — grant library access, not just item access.
• External sharing links may have expired — regenerate the sharing link with an updated expiration date.

5,000-Item List View Threshold

The list view threshold error occurs when a SharePoint view tries to display or filter more than 5,000 items at once. Here are five ways to fix it.

1. Index filter columns — create indexed columns for every column used in filters and sorts. Do this first — it resolves most threshold errors.
2. Add a view filter — modify the default view to filter items below 5,000 using an indexed column (e.g., Status = "Open").
3. Use metadata navigation — enable the metadata navigation feature to let users drill down without loading all items at once.
4. Restructure large lists — split large lists into multiple lists by year, department, or status category.
5. Migrate to Dataverse — for extreme cases (100K+ items), move the data to Dataverse for better query performance and filtering.

Migration Failures

The top five causes of SharePoint migration failures — and how to prevent each one.

1. API throttling — running too many concurrent migration jobs hits Microsoft's throttling limits. Fix: reduce concurrent threads in your migration tool settings.
2. Unsupported file names — files containing # % & * : < > ? / \ | cause migration failures. Fix: scan and rename before migration using the SharePoint Migration Assessment Tool.
3. Path length exceeded — file paths exceeding 400 characters fail to migrate. Fix: shorten folder or file names; flatten deep folder hierarchies before migration.
4. Large files without chunked upload — files over 250 MB require chunked upload configuration in the migration tool. Fix: configure chunked upload in ShareGate or AvePoint before starting.
5. Missing pre-migration assessment — custom solutions, workflows, and InfoPath forms that were not identified before migration require remediation during migration — causing delays. Fix: run SMAT and assess all customizations before starting.

SPFx and Custom Development Issues

SPFx web part not loading

• Check browser console for CORS errors — the Azure AD app registration may be missing a required permission scope.
• Check the SPFx package version against the SharePoint Online target API — older SPFx versions lose support over time.
• Verify the solution is deployed to the App Catalog and approved — unapproved apps do not load.
• Check Content Security Policy (CSP) violations — SharePoint Online's CSP may be blocking external script sources.

Power Automate flow not triggering on SharePoint changes

• Verify the trigger is set to the correct list or library — a common error is the flow pointing to a different site collection.
• Check the flow owner's SharePoint permissions — the flow runs in the context of the connection owner.
• Check throttling in the flow run history — high-volume lists may trigger Microsoft's Power Automate throttling.
• Check whether the flow was disabled due to connector authentication expiry — re-authenticate the SharePoint connection.

Search Issues

Documents not appearing in SharePoint search

• Newly uploaded documents take 4–24 hours to be indexed — wait and retry.
• If still not appearing after 24 hours: check the library settings → "Re-index document library" to force a crawl.
• Check whether the library is excluded from search — go to Library Settings → Advanced Settings → "Allow items from this document library to appear in search results."
• Check whether the user has read permissions on the document — search only returns results the querying user has access to.

Custom metadata not showing in search results

• Custom columns must be mapped to managed properties in the SharePoint Admin Center search schema.
• After mapping, trigger a full recrawl — metadata does not appear in results until the crawl completes.
• Managed properties must be set as "Queryable" and "Refinable" to appear in search filters.

OneDrive Sync Failures

• Files with unsupported characters (# % * : < > ? / \ | and others) cannot sync — rename the files.
• File path too long — SharePoint enforces a 400-character URL limit. Shorten folder or file names.
• Sync client out of date — update to the latest OneDrive build. Many sync errors are fixed in recent releases.
• Library exceeding 300,000 files — OneDrive sync degrades significantly above this limit. Split the library.
• Conditional access blocking sync — check whether your Intune device compliance policy requires managed devices for SharePoint access.

When to Call EPC Group for SharePoint Support

Hire external SharePoint consultants when these conditions apply.

1. Issues have persisted more than 2 weeks without resolution despite internal troubleshooting.
2. The problem involves cross-tenant migration, hybrid configuration, or complex identity federation.
3. Compliance requirements (HIPAA, FedRAMP, ITAR) demand certified expertise and documented resolution.
4. A migration deadline is at risk and internal teams lack bandwidth.
5. Custom SPFx development exceeds internal developer capabilities.
6. Governance gaps are causing recurring issues that keep returning after point fixes.

Frequently Asked Questions

How do I fix the SharePoint list view threshold error?

Index the columns used in your list filters and sorts. Then modify the default view to add a filter that limits visible items below 5,000. For libraries with millions of items, enable metadata navigation or split the library into smaller libraries organized by year or category.

Why is my SharePoint migration failing?

The most common causes are: API throttling (reduce concurrent migration threads), unsupported file names (scan and rename first), path lengths over 400 characters (shorten folder names), large files without chunked upload (configure chunked upload in your tool), and missing pre-migration assessment (run SMAT before starting). Fix the root cause before retrying migration.

How long does SharePoint search indexing take?

Newly uploaded documents appear in search within 4–24 hours under normal conditions. Large libraries or full recrawls can take up to 48 hours. If documents do not appear after 24 hours, check whether the library is set to appear in search results and trigger a manual re-index from the library settings.

Get Emergency SharePoint Support

For critical production issues, call EPC Group at (888) 381-9725. For non-urgent support, submit a support request and receive a response within 4 business hours.