Replies

This is especially bad for Outlook, where it's operation is tightly coupled with "current user's profile" of the user running Outlook, and usually the web application runs under NetworkService/Application Identity context, so it'd create security
complications (it's possible to adjust the security settings to allow it to run, but also note that Outlook can execute binaries so it's general a bad idea).

As cheong said, Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because
Office may exhibit unstable behavior and/or deadlock when Office is run in this environment. For more information, please visit
Considerations for server-side Automation of Office:

In addition to these issues, one of the following common errors may occur when you try to automate Office server-side:

The CreateObject function and the CoCreateInstance function return one of the following run-time error messages and cannot be started for Automation.