Hello, we have an automated process that runs and converts Word docs to PDF. It has been running for a long time (using v 17.7) without any issues. A few weeks ago we noticed that the font substitution stopped working correctly. The Calibri font in the Word files was being changed to Fanwood in the resulting PDF. We believe this was caused by new security policies put into place that have placed some kind of restrictions on the service account(s) that run this automated process that does the conversion. We run this on Windows Server 2016. We have added the service accounts as local admins on this server but the process is still not converting correctly. Can anyone suggest other security settings that we can check or help us determine which setting may have been changed/removed to cause this behavior?
It seems that the problem occurs because your application using Aspose.Words does no longer have permissions to access Fonts folder on your server machine. You can search on web to determine how to give permissions to access font files folder e.g. Redirecting
Do you see any warning messages during Word to PDF conversions (refer to: How to Recognize That the Font Was Replaced)? Alternatively, you can add fonts in a custom fonts folder inside your application and instruct Aspose.Words to look for fonts in only that folder. Please refer to Specifying TrueType Fonts Location