|
| We are trying to set up an application using ActivePerl and FrameScript to
create PDF files from FrameMaker files via a webinterface. Until now we were
not able to launch FrameMaker completely. After removing some blockades in
the access control the FrameMaker process launches and keeps running.
Using FileMon from SysInternals I found out that part of the initialization
process is executed normally, but at a certain point the file access stops,
this point is the same every time. I found out that, when starting FrameMaker
directly via remote access, the file access should continue for a certain
amount to complete the initialization. Therefore I guess the initialization
aborts for soem internal reasons. Since no error messages are left that may
indicate the problem I am stuck now.
Is there anyone who may have a clue on what might be the cause of this
initialization stop?
The configuration is a Windows 2003 Server with IIS 6.0. FrameScript is
version 3.2R1 and ActivPerl is version 5.8.6.811. FrameMaker is version 7.1.
|
|