Fix Embedded PowerPoint Videos Not Playing When Exported via IIS
Question details
The user is trying to generate a video from a PowerPoint presentation containing embedded videos using Microsoft Office Interop on an IIS server, but the embedded videos fail to play in the output.

- Product
- Microsoft PowerPoint
- Device & OS
- not provided
- Scenario
- Automating the conversion of a PowerPoint presentation with embedded media into a video file via an IIS-hosted application.
- Observed behavior
- The video file is created successfully upon IIS deployment, but the embedded videos and animations do not play in the final output, despite working perfectly when run locally through Visual Studio.
Verify that your IIS server is correctly configured with the necessary MIME types for video files (such as .mp4 or .avi) and ensure you have administrative access to modify application pool identities.
Adjust IIS Application Pool Permissions and File Paths
Resolves access discrepancies between Visual Studio (which uses your local user account) and IIS (which uses a restricted system account).
When running Microsoft Office Interop via IIS, the application pool identity often lacks the necessary permissions to access the embedded media files or the temporary directories used by PowerPoint during video rendering. Visual Studio succeeds because it runs under your active user profile.
Press Win + R, type inetmgr, and press Enter to open the Internet Information Services (IIS) Manager.
In the Connections pane on the left side, click on Application Pools.
Right-click the application pool associated with your site and select Advanced Settings. Find the Identity property under the Process Model section.
Change the Identity to a Custom account and enter the credentials of a user with full file access permissions (e.g., the same account used in Visual Studio).
Ensure that all file paths referenced in your code for the PowerPoint file and its embedded media use absolute, accessible local drive or network paths rather than relative paths.

Migrate to Open XML SDK or Microsoft 365 APIs
Replaces the unsupported server-side Office Interop with robust, server-safe alternatives.
Create and Export Presentations Smoothly with WPS Office
If you are encountering complex permission issues and heavy system overhead with Microsoft Office on desktop or server environments, consider switching to WPS Office. It provides a lightweight, highly compatible suite for creating, editing, and exporting presentations reliably.
- 1. Open your Presentation: Launch WPS Presentation on your desktop and open your .pptx file containing the embedded videos.
- 2. Access Export Features: Navigate to the Tools tab located on the top ribbon and select Export to Video.
- 3. Generate the Video: Choose your desired video resolution and output directory, then click Export to generate a flawless video file.

Frequently Asked Questions
Why does Microsoft Office Interop work in Visual Studio but fail in IIS?
Visual Studio runs under your active desktop user account, which has full access to the interactive desktop environment and file system. IIS typically runs under a restricted service account (like ApplicationPoolIdentity) that lacks the necessary permissions and the interactive session required by Office Interop.
Can I safely use Office Interop for server-side automation?
No. Microsoft officially states that Office Interop is not supported for unattended server-side automation. Using it in environments like IIS can lead to scalability issues, memory leaks, security vulnerabilities, and process deadlocks.
What are the best alternatives to Office Interop for generating files on a server?
For server-side document generation, it is highly recommended to use the Open XML SDK, Microsoft Graph APIs, or specialized third-party libraries designed explicitly for unattended server environments.
How do I ensure IIS has access to my PowerPoint media files?
You must grant explicit Read and Write permissions for the folder containing your media files to the identity account running your IIS Application Pool. Additionally, ensure your application code uses absolute file paths rather than relative ones.




