Reporting Studio connects to broken databases
Description
If the Report Engine
database contains metadata tables with invalid column definitions, the Reporting
Studio indicates errors but will nevertheless establish a connection. It is
expected that Report Studio will not establish the connection if errors are
detected.
This bug has been fixed. The database validation has
been corrected and Reporting Studio now abortes the connection if
the database structure definition is not fulfilled.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 12
or higher.
Item ID: 284323
Version: 12.00 Build: 272744
Related Articles
Checklist: Error connecting with the Report Engine database in Reporting Studio
Check if the zrsLicSrv service (Report Engine License Service) is running in Windows Services/Task Manager and the corresponding (default) listening TCP 50779 port is open and listening for incoming connections -> to do this, start the Command prompt ...
FAQ: What is the difference between the Report Viewer and the zenon Reporting Studio?
A detailed description of the differences can be found in the attached PDF documents (English and German). The description is based on zenon Supervisor 7.50 and zenon Analyzer 3.00.
Checklist: Software-dongle is broken
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. Checklist usage: #. [Quick hints] ...
Reporting Studio shows SG connection state in status bar
Summary In the status line of the Reporting Studio, the connection status of the Report Engine Server and the Reporting Studio to the IIoT Services is now displayed. Description Possible states for the connection status: No connection established ...
Checklist: Hardware-dongle is broken
Time estimate: 5 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. Checklist usage: #. [Quick hints] ...