Error Logs

[ptc-3050150]

I've now dug through 17 PTC PDF manuals.

Where in the world is an honest to goodness error log?

It is bad enough the composer log window when it does give the line of the stylesheet where it hit an error, it doesn't tell you which XML file it was parsing at the time. I've got those cleaned up now BUT!

I still have a multitude of errors that are just too vague to be useful (like "received fo:block when expected fo:root" with no code context at all).

I've dug through the transaction archives file by file. I still don't know what to do with a .dat file even with all the PDF manuals.

Shoot, I can't even get our Windows 2003 Server to show the Java Console!

Finally get through IT and get some access to the server, but I still can't find a decent error log.

Thanks again, guys...

John T. Jarrett
Sr. Tech Writer, BAE Systems

Arbortext version 5.4

LOGSA XSL-FO v 1.5

[mramshaw]

I agree this is an error that needs a lot of work, debugging PE server applications seems almost impossible. I once had good luck with going in C:\windows\temp on the PE Server machine and there were a lot of directories like e3_4455 in it that would appear for each recent compose attempt. In these directories were actual composer.log files that were very useful. They stopped appearing for some reason though which really annoys me but if you can find them, they will be quite helpful. If anyone could provide some help on finding a log on the PE server, it would be most appreciated.

[naglists]

I suggest opening a call. I do not remember all the different logs I have
been instructed to open for various problems, but I know there are many.
Some involve multiple configuration items (changing log levels ERROR, WARN,
INFO, for example), directing various threads to specific files, max file
size before rolling, max copies of files, etc. etc. etc. Often these config
changes are by way of ACL settings run from init. Sometimes by environment
variables.

I agree, though, it would be an awesome resource, to have an exhaustive,
centralized list of such logging functionality. I know if I searched my
calls, I could find some of the ones I've used.

On Mon, Jan 18, 2010 at 2:35 PM, John Jarrett
<->wrote:

> I've now dug through 17 PTC PDF manuals.
>
> Where in the world is an honest to goodness error log?
>
> It is bad enough the composer log window when it does give the line of the
> stylesheet where it hit an error, it doesn't tell you which XML file it was
> parsing at the time. I've got those cleaned up now BUT!
>
> I still have a multitude of errors that are just too vague to be useful
> (like "received fo:block when expected fo:root" with no code context at
> all).
>
> I've dug through the transaction archives file by file. I still don't know
> what to do with a .dat file even with all the PDF manuals.
>
> Shoot, I can't even get our Windows 2003 Server to show the Java Console!
>
> Finally get through IT and get some access to the server, but I still
> can't find a decent error log.
>
> Thanks again, guys...
>
> John T. Jarrett
> Sr. Tech Writer, BAE Systems
>
> Arbortext version 5.4
>
> LOGSA XSL-FO v 1.5
>