Skip to main content
MohitPatel4-Participant
4-Participant
Feb 9, 2026 3:24 PM UTC
Question

Publishing TM Getting error

I am trying to publish TM that is around 8000 page. We can publish each chapter separately but when we combined into whole TM, we get this error . 

 

PTC Arbortext Editor (Build 8.1.3.1-2) terminated unexpectedly at Fri Feb  6 15:21:47 2026:

 

[A17120] Assertion failed: size < TXF_MARK, file D:\jenkins\workspace\Adept_1\adept\src\pub\pub\edit\src\stortxt.cpp, line 534

 

Current ACL statement at "C:\progra~1\PTC\arbort~1\packages\main\_grhook.acl":264:
  264 [1]   return path

 

ACL function traceback at time of error:
#1   layout::format(doc=31, sourcedoc=31, sstype="", force=1) at "C:\progra~1\PTC\arbort~1\packages\main\_grhook.acl":264
#2   comp_pdf::pdf_postprocessing(doc=31, params=inParams[], interactive=1)
#3   compose::compose_for_type_int(doc=31, comp_type="pdf", interactive=1, inParams=inParams[], preprocessing_function="comp_pdf::pdf_preprocessing", dialog_function="comp_pdf::dialog_for_pdf", param_fixup_function="comp_pdf::pdf_parameter_fixup", postprocessing_function="comp_pdf::pdf_postprocessing") at "C:\progra~1\PTC\arbort~1\packages\tools\compose.acl":2672
#4   compose::compose_for_type(doc=31, comp_type="pdf", interactive=1, inParams=current_params[], prefn="comp_pdf::pdf_preprocessing", dialogfn="comp_pdf::dialog_for_pdf", paramfn="comp_pdf::pdf_parameter_fixup", postfn="comp_pdf::pdf_postprocessing") at "C:\progra~1\PTC\arbort~1\packages\tools\compose.acl":1761
#5   compose::compose_for_pdf(doc=31, batch_params=dummy[]) at "C:\progra~1\PTC\arbort~1\packages\tools\comp_pdf.acl":324
#6   compose_pdf() at "C:\progra~1\PTC\arbort~1\packages\tools\comp_pdf.acl":117

 

thank you 

7 replies

bfriesen
bfriesen18-Opal
18-Opal
Feb 9, 2026 6:12 PM UTC

Just did a quick search of the PTC help

 

Looks like it has been asked before also with no solutions

https://community.ptc.com/t5/Arbortext/A17120-Assertion-failed-aptFalse-file-src-forsirtns-cpp-line/m-p/497907#M31261%3Fsource=search

https://community.ptc.com/t5/Arbortext/Error-A17120-Assertion-failed-size/m-p/231400#M16455%3Fsource=search

https://community.ptc.com/t5/Arbortext/blown-out-paths/m-p/190636#M13534%3Fsource=search

 

here are a couple from PTC support to look at.

https://www.ptc.com/en/support/article/CS410678?source=search

https://www.ptc.com/en/support/article/CS187410?source=search

Sotution:

  • The problem is due to the length of the <item>s contents exceeding the maximum length for <item>s in an assertion check
  • Removing the assertion has the potential to cause the application to become unstable and likely to crash

Bryon

Translate
manpsingh12-Amethyst
12-Amethyst
Feb 10, 2026 3:24 PM UTC

Dear Customer,

 

Have you made any changes to this ACL? Did you customise this?

 

Regards,

Manpreet Singh

Translate
MohitPatel4-ParticipantAuthor
4-Participant
Feb 10, 2026 4:06 PM UTC

Thank you Manpreet and bfriesen,

 

we have not modified any ACL. Per PTC support ticket https://www.ptc.com/en/support/article/CS410678?source=search

 

I have test version of Editor 8.3.1. Ran thorough the same manual, I got signal 22 error. 

 

 
Translate
manpsingh12-Amethyst
12-Amethyst
Feb 12, 2026 3:47 PM UTC

Hello Mohit,

 

Did you also face the same error (along with what you mentioned above) mentioned in that article?

 

Regards,

Manpreet Singh

Translate
ECampbell11-Garnet
11-Garnet
May 14, 2026 8:11 PM UTC

Hello,

We have seen very similar behavior, specifically working on large documents. The issues started specifically with the upgrade to Editor 8.0 and have persisted ever since.

We have also encountered this when publishing individual chapters, depending on their size, and we work with some very large documents. Our only workaround has been to use queued transactions. We’re unalbe publish the full manuals affected by this issue (even using queues), but we are able to use queued transactions for the larger chapters which also fail, and then publish the others individually using our standard methods.

Will you update here if you do get an answer? 
 

Translate
Terms & ConditionsAccessibility statement