Fully Qualified Domain Name is wrong in MQTT client for Editor/Runtime/Drivers

• Related Articles

• SQL connector to linked server does not work with FQDN ( full qualified domain name )

  Summary SQL connector and 3rd party connector are now capable of working with linked server names that contain the dot (.) character. This character is usually used in fully qualified domain names for computers. To deploy this fix: Install a build ...

• Checklist: Client/Standby cannot establish a reliable connection with Service Engine Server

  Time estimate: 45 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: What are Installation and Security considerations of the zenon Smart Server and Smart Client?

  The attached document (English only) describes in some detail the specifics of the zenon Smart Server Application and the zenon Smart Client Application. Also a short explanation of security features and components is given. More information about ...

• Straton to zenon Runtime connection handles special characters in variable names wrong (cross effects on name related variables in Runtime)

  Summary Straton to zenon Runtime connection handles special characters in variable named wrong (cross effects on name related variables in Runtime) Description Straton to zenon Runtime connection handles special characters in variable named wrong ...

• Checklist: Smart Client cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the items in the following checklist. If necessary, confirm any information you cannot verify with the IT department before contacting your local COPA-DATA representative. Checklist usage: #. [Quick ...