I had a similar dvi error reporting - no information to help troubleshoot.
If I read your post right it seems the opposite of what I had difficulties
with. My situation was that it work with Print composer (local engine) but
would not work with PE.
After packaging everything up and sending it in, it turned out to be
related to the content. For me the issue was missing graphics. I had a
reference to a file that didn't exist. Evidently Composer and PE react
differently to the problem. Where Composer reported the problem and
carried on, PE would kick back an error that looked similar to yours and
Maybe some one restored a file on you?
> I'm presently ignoring the problem which may be related to a specific test
> document. I gotta get the formatting work done, then I'll come back and
> start chopping up my test doc.
> That said, I am doing Print Composer runs (not Print Previews, but the
> results may be the same ... I am definitely seeing .dvi leftovers in
> .aptcache) during development. I will typically post the .style to PE and
> test it in that environment toward the end or when I need authors to
> with author-eyes.
> Ok, I just did two print previews and two PDF compositions using the old
> new "test documents" and all is well. Hmmm. Either I've unknowingly
> whatever was hinky in the .style, the gremlins are bugging someone else
> today, or they're planning a fashionably late arrival. I did reboot a
> of times yesterday ... that didn't fix it then. I also got Clay's favorite
> failure (Crash within a Crash) at one point.
> Ah well ...
> On Thu, Jun 17, 2010 at 4:10 AM, Benton, Ed L <->
>> With Print Composer, doing Print Preview creates a DVI file, which is
>> file that is actually being viewed during Print Preview. Sometimes this
>> will expose errors that you can?t find during regular PDF processing.
>> not familiar with what goes on in PE and/or Styler, but what happens
>> you do a Print Preview?
>> Or you might try set crashyboingboing=off.
>> *From:* Paul Nagai [
>> it fails the composition and displays a DVI exception (opening dvi file
>> (filename) dvipos...