cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

E3 5.3 Publish Error

unknown1
Newbie

E3 5.3 Publish Error

When I try to publish web content, File->Compose->To Web, with E3 v5.3 Publishing Engine, I receive the following error:

ERROR
-----
endDocument() fail.

FATAL ERROR
-----------
Fatal error encountered while running composition pipeline. Configuration File: "C:\Program Files\Arbortext\PE\composer\web.ccf".

FATAL ERROR
-----------
Operation terminated.

This is not enough information for me to troubleshoot. The file is original from the installation. I just installed the software this morning and tried a test run.

I also get the following warning when I open up the XML file in the Publishing Engine:
[A15013]
Warning: DTD 'C:\Program Files\Arbortext\PE\custom doctypes\jws\jws.dtd' has been modified since document type was last compiled. Consider recompiling the document type.

The DTD and associative files were exported from the Documentum repository, therefore I dont understand how it was changed. Does the software look at the timestamp, because the timestamp changes when the files have completed downloading.

Thanks for your help.

Mario Williams
Tags (2)
4 REPLIES 4

Re: E3 5.3 Publish Error

Hi Mario,

> The DTD and associative files were exported from the Documentum
> repository, therefore I dont understand how it was changed. Does the
> software look at the timestamp, because the timestamp changes when
> the files have completed downloading.
If you're using a compiled doctype application (and it sounds like you
are), then the software will produce a helpful informational message when
any of the DTD source files have a timestamp more recent than the binary
files created by the Compile > DTD process. The binary files are named
[doctype].ptd, [doctype].pro, [doctype].dec. It would be nice to be able
to toggle these helpful informational messages on and off, because my Ant
deployments tend to cause the same "disturbing" messages (even after
creating a touch task with the same timestamp on all files in the custom
directory).

Note that a compiled DTD is not always required. A different parser is
available to you as long as you don't have dependencies on the compiled
DTD (your CMS may require it, for example).

As to your fatal error with endDocument(), I'd try using PE Interactive on
your server with the doctype in question. Try using the other output
formats and observe results. You may also learn more by digging into the
web.ccf. I'm sorry I don't have more information for you, I do not
presently use PE's Compose to Web feature.

Hope this helps,
Jason





"mario.williams.ctr" <mario.williams.ctr@eglin.af.mil>
06/13/2007 04:43 AM
Please respond to
<adepters@arbortext.com>


To
<adepters@maillist.arbortext.com>
cc

Subject
E3 5.3 Publish Error






When I try to publish web content, File->Compose->To Web, with E3 v5.3
Publishing Engine, I receive the following error:

ERROR
-----
endDocument() fail.

FATAL ERROR
-----------
Fatal error encountered while running composition pipeline. Configuration
File: "C:\Program Files\Arbortext\PE\composer\web.ccf".

FATAL ERROR
-----------
Operation terminated.

This is not enough information for me to troubleshoot. The file is
original from the installation. I just installed the software this morning
and tried a test run.

I also get the following warning when I open up the XML file in the
Publishing Engine:
[A15013]
Warning: DTD 'C:\Program Files\Arbortext\PE\custom doctypes\jws\jws.dtd'
has been modified since document type was last compiled. Consider
recompiling the document type.

The DTD and associative files were exported from the Documentum
repository, therefore I dont understand how it was changed. Does the
software look at the timestamp, because the timestamp changes when the
files have completed downloading.

Thanks for your help.

Mario Williams >> To unsubscribe from the list, send an email to
listmanager@maillist.arbortext.com with the following in the body:
unsubscribe adepters - For additional information on the adepters list
(how to subscribe or unsubscribe etc), send an email to:
listmanager@maillist.arbortext.com with the following in the body: info
Adepters - You may also go to forums.arbortext.com, enter the Adepters
folder and change your subscription options and preferences.>>

Writable file left open after check-in

Hello adepters,

I'm currently using Sigmalink and Epic 4, and the bridge between them is
set up so that if I check-out and change a file in Epic, and then check
it in from Sigmalink, the file in Epic closes.

I'm replacing Sigmalink with Documentum 5.3 and upgrading to Arbortext
Editor 5.3 with the DocumentumWDK bridge. With the same check-out,
change the file, check-in from Documentum process, I'm left with a
writable file in the editor.

Does anyone else have a similar setup that can verify this issue? Has
anyone found a way to solve it?

Thanks.
>> Randy



RE: E3 5.3 Publish Error

Jason,
Thanks for the response. I recompiled the DTD and the error went
away. I appreciate your help. I have one more problem, which I posted a
on the adepters site: When I try to publish my XML file, the E3
Publishing Engine stops without error. It creates the output folder but
there is no content files in the folder. When I say content files, I
mean no HTM files were generate. It does contain "graphics" folder and
all the files that are copied from the "framesets/default/default/"
folder. I wished that E3 would give back some meaningful error message,
but it doesn't. Do you know what the problem could be? I went through
the XML file and added a chapter at a time until I got to the chapter
which caused the problem. Then, I added each section of that chapter
until I found the section which was causing the problem. The section
which caused the problem was valid according to the DTD. One thing I
notice was that my <sectiontitle> had a '>' sign was on the line below
due to word-wrapping. When I pulled it up to the line above, the publish
worked file. Do you have any idea why this happens? Also, some of the
content will only publish if I add it one piece at a time. Some sections
make the composition fail, but when I added each <para> to the section
it works. E3 Publishing Engine is giving me fits. Thanks again.

Mario Williams

Re: E3 5.3 Publish Error

On 6/14/07, Williams Mario L CTR USAF AAC/ENA <Mario.Williams.ctr@eglin.af.mil> wrote:

...folder. I wished that E3 would give back some meaningful error message,
but it doesn't.

It's possible to see more of what's going on Publishing Engine. Support will occasionally ask me to do the following if we're chasing a problem. I usually forget to do it myself.


Enable Publishing Engine debugging:
1) On your PE Server, select Start > Programs > Arbortext > PE Configuration 5.x.
2) In the configuration panel, click Edit Configuration using PE Interactive.

Notes:
a) PE Interactive is "just" Editor within the PE publishing environment.
b) The file now open is e3config.xml.
c) This file controls your PE server's behavior. Don't do this on a production PE server unless you know what you're doing or you like getting screen-captures from your customers 😉

d) The first element should be <parameter name="debug" value="false">.
3) Change the value of value to true.
4) Save e3config.xml and close PE Interactive.
5) Cancel out of the PE Configuration dialog.

6) Restart Tomcat.
7) Select Start > Programs > Arbortext > PE Diagnostics 5.x.

😎 From your client, submit the failing job.
9) Watch the fun in the PE Diagnostics window.
10) Fix the problem.
11) Undo the configuration change (return debug to false, restart Tomcat).
12) Open something cold.


Ok, support didn't really tell me to do step 12. I improvised.

Seriously, consider what the PE server is being used for ... if you have test servers, that's where you want to do this. If you have to test on prod, consider doing this type of thing off-hours for all the obvious reasons.


--
Paul Nagai
Announcements