• State Verified Answer
  • Replies 1 reply
  • Subscribers 137 subscribers
  • Views 1458 views
  • Users 0 members are here
Options
Related

How can I diagnose publish failing to store result?

Kendall Shaw

We are using Knowledge Center. A publish succeeds running DITA-OT but then fails when storing the result:

Unable to store the result. See eventdata for more details.

The evendata says:

ExportDataToFileSystem started - lTotalNoOfLngCardIds99

ExportDataToFileSystem started

ExportDataToFileSystem started - lTotalNoOfLngCardIds3166

Unable to store the result

 

Do you know what could be causing this?
Rate translation
×
Suggest better translation
×
Parents
  • +1

    Hi

    Looks more like a support ticket to me as you can provide more details and context (actual data, only reproduced with one or all pubs, log files, etc)... this could be about

    1. Running out of disk space on your publish server
    2. Large data (massive images typically that force disk/memory fragmentation issues)
    3. Weird characters in the generated filename (so probably weird characters in FTITLE)
    4. Absolute connection/database timeouts
    5. ...

    In Docs 13/13.0.1 the publishing pipeline got a complete revamp, compared to your Knowledge Center 2016/12.0.x. Definitely worth the upgrade :)

    Best wishes,
    Dave
Reply
  • +1

    Hi

    Looks more like a support ticket to me as you can provide more details and context (actual data, only reproduced with one or all pubs, log files, etc)... this could be about

    1. Running out of disk space on your publish server
    2. Large data (massive images typically that force disk/memory fragmentation issues)
    3. Weird characters in the generated filename (so probably weird characters in FTITLE)
    4. Absolute connection/database timeouts
    5. ...

    In Docs 13/13.0.1 the publishing pipeline got a complete revamp, compared to your Knowledge Center 2016/12.0.x. Definitely worth the upgrade :)

    Best wishes,
    Dave
Children
No Data