Skip to content

Known Issues

The following are the known issues as of 06/25:

Industrial Edge Management

Issue Troubleshooting Affected versions
Large RSA keys in certificate chains can cause a client to expend significant CPU time verifying signatures. In case you experience this behavior when using the IE State Service, it is recommended to reduce the size of the RSA key in your certificate chain. -
Deleting a configuration of the IE Databus and the SIMATIC S7 Connector by clicking the "Delete Configuration" button under the "My Installed Apps" menu item starts a task on the according Edge Device but fails immediately. - -
Connecting an Edge Device to the IEM fails and the "Nginx configuration test failed" error message is displayed during activating the Edge Device phase. Check the DNS server configuration since the error message is DNS server related. The DNS server must be configured properly and reachable for the IEM. -
If an user creates an "Admin Group" and adds devices to it these devices will not only show up under "My Edge Devices" but also under "Authorized Edge Devices". The user automatically gets the role for the created "Admin Group" assigned. You could remove the role for the group in IAM. -
Field mac_address in apps docker compose is ignored. This is a bug of Docker Engine resolved with devices that use Docker Engine greater than 24.0. -
If the user does not have sufficient access rights to Identity & Access Management, the Identity & Access Management application will not load and the cursor will not stop. This error means that the user does not have permissions to work with Identity & Access Management. If you want to enable this for the user, you can follow the description in the "Assigning Roles" chapter and add the "realm-management - realm-admin" role to the user. -
If an Edge Device with a scheduled/active firmware update job is deleted from the IEM, the Edge Device itself may become unstable. Before deleting a Device from the IEM, make sure there is no scheduled/active firmware update job on the Device. -
Do not delete the user who has mounted a Device. If the user is deleted, no applications can be downloaded to the Device because the Device cannot authenticate to the IEM's Docker Registry. - -
The email and username values are case-sensitive and will be automatically converted to lowercase in certain system components. To ensure proper functionality, always provide email and username values in lowercase letters. -
With IEM Pro v1.12.11 the USB-onboarding of an Industrial Edge Device fails. This issue is caused by the introduction of a new file name and a new value called expirationTime within the file.
There is a workaround in place you can use to overcome this situation:
  • Rename the onboarding file to device-<deviceId>, e.g. device-02ab9064847d4aba9106b7ac1064b8be. The deviceId is part of the onboarding file.
  • Remove the line "expirationTime":"1" from within the onboarding file.
Instead of the workaround you can also apply the hotfix IEM Pro v1.12.12.
1.12.11
Job manager behaviour on application installation if application config detail is not updated to IEM According to the Job manager design
  • The job may fail if it cannot update the deployed configuration details on IEM. Nevertheless, the configuration is successfully downloaded, and the application starts working on IED.
  • The job will be marked as failed initially, with the option to retry. Upon retry, the job will be completed successfully.

Industrial Edge Management Virtual

Issue Troubleshooting Affected versions
Software Update: When too many IEM Apps are installed, the update process might fail due to CPU resource restrictions without showing the reason. In particular, the update from version 2.4.x to 2.5 fails. Assign at least 8 CPU cores to the system and retry the update. Alternatively, uninstall IEM applications to reduce resource usage; they can be reinstalled after the update completes successfully. 2.4.x → 2.5
Software Update: For some IEM Virtual instances, the update stalls when bandwidth is limited. If an IEM Virtual update stalls due to limited network bandwidth, use the recovery key to access the Service and Maintenance applet through port 4443. You'll see the update in progress; cancel it to revert to the previous version for continued operation. Increase the bandwidth before attempting the update again. A solution to facilitate updates with limited bandwidth is under development. -
During an IEM Virtual update, "Unauthorized Access" and a Login button may appear, with the version still showing as the previous one. Refreshing the page may lead to errors like "The service is currently unavailable" and "The request was not carried out due to the client's lack of authorization."
  • Login using the Recovery key on port 4443
  • If errors persist, refresh the SaM UI page until the update progress reappears.
  • The Service and Maintenance UI will show the update process if it is still running.
  • After a few minutes, the update should complete, and all applications will become accessible.
-
Software update logs are not appearing in the Logs console after an OS update.
  • Due to authentication timeouts during the update process, logs might not be visible during the whole process.
  • Start the update via port 4443, this will show the logs during the update process.
-
Helmchart version in the OS Bar or IE Hub may not be displayed correctly after updating from 2.3.x A synchronisation problem introduced in 2.4.0 prevents the Helmchart version from being updated in the Hub or OS Bar. Reboot the virtual IEM to fix the problem. 2.3.x → 2.4.0
DHCP: When using DHCP, make sure to always assign the same IP address to the IEM Virtual. Not doing so will result in an unreachable and unstable system. Assign a fixed IP address to the IEM Virtual instance. Ensure the DHCP does not dynamically change it. -
If an FQDN is provided, the IEM-APP cannot be reached via IP address anymore, only via the hostname. Ensure that the DNS server is available and working before providing an FQDN name. -
Network Limitations: Some network or proxy settings cannot be changed after onboarding. Keep the IEM Virtual instance up to date. This functionality will be available in upcoming versions. -
Newly configured IEM Virtual displays errors on first login or after reboot. This issue occurs because not all services are fully initialized. Wait a few moments for the services to start, and the errors will resolve themselves. -

Industrial Edge Virtual Device

Known Issue from 20.01.2024:

Users may experience issues when attempting to update IE Virtual Device connected to the IEM Cloud due to a certificate issue. However, this issue has been resolved in the latest release. We have provided a workaround to ensure a successful update. Please refer to the table below to identify the scenarios where this workaround is required.

From To Affected
1.8.0-4-b 1.11.0-4-a yes
1.10.0-6-a 1.11.0-4-a yes
1.11.0-4-a 1.12.0-3-a yes
1.12.0-3-a 1.16.1-1-a no

Workaround

  • Step 1
    Download the "IEM CA Certificate" file in the Industrial Edge Management UI. It can be obtained in the Device Menu clicking on the three dots of the target device. The button is shown in the image.
    First step

  • Step 2
    Import file to Industrial Edge Device. Therefore navigate to the System tab in the Settings menu. Then use the button "Import Certificates to IED Truststore" as shown below.
    Second step