As example of .DOCX extension (no PDF created):
D:\Esko\bg_prog_fastserver_v242\bin_x64>mkdir “\D03414-T-APP01\FileStore\temp\9882ad1d-bdb8-430a-b086-6d7bfbf4c12a\000005\00002_0000050976_inProgress\2f0aa215-aa49-418b-8c19-369f40c4c8e3.DOCX”
D:\Esko\bg_prog_fastserver_v242\bin_x64>D:\Esko\bg_prog_fastserver_v242\jre_x64\bin\java -jar “D:\Esko\bg_data_fastserver_v100\Scripts\Batch\ConvertOfficeFiles-jar-with-dependencies.jar” ""D:\Esko\bg_data_fastserver_v100\jdf\temp\JDFPBackStageTask\2f0aa21
[D:\Esko\bg_data_fastserver_v100\jdf\temp\JDFPBackStageTask\2f0aa215-aa49-418b-8c19-369f40c4c8e3.DOCX, \D03414-T-APP01\FileStore\temp\9882ad1d-bdb8-430a-b086-6d7bfbf4c12a\000005\00002_0000050976_inProgress\2f0aa215-aa49-418b-8c19-369f40c4c8e3.DOCX, pdf,
Warning: No license could be loaded
For comparison, here a PDF is created successfully::
D:\Esko\bg_prog_fastserver_v242\bin_x64>mkdir “\D03414-T-APP01\FileStore\temp\ee23d274-d188-4bfe-b9bb-4c22e23331f1\000005\00002_0000050977_inProgress\6eb4f203-9841-4dbb-9b09-5bd240d483e5.docx”
D:\Esko\bg_prog_fastserver_v242\bin_x64>D:\Esko\bg_prog_fastserver_v242\jre_x64\bin\java -jar “D:\Esko\bg_data_fastserver_v100\Scripts\Batch\ConvertOfficeFiles-jar-with-dependencies.jar” ""D:\Esko\bg_data_fastserver_v100\jdf\temp\JDFPBackStageTask\6eb4f20
[D:\Esko\bg_data_fastserver_v100\jdf\temp\JDFPBackStageTask\6eb4f203-9841-4dbb-9b09-5bd240d483e5.docx, \D03414-T-APP01\FileStore\temp\ee23d274-d188-4bfe-b9bb-4c22e23331f1\000005\00002_0000050977_inProgress\6eb4f203-9841-4dbb-9b09-5bd240d483e5.docx, pdf,
file\D03414-T-APP01\FileStore\temp\ee23d274-d188-4bfe-b9bb-4c22e23331f1\000005\00002_0000050977_inProgress\6eb4f203-9841-4dbb-9b09-5bd240d483e5.docx\6eb4f203-9841-4dbb-9b09-5bd240d483e5.pdf, created.
Both are triggered in the same manner where of course the license is available and acknowledged when input is .docx, but not when .DOCX.
Glad to provide any further information upon request, but may need guidance for where to look. I cannot discern right off if/which version of Aspose is employed in ConvertOfficeFiles-jar-with-dependencies.jar
@eskonesu
It seems that you are encountering an issue with loading the license when converting a .DOCX file to PDF, specifically when the file extension is in uppercase (.DOCX). Here are some steps and considerations that might help you resolve this issue:
-
Check License Loading: Ensure that the license loading code is executed correctly. The license must be set before any Aspose objects are instantiated. If the license is not found or is invalid, it may lead to warnings or errors during processing.
-
File Extension Sensitivity: The issue you are experiencing could be related to how the library handles file extensions. Some libraries may treat file extensions as case-sensitive. Try renaming your .DOCX files to lowercase (.docx) and see if the conversion works without any warnings.
-
Debugging License Issues: If you are using a debugger, step through the code to confirm that the license loading method is being called and that it does not throw any exceptions. If there are exceptions, they may provide insight into why the license is not being loaded.
-
Check for Existing Evaluation Messages: If the input documents already contain evaluation messages, Aspose libraries do not remove them. Ensure that the documents you are converting do not have any remnants of previous evaluation messages.
-
Multiple Libraries: If you are using multiple Aspose libraries (e.g., Aspose.Words and Aspose.PDF), ensure that you are setting the license for each library appropriately. You can set the license once per application domain, typically at the start of your application.
-
Version Compatibility: Make sure that the version of the Aspose library you are using is compatible with the license file. If the license has expired or is not valid for the version you are using, it may lead to issues.
If you continue to face difficulties, consider providing additional details about the version of the Aspose library you are using and any specific error messages you receive. This information can help in diagnosing the problem further.
If you need more assistance, feel free to ask!
Where do I find the version?
@eskonesu Could you please provide code that will allow us to reproduce the problem? We will check the issue and provide you more information.
@eskonesu Thank you for additional information. But, I am afraid, I do not see where Aspose.Words is used in the provided bat.
Further scrutiny to our part of the code focusing to ‘Warning: No license could be loaded’ has our R&D team suspecting we may be able to resolve this. That effort is ongoing. If possible to keep this open for some time; a few days, or week at most, I can offer back confirmation.
1 Like