XLS to PDF conversion has a watermark

GroupDocs.Conversion Product Family
,
1

In version 25.6 when I convert an XLS to PDF the result includes a “temp_watermark” text.

Attaching the source and the result files.
watermark.zip (22.4 KB)

2

@adrian.gruber.95

It sounds like you’re encountering a watermark issue during the conversion of XLS to PDF in version 25.6. This “temp_watermark” text typically appears when the document is being processed in a trial mode or if there are licensing issues.

Cause: The watermark indicates that the GroupDocs.Conversion library is either in trial mode or there is a problem with the license.

Solution: To resolve this, please follow these steps:

  1. License Verification: Ensure that you have a valid license for the GroupDocs.Conversion library. If you’re using a trial version, the watermark will appear on the output documents.

  2. License Implementation: If you have a license, make sure it is correctly implemented in your code. Here’s a sample code snippet to set the license:

    // Load the license
License license = new License();
license.SetLicense("path_to_your_license_file.lic");

  3. Re-run the Conversion: After confirming the license is set correctly, try converting the XLS file to PDF again.

Next Steps: If you continue to see the watermark after these steps, please provide more details about your implementation, including any error messages or code snippets, and I will assist you further.

Thank you for your patience, and I look forward to helping you resolve this issue!

3

I can reproduce the issue with the online converter (Online file conversion | Free GroupDocs Apps) so I think it should be an internal error.

4

I exported the file with LibreOffice and I figured that it puts the file name in the metadata which is rendered in the generated PDF file. Jira’s file viewer does the very same thing so I guess it is expected. I’m sorry if it is a false alarm as I wasn’t aware of this LibreOffice behavior.

5

Hello @adrian.gruber.95 ,

Thank you for reaching out to us and for sharing additional details regarding this situation. We were able to reproduce this behavior on our side, and as you mentioned, the cause may indeed be the export from LibreOffice. However, we will continue to investigate this behavior in more detail and may be able to improve our library to avoid such situations in the future.

1 Like