How to Fix a SharePoint App Not Working on Specific Sites
Question details
The user needs to troubleshoot a SharePoint application that functions properly on some sites but fails to load, execute, or display correctly on specific sites.
- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Attempting to use a custom or third-party SharePoint application across multiple sites within the same tenant.
- Observed behavior
- The SharePoint app fails to run on specific sites, often due to blocked scripts, Content Security Policy (CSP) restrictions, or hidden permission errors.
Ensure you have Site Collection Administrator privileges for the affected SharePoint site and access to your web browser's developer tools.
Check Browser Console and Content Security Policy
Use this method to identify if required app scripts are being blocked by the browser or the site's Content Security Policy settings.
SharePoint apps often rely on external scripts and resources. If a specific site has strict Content Security Policy (CSP) configurations, it may actively block these resources, preventing the app from working.
Navigate to the affected SharePoint site in your web browser. Press F12 or right-click the page and select 'Inspect' to open the Developer Tools panel.
Click on the 'Console' tab and look for red error messages. Pay special attention to errors mentioning 'Content Security Policy' or 'Failed to load resource'.
Switch to the 'Network' tab, refresh the page, and check if any scripts related to the SharePoint app are showing a 403 Forbidden or blocked status.
If you identify blocked domains, an administrator must update the site's Content Security Policy in the SharePoint admin center to permit the app's required resource URLs.
Verify Site Permissions and App Catalog Settings
Ensure the specific site has the correct permissions, app catalog configurations, and activated features to support the app.
Open a Microsoft Support Ticket
If local troubleshooting fails to resolve the app issue, contact Microsoft Support to investigate potential backend tenant or synchronization problems.
Looking for a Seamless Office Experience? Try WPS Office
While resolving complex SharePoint backend and permission issues can be tedious, your daily document management shouldn't be. WPS Office provides a free, lightweight, and powerful alternative to Microsoft Office, allowing you to easily view, edit, and collaborate on documents without complex administrative setups.
- 1. Download the Software: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install WPS Office: Run the downloaded installation file and follow the simple on-screen instructions to set up the software.
- 3. Open Your Files: Launch WPS Office and seamlessly open your existing Microsoft Office files with perfect formatting preservation.
Frequently Asked Questions
Why does my SharePoint app work perfectly on one site but fail on another?
This discrepancy is usually caused by site-specific configurations. The failing site might have stricter Content Security Policy (CSP) settings, missing site features, custom scripting restrictions, or distinct permission levels that prevent the app from executing.
How do I check if scripts are being blocked in my SharePoint environment?
You can check for blocked scripts by opening the affected SharePoint page, pressing F12 to open your browser's Developer Tools, and navigating to the 'Console' tab. Look for red error texts indicating blocked resources or CSP violations.
Can a tenant-level backend issue affect only a few specific SharePoint sites?
Yes. Backend tenant-level synchronization issues, partial app catalog corruptions, or delayed propagation of permissions can sometimes manifest selectively, causing an app to fail on a few isolated sites while working elsewhere.
What information should I gather before opening a Microsoft support ticket for SharePoint?
Collect the exact URLs of both the working and non-working sites, the specific name and version of the app, screenshots of any browser console errors, and any correlation IDs that SharePoint displays when the app fails to load.
