[MSI Interface]: Invalid Token Request

[MSI Interface]: Invalid Token Request

Description

The Werum MSI Interface cannot communicate with the PAS-X adapter version PASX2X v4.3.0 or higher. An invalid request is sent. Thus, the MSI Interface does not receive a token. Therefore, no messages can be sent to PAS-X.

 

This error has been fixed. The Werum MSI Interface now sends requests that are accepted by the PAS-X adapter of version PASX2X v4.3.0. 

 

To benefit from this fix:

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

 



Item ID: 265973
Version: 11.00 Build: 157700
    • Related Articles

    • MSI Interface: The response to an Exception Request includes historic and non historic alarms

      Description If historic alarms should be retrieved from the MSI Interface, the response included historic alarms and alarms which are defined as non-historic. The issue has been addressed and now the response only includes historic alarms. To benefit ...
    • AccessModbus: Process Gateway closes unexpectedly on receiving an invalid request

      Summary When the AccessModbus Process Gateway receives a specific invalid modbus request, the process gateway closes unexpectedly. Description When the AccessModbus Process Gateway receives a specific invalid modbus request, the process gateway ...
    • Checklist: SAP Interface does not work

      Time estimate:  30 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 ...
    • Werum MSI Interface AddIn is not running in zenon 11

      Description The Werum MSI Interface AddIn does not work in zenon 11 if the simulator is not running on the same computer. If an IP is defined that is not on the same computer, the web server contained in the AddIn will not start. This error has been ...
    • [MSI Interface]Too many Exception Messages are sent

      Description If the “Alarm acknowledged” option was used for alarm-based exception messages, a message was sent incorrectly when the alarm occurred. The issue has been addressed and wrong shipments are no longer executed. To benefit from this fix: ...