We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Aspose.Word.dll 17.2.0.0 stops working

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

Sorry about the word wrapping!

Hi Kristen,

Thanks for your inquiry. We suggest you please remove all old reference of Aspose.Words from your application and add reference of Aspose.Words for .NET 17.3.0 in your application. Hope this helps you.

It seems that you are using Aspose.Words and Aspose.Email. Could you please share some more detail about your use case along with input documents? We will investigate the issue on our side and provide you more information.

The developer is also asking where we should be setting the license. We are currently setting it every time we create a PDF. When is the best time to set this?

Hi Kristen,

Thanks for your inquiry. Please refer to the following article. Hope this helps you.

When to Apply a License

Thank you! I think that will resolve our issue.

Hi Kristen,

Thanks for your feedback. Please feel free to ask if you have any question about Aspose.Words, we will be happy to help you.