We have a scenario where we are converting an RTF file to PDF. The conversion process itself works correctly; however, we encountered a case where the source RTF file triggers two security warnings (screenshots attached).
The first warning states:
“Some content is blocked”
and requires the user to click either “Unblock” or “OK.”
The second warning states:
“This document contains code your security settings do not allow…”
and requires the user to click “OK.”
Because this process runs silently on a server, these dialog boxes cannot be interacted with and cause the conversion to hang. We are looking for a supported method to suppress, bypass, or otherwise handle these security prompts during automated execution.
Please advise on the recommended approach.
@ian.jenkins It looks like the warning are shown because RTF documents contain some suspicious macros. Aspose.Words does not run any macros in the document, so the warning will not be the problem upon converting RTF document to PDF using Aspose.Words. The macros will be simply ignored by Aspose.Words.
I wish that were the case, however, when I attempt to load the RTF file it just hangs infinitely.
This is the line that it hangs on:
Aspose.Words.Document document = new Aspose.Words.Document(inputPath);
@ian.jenkins Could you please zip and attach the problematic RTF document here for testing? We will check the issue and provide you more information.
After further investigation, it was determined that the security warnings are not the root cause of the issue. We opened several documents that converted successfully and found they contained the same warnings, yet processed without any problems.
The issue appears to be related to the size and complexity of this particular document. The source RTF is approximately 100MB and renders into a 111-page PDF. We currently have logic in place to detect conversions that appear hung or exceed an expected processing time. In this case, the conversion is taking approximately 15 minutes to complete.
Is there anything that can be done to reduce the document load time or PDF save time? We were wondering if there are any load options or performance-related settings that could help optimize the conversion process.
Additionally, would it be safe to remove or relax our timeout routine? Does Aspose have any built-in handling or safeguards for long-running operations? This code was originally ported from an Office automation-based solution where hung conversion requests were common, making the timeout logic absolutely necessary at the time.
@ian.jenkins Unfortunately, without the problematic document it hard to tell whether there is a way to speedup document processing. Therefore, if possible, could you please share the problematic RTF for testing?
Please see our documentation to learn about document pceissing interruption:
https://docs.aspose.com/words/net/document-processing-interruption/