Empty Pages are Exported after DOCX to PDF Conversion using .NET

The document is uploaded to the system and when it is desired to be viewed in pdf format, it is seen that blank pages are added to the document and the number of pages is different from the original. There is more than one document in this way. Test application has been added

I attached the original file and corrupted file. We are using Aspose.Word.21.4 version. Thanks.

Test App

@srmbimser

We have tested the scenario and managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-22229. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Can you share what the error in the document is about?

@srmbimser

The issue occurs because Aspose.Words does not reproduce some special MS Word logic when truncating a very tall header that is higher than the page in compatibility mode.

If you copy the header contents and paste them in document’s body, the contents will be rendered over 6 pages. Please rework the document and remove invisible parts from the problematic header.

Hi,
Any progress on WORDSNET-22229?

@srmbimser

Unfortunately, there is no update available on this issue at the moment. We will be sure to inform you via this forum thread as soon as there is any update available on it.

Hi,
Any progress on WORDSNET-22229?

@srmbimser Unfortunately, the issue is still unresolved. Currently we cannot provide you any estimate regarding this issue, since it is not clear how to reproduce MS Word logic. The case is quite specific and looks like rare. The simples way to resolve the problem is reworking the document and removing the invisible parts from the problematic header.

Hi,
Any progress on WORDSNET-22229?

@srmbimser Unfortunately, there is no news regarding this issue yet. The issues is not scheduled for development at the moment.

Hi,
Any progress on WORDSNET-22229?

@srmbimser Unfortunately, There are still no news regarding this issue. The issue is still postponed.

The issues you have found earlier (filed as WORDSNET-22229) have been fixed in this Aspose.Words for .NET 22.9 update also available on NuGet.