SE crashes if printer is not reachable

SE crashes if printer is not reachable

Description

When printing via the Report Viewer, the zenon Service Engine was closed unexpectedly if the printer was not available.   
The issue has been addressed and the Service Engine behavior is now as expected.  

To benefit from this fix: 
  • Update your zenon Software Platform to the latest build of zenon 11 or higher. 



Item ID: 299509
Version: 14.00 Build: 405141
Version: 12.00 Build: 407620
Version: 11.00 Build: 400376

    • Related Articles

    • SE: ETM - zoom out completly on Y axis - SE crashes

      Description The zenon Service Engine closed unexpectedly after a zooming out procedure in the ETM screen. The issue was triggered by trying to extend the time range beyond Year 2038, where the traditional 32bit signed integer wraps to -1. The ...

    • Checklist: Printer does not print

      Time estimate: 15 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Printer is switched on, is online ...

    • zenon Smart Client freezes on Printer Selection

      Summary Using a Smart Client may lead to freezes of the Client PC if you open the Printer Selection of the Screen Specific Function "Print with Dialog" of the AML or CEL Screen. New Printer Dialog was implemented to fix this. Issue Number: 251643 ...

    • zenon Smart Client freezes on Printer Selection

      Description In the Smart Client, opening the printer selection via the “Print with dialog” screen element in the AML or CEL screen causes the computer to freeze. This freeze can last for some time before the computer becomes operable again. The ...

    • SE on Client, with network delay to the Server, crashes when opening the Command Processing Screen.

      Description The Service Engine on a Client with a network delay to the Server closed unexpectedly when the Command Processing Screen was opened. The issue has been addressed and the behavior is now as expected. To benefit from this fix: Update your ...