Issue with DOC to PDF Conversion - Output Trimmed to 3 Pages

GroupDocs.Conversion Product Family
,
1

Hi Team,

We are facing an issue while converting DOC/DOCX files to PDF using GroupDocs.Conversion for Java.

Issue Details:

  • During conversion, only the first 3 pages are present in the generated PDF.
  • Remaining pages are getting trimmed/skipped.
  • No exception is being thrown during conversion.

Environment Details:

  • Product: GroupDocs.Conversion for Java
  • Current library version: 23.6
  • License Type: Developer OEM
  • Subscription Expiry: 2026-01-23

Sample Conversion Code:

private String convertToPdfIfRequired(String originalFilePath, String sharedDirectory, int sortOrder) {

    if (originalFilePath == null || sharedDirectory == null) {
        return null;
    }

    String extension = originalFilePath.substring(originalFilePath.lastIndexOf('.') + 1).toLowerCase();

    if (!List.of("doc", "docx", "xls", "xlsx").contains(extension)) {
        return originalFilePath;
    }

    String pdfFilePath = Paths.get(sharedDirectory, sortOrder + "_converted.pdf").toString();

    try (Converter converter = new Converter(originalFilePath)) {

        PdfConvertOptions options = new PdfConvertOptions();
        converter.convert(pdfFilePath, options);

        return pdfFilePath;

    } catch (Exception e) {
        e.printStackTrace();
        return null;
    }
}

Observations:

  • Conversion completes successfully without errors.
  • Generated PDF contains only 3 pages even though the source document has more pages.
  • We suspect this may be related to license validation/evaluation mode behavior.

Could you please confirm:

  1. Whether expired/incompatible licenses can cause page trimming limitations.
  2. Whether our current license is compatible with the library version being used.
  3. If there are any additional configurations required for full document conversion.

Please let us know if any additional logs/sample documents are required.

2

@Polus

I’m sorry for the delayed response, it is highly likely that the license is not applied and library works in the trial mode. Please share you license file by sending it to developers@groupdocs.com and we’ll take a look what is going on as it looks like the version you’re using does not support newer license signature.

3

Could you clarify the difference between LicenseExpiry and SubscriptionExpiry in our Developer OEM license? Specifically, what behavior should we expect after LicenseExpiry (2026-04-26) and SubscriptionExpiry (2027-03-26) while using GroupDocs.Conversion for Java 23.6? Will the product continue to function normally for eligible versions, or are there any licensing restrictions after this date?

4

@Polus

These two dates have different purposes.

LicenseExpiry

This is the date until which the license itself is valid.

  • The license stops working after this date.
  • If your application is successfully licensed today and this date is in the future, the license is considered valid

In your case 2026-04-26 means the license is already not valid.

SubscriptionExpiry

This controls which product versions you are allowed to use, not whether the license itself is valid.
GroupDocs products contain a release date. When you apply a license, lib checks:

Is the product version’s release date on or before the SubscriptionExpiry date?

If yes, the license works.

If you use a product version released after the subscription expiry date, lib is expected to throw an exception telling you to renew your subscription or use an older version.

Now, let’s return back to your questions:

Specifically, what behavior should we expect after LicenseExpiry (2026-04-26) and SubscriptionExpiry (2027-03-26) while using GroupDocs.Conversion for Java 23.6? Will the product continue to function normally for eligible versions, or are there any licensing restrictions after this date?

Since license expiry is already passed the license is no longer accepted and the lib turns into evaluation mode, so it is the root cause of the issue.

Since you does not see any exceptions it supposed to be a bug. Let me report it to the dev team so they could take a look into the code. The issue ID for reference is CONVERSIONJAVA-3149.

5

Hi @Polus, I will fix it in 26.6, the exception should be thrown.