This example shows how to make Microsoft Word ready for server
use. The other office products can also be configured just the same
All you need to do here is to make sure that there is no pop-up dialogs from Office products during PDF conversion.
Note: If you have previously modified Microsoft Word setting through Distributed COM Configuration Properties, you need to set it back to the orignal setting (especially in the Identity tab, it must be set to The launching user) . If you are not sure, we recommend re-installing Microsoft Word.
If you have any 3rd party Word macro or add-ins, we recommend that you remove them because they often add an extra overhead to Microsoft Word and slows down the whole PDF conversion process.
After installing the Windows 10 Anniversary Update, you may encounter an issue where server-side Office automation does not work while an interactive user is logged on, but works while all users are logged off.
If you encounter this issue, it can be resolved by creating a unique User Account for easyPDF Printing. This Account must be an Administrator, and must be the Account used for the Loader Service or Impersonation methods of Server Side Printing. This User Account must remain Logged Off during operation.
This will allow other User Accounts to log on to the server freely, without disrupting the Printing Process.
Under Windows Vista, 7, 8.x, 10, Windows Server 2008 and 2012, with Microsoft Word 2003 and 2007, for conversions using WordPrintJob from a system service or a web service, an interactive user must be logged in to the machine at all times. This requirement applies to ASP and ASP.NET alike. Note that only WordPrintJob is affected, whereas other Office conversion classes such as ExcelPrintJob, PowerPointPrintJob, PublisherPrintJob, and VisioPrintJob are not.
If a user cannot be permanently logged in to the machine for some reason, then consider the following workarounds: