The following is an excerpt from our Scrub log as we process metadata with Aspose.Word.dll (version 17.2.0.0)
…Showing iScrub Prompt…
[TaskHelper bool DisplayDialog(IntPtr, IDetergent, IAttachments, IAttachments, int)]
[TaskHelper][DisplayTaskDialog]: Attachment count: 2
[TaskHelper][DisplayTaskDialog]: DefaultScrubLevel != 0 so use default
[TaskDialog.xaml.cs InitDialog()] nDefaultLevel = 1
[TaskHelper DisplayTaskDialog] ScrubAction -> PromptEach
…Invoking iScrub…
In wdBaseManger Invoking word scrub
In new DocManager
*** THIS IS WHERE IT STOPS PROCESSING ***
*** NORMALLY CONTINUES AS FOLLOWS ***
In docManager constructor
DocManager.OpenDocument()
base PerformScrub
PerformScrub invoking Scrub document
…iScrub completed file processing…
Outlook: Entered
CMAPIWrapper::SwapAttachment
[Attachments Clear()]
--------------------------------------------
OUTGOING ATTACHMENTS:
_ FORM Lodgeside Condominium Addendum - Construction (1.17.17).DOCX
_ FORM Lodgeside Buy Sell Agreement- Construction (2).PDF
image001.png
----------------------------------------
Outlook: [CConnect.ScrubMailItem] Return from RunScrubMailItem
Outlook: Entering cleanup routine
Outlook: Starting cleanup
Outlook: ScrubMailItem returns:
ResultSuccessNoRPost
2017-02-28.17:13:44
When I asked our developer what is happening at the stoppage point he replied we are trying to set the license so we can use the Aspose dll:
License license = new License();
license.SetLicense(“Aspose.Words.lic”);
This problem appears to have started after we upgraded the Aspose.Word.dll from 16.11.0.0 to 17.2.0.0.
It does not happen on every Word document we attempt to process and it is not reproducible with the same document that previously failed. It causes Outlook to freeze and Outlook must be restarted. The developer is wondering whether we are setting the license information correctly, or if something change recently.
Thanks,
Kristen Theologus
Produce Support Specialist
BigHand