Hello,
one of my customers is using aspose pdf for SharePoint in latest Version.
Last month he has opened this thread Aspose.Word for Sharepoint to convert doc/docx to pdf.
This Problem seems to be solved now.
Now thier is another issue. In thier SharePoint 2013 is a document library with several taxonomy columns.
When I set two of these columns with values, the convert process fails with this message:
Conversion has failed for 1 file(s)
An unexpected error occured when trying to convert source file or Folder. Conversion failed
When I leave these values to NULL the conversion is fine.
I cannot find any Errors with these columns.
Are their any possibilities to start a detailed Debugging or any Logs?
In ULS Logs there no corresponding Errors.
Hi Andreas,
Hi tilal,
sorry about the confusion. You are right, it relates to Aspose.Words for SharePoint.
In my library there is a Content type with a list template. In this dotx there are several Word Quick Parts. It seems, that the pdf convert has a Problem with this template.
So I want to know, if there is any additional logging out there, to fix my issue.
As Attachement you can find the corresponding docx from the template.
Kind regards Andreas
Hi Andreas,
OK.
I have an Update for you.
This error was not there in the previous Version (before Aspose.Words for SharePoint 16.12.0)
Hi Andreas,
I have uploaded the docx again.
Hi Andreas,
Hi Awais,
I think you can’t reproduce our issue, because it has something to with These two columns.
Are there any Limitations with the values of Taxonomy columns?
My Steps are:
1. Open the dotx from the library via Content type (SharePoint Ribbon -> New Doument)
2. Type in some text to the template and save it as docx in the same library.
3. Define Metadata to the item like date, Taxonomy und string columns.
4. Convert the docx to pdf over the ribbon.
5. Then I get the error.
My question was, if there are more logging or debug Features?
Later I will attach my template
Hi Andreas,
Any News right now?
The issues you have found earlier (filed as WORDSSP-246) have been fixed in this Aspose.Words for SharePoint 17.1.0 update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.