Service Grid Ingress Connector causes Service Engine to crash when a Historian request is aborted

• Related Articles

• Service Grid Ingress Connector causes Service Engine to crash when a Historian request is aborted

  Summary The crash was caused by a wrong object access in cancelling running historian requests when the Data Hub connection is lost. The object access has been corrected and the crash no longer occurrs. Description The crash was caused by a wrong ...

• FAQ: Historian configuration general recommendations

  1. Recommendation on hardware: Storage Memory CPU - SSD (Solid-State Drive). - Disk space capacity as detailed in the attached Excel sheet outputs. - RAM required to load the archive data is about 4 times greater the size of the respective ARX files. ...

• Checklist: Data Missing in Service Engine

  Time estimate: 60 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] ...

• FAQ: How can I backup the Service Engine data, the data created during Service Engine?

  The path of the Service Engine folder can be amended in the project properties and it is set into zenon6.ini (VBF30=) when the start project is set in Engineering Studio or in zenon Startup Tool. In the Service Engine folder, there is the subfolder ...

• SG Ingress Connector: reload issue - consumer receives no values until timeout

  Summary The contents of the Service Grid Ingress Connector started up before the connection to the Data Hub was entirely established. Thus, not all objects were correctly connected and the Web Engine request for advising variables was rejected. Now, ...