Skip to main content
S
Sherri_McCue
Participant
February 14, 2017
Question

Validation Error Messages Not Logged In Console Window (FM12)

  • February 14, 2017
  • 1 reply
  • 2010 views

When I save a structured documents as XML (File -> Save As – XML), messages and errors appear in a Console Pod but are not reflected in the Console Window or in consfile.txt

Any help appreciated.

This topic has been closed for replies.

1 reply

S
shoose
Known Participant
March 11, 2017

I have this problem also -- I need to capture the validation errors somewhere, but they are not logged to consfile.txt.  Is there a setting somewhere that controls what is written to consfile?

I am using FrameScript also, and have not yet found a way to capture these validation errors from the console pod and copy them to a file somewhere.

This seems like a serious bug or issue in Frame, that errors just disappear and are not logged anywhere, unless there is a workaround.

I'm now on FM 2015.

Thanks much,

Shelley

W
Wiedenmaier
Inspiring
March 14, 2017

I'm never used the console.txt file for error handling in all the years.

XML messages that appear are validation issues mostly. So you can check the root element if structure is valid after document is opened or before it is saved.

Other issues are due to an inconsistent environment, XML application. So once your Setup is correct, there is no need anymore to check console.txt.

Markus

S
shoose
Known Participant
March 14, 2017

Markus -- Thanks for taking the time to reply.

We work in an environment with multiple writers, and sometimes someone edits a file in a way that renders it invalid, thus causing parsing messages in Frame. We have everything set up in automation because the products have a large set of documentation that we cannot maintain by hand -- so these parsing errors can just "fly by" during HTML and PDF generation without our knowing that a document is in a bad state.

I therefore need a way to capture these errors, hopefully through FrameScript since FM obviously cannot do it natively. It sounds like, even in FM 2017, these XML parsing errors are not logged to console.txt, unfortunately.

We currently grep console.txt for logged errors relating to broken xrefs, which works well. If console.txt captured a more complete set of errors/logs, it would be highly useful.

Thanks,

Shelley

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices