We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Page# re-fresh issue when track change is on using Aspose.Word

We confirmed with track changes ON, the validation error was actually on page 26. We then turned track changes OFF, and the validation error was on page 19. What this confirms is ASPOSE.word (version= does not account for the additions/deletions of content and the impact to page numbers as a result of the additions/deletions when track changes are on. Workaround is "Tracked changes causes the page # to be off, to make the pages line up in Word under the reviews tab change ‘All Markup’ to ‘No Markup’ and this will make the numbers match.”
Question - Does anyone have seen same/similar situation where ASPOSE was integrated in the application? If so, how did you handle and potential resolved it? Please advise.
ASPOSE support team - Is this a known issue in Version = If so, has it been addressed in higher version? Please advise ASAP.

Please forward as appropriate, if you know some one else might have resolve this issue before. Alternatively, you can share name with me and I will send out details.

Thank you all in advance,


Thanks for your inquiry. To ensure a timely and accurate response, please attach the following resources here for testing:

  • Your input Word document.
  • Please share how are you validating the page numbers.
  • Please create a standalone console application ( source code without compilation errors ) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip and upload them.

Thank you for quick response. Please find attached document contains screen shots with explanation. Hope this helps. We are working with our DEV team to create standalone console application, per request.

Thank you again,ScreenShots-For-AsposeForum.pdf (456.2 KB)


Thanks for sharing the detail. Please ZIP and attach your input Word document and code here for testing. We will investigate the issue on our side and provide you more information.

Please find attached ZIP contains console App (Code and input word document) to simulate the situation on your side. Thank you for your patience and looking forward to hear back from you soon for resolution.cs.CM.Templates.PageElements.zip (159.6 KB)


Thanks for sharing the detail.

We suggest you please use the latest version of Aspose.Words for .NET 19.2. Hope this helps you.

If you still face problem, please ZIP and attach your input document and expected output here for testing. Unfortunately, we have not found the input document in the shared ZIP file. We will investigate the issue on our side and provide you more information.

Thank you for quick response. Sorry for missing input document, ASPOSE-InputDocumentTemplateForTesting.zip (138.3 KB)
here you go. The previously attached screen shots shows the expected outcome and current outcome. Hope this will help.


Thanks for sharing the detail. We have executed the shared application using the latest version of Aspose.Words for .NET 19.2 and got the message “Parse - succeeded.”. Please check the attached screenshot.

Thank you for execution of the console app. The parsing is always successful, the issue is related to the page numbers mismatch with track changes on/off. Would you please simulate the situation that way and see? Sorry, it took little longer to get back to you.

Thank you again,


Thanks for your inquiry. Have you tried the latest version of Aspose.Words for .NET 19.2?

We tested the scenario by turning on/off the track changes for your document. We have not found any difference in output.

If you still face problem after using the latest version of Aspose.Words for .NET 19.2, please share following detail for further investigation. This will help us to understand your scenario and we will be in a better position to address your concerns accordingly.

  • Your question is not clear enough therefore we request you to please elaborate your inquiry further.
  • Please share what is validation errors.
  • Please create and share simplified console application that uses only Aspose.Words code.
  • Please share the screenshot of problematic output generated by sample application.
  • Please share the expected output.

Thanks for your cooperation.

Hello - Thank you for prompt response. Glad to know, the issue is not appeared with 19.2 version. Would you please send us screen shot for that test? We would like to share with our QA team.

Thank you -


Thanks for your inquiry. The following screenshot shows the output when tracking changes is off.

The following screenshot shows the output when tracking changes is on.