Visokio website     Downloads     Video tutorials     KnowledgeBase  
Printing: PDF output layout differs when running as Scheduler task? - Visokio Forums
Printing: PDF output layout differs when running as Scheduler task?
  •     enrico68 July 1, 2014 10:27AM
    We have to produce a PDF document containing different outputs (graphs and tables) from a .iok file. However, we obtain two different output results, depending on whether the output PDF production process is launched manually from an open .iok file (containing an Output as PDF block) or if it is launched from a Scheduler Task List process (containing a 'Publish DataManager Output Blocks' command).

    We opened the .iok file on the same Omniscope server where the scheduled process runs (Omniscope Server version 2.8 b1216 is installed) and looks like that trying different online page settings (xga, svga, ..) does not have an impact on the Scheduled process behaviour.

    In the attached file, it is possible to see an example of the different layout observed: when produced manually from the .iok file, the table reported is completely visible; when produced by the scheduled output process the table is not completely visible.

    It seems to me that scheduled process uses different page dimensions and configuration settings to produce the PDF file?

    The desired result is obviously to have the same PDF output in both production methods: manual and by scheduled process.
    Sample page.docx 866K
  •     enrico68 July 1, 2014 10:30AM
    Sorry, this is the correct sample file.
    Sample page.docx 902K
  •     donald July 1, 2014 2:42PM
    Can you confirm whether the scheduler is running as a Windows service ?

    If so can you try the following
    1. Log onto the server console GUI as the licensed Omniscope user.
    2. Stop the "Visokio Enterprise" windows service.
    3. Run Omniscope Server on the console.

    The scheduled jobs should run as normal and we will be able to compare the "windows service" scheduler output against the "console GUI" scheduler output.

    You will have to leave the user logged onto the console whilst Omniscope Server is running like this, if connected remotely then "disconnect" to leave the scheduler running.

    Once you have generated outputs for comparison you can resume running the scheduler as a Windows service.

    4. Exit the Omniscope Server program on the console GUI.
    5. Start the Omniscope Enterprise windows service.
    6. Log off the server console GUI as the licensed Omniscope user.

    We have checked the behavior and can reproduce the problem. When running Omniscope Scheduler as a "Windows service" the "virtual screen" size which is used to generate the pages is being restricted to a "Screenshot size" of xvga or lower.

    This will require further investigation by our developers.
  •     enrico68 July 2, 2014 3:58AM

    I confirm that scheduler is running as a Windows service.

    I did the test and I can confirm that running the scheduler using the console GUI produces the correct report.
    So the problem is related to the scheduler Windows service.
  •     steve July 2, 2014 5:22AM

    This is a known limitation of scheduled printing under the Windows service. There is no solution at present other than to adapt your report to smaller screen sizes.

    Instead of using the Windows Service, launch the Server/Scheduler app in a full login session. It's possible to configure Windows to auto-login and launch apps at startup, so this may be a viable long-term solution for you. If you need help with this, let us know.

  •     enrico68 July 3, 2014 6:22AM

    we are using the workaround you suggested and we are able to obtain readable PDF.


It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership