Troubleshooting
Problem
Users may encounter issues opening files (Word, Excel, PDF, images, ZIP files, etc.) within Viva Engage communities or storyline posts. These problems commonly arise due to SharePoint authentication, browser conflicts, device‑specific limitations, or viewer compatibility issues.
Symptom
1. Files Visible in Mobile App but Not on Desktop/Web
- Windows desktop browsers (Edge/Chrome) often show blank file areas or fail to load attachments.
2. Blank File List When Opening a Community
- The Files tab appears empty, often related to authentication mismatches or stale cookies.
3. PDFs Not Opening
- PDFs work on Windows and iPhone but fail on Android with errors such as:
“An error has occurred, please try again in a little while.”
4. Files Do Not Respond When Clicked
- Clicking a file does nothing—common with PDFs in Engage UI.
Environment
Viva Engage
Diagnosing The Problem
Understanding where files are stored is essential for diagnosing access issues.
Note: Understanding where files are stored is essential for diagnosing access issues.
- Viva Engage does not store attachments directly.
- Community post files are stored in the SharePoint document library backing the community.
- Storyline attachments are stored in a hidden OneDrive library belonging to the post creator.
- Classic Yammer communities may use Yammer‑labeled folders in SharePoint.
Step 1 — Test Browser Authentication and Cache
Many desktop issues stem from browser authentication failures with SharePoint.
Actions
- Open Viva Engage in InPrivate/Incognito Mode.
- Helps especially with PDF preview issues and blank file areas.
- Helps especially with PDF preview issues and blank file areas.
- Clear browser cache/cookies.
- Sign out of Microsoft 365 → close browser → sign back in.
- Try a different browser (Edge ↔ Chrome).
Step 2 — Validate SharePoint Permissions and File Access
Since Viva Engage depends on SharePoint, permissions must be verified.
Actions
- Go to: Community → Files tab → Open in SharePoint
- Navigate to: Document Library → Apps → Viva Engage
- Attempt to open the file directly from SharePoint.
If the file opens in SharePoint but not in Viva Engage, the issue is UI-related, not permission-related.
Step 3 — Device-Specific Diagnostics
Windows (Desktop Browsers)
- Windows browsers are disproportionately affected by file visibility issues.
- Disable corporate VPN/proxy temporarily.
- Test from a non‑corporate network.
Android (Mobile)
- Known bug: PDFs cannot open on Android even though they work on PC/iPhone.
Workarounds:
- Open the file through Microsoft Teams instead.
- Access Engage via browser rather than the mobile app.
Step 4 — Check File-Type Behavior
PDF Files
- In SharePoint, select
Open in Browser or Open in Adobe
This bypasses Engage viewer issues.
Office Files (Word/Excel/PowerPoint)
- Confirm that user has at least View permissions in SharePoint.
- Try downloading the file—if it downloads but won't preview, the issue is viewer‑specific.
Step 5 — Identify the Community Type
If you are working with a legacy Yammer community, SharePoint uses Yammer-named folders, which may cause confusion with permissions or client-side caching.
Step 6 — Test Viva Engage Through Microsoft Teams
Teams often bypasses the authentication issue present in browsers.
Actions
- Open Teams → Viva Engage
- Navigate to the same community/post
- Attempt to open the file again
If it works in Teams but not the browser → browser session is the root cause.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
23 January 2026
UID
ibm17257091