API Error when running Instance Wizard (GSK)

API Error when running Instance Wizard (GSK)

Description

If a Smart Object instance is created with the Instant Wizard (GFK) and removed again with this wizard, an API error occurs when another instance is created. The error message refers to: "Attempt to read or write protected memory."

This error has been fixed. The Instant Wizard (GFK) works again as expected.

To benefit from this fix:

  • Update your zenon Software Platform to the latest build of zenon 11 or higher.

 



Item ID: 272440
Version: 12.00 Build: 206562
Version: 11.00 Build: 201786

    • Related Articles

    • zenon Changesets Excel

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

    • zenon Changesets CSV

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...

    • Smart Object API : Variable mapping not applied after changing in engineering studio

      Summary Changes in the variable mapping of a Smart Object instance are not applied during CSV export via SmartObject Export Wizard. This behavior has been changed. Description For a new Smart Object instance, variables are mapped in the Engineering ...

    • WebEngine Deployment - IIoT Service Connection Wizard can't be started

      Summary When deploying the HTML Web Engine, an error message is displayed that refers to a missing service. This message has been made more precise. Description An error message is displayed when deploying the HTML Web Engine. This indicates that no ...

    • zenWebClientStarter duplicate start / crash while opening filter dialogues - Exception code E06D7363

      Description If the Smart Client is started more than once on a system, the Smart Client is not running correct. A multiple start can also occur unattended if the Smart Client is started but the previously terminated instance is still active. This ...