ClearSCADA 2010 R2.1 Known Issues

[Anonymous user]

📖 Home  Back  
Please read the information below prior to installing ClearSCADA 2010 R2.1 for important information on any known issues.

Client Compatibility

• Mimics created in ClearSCADA 2010 R2.1 cannot be opened from ViewX clients running version ClearSCADA 2010 R1.1 and older. This could cause ViewX to crash. This is due the addition of the default text border and graph key font in the newer versions.

Installer

• During an upgrade from an older version to ClearSCADA 2010 R2.1 on a Windows XP machine, the installation of the .Net Runtime component may fail. If this happens, restart the machine and re-run the ClearSCADA 2010 R2.1 installer and the upgrade should complete successfully.

• On a clean installation of ClearSCADA 2010 R2.1, the classes for OPCDA, OPCAE and OPCHDA are not registered. The user would need to open the Client Configuration dialog and click OK on the configured connection for the classes to be registered. This was changed to add support for the Systems.xml file.

Redundancy

• When performing operations such as Delete, Copy-Paste etc on a ViewX client connected to the Standby, the number of links for the Guest user keeps increasing on the Main server. This is due to the Guest user count being maintained incorrectly when proxying requests to the Main.

Please note that this does not cause any memory issues and will be fixed in the next release of ClearSCADA.

Support for Internet Explorer 9

The following problems were identified:

• When clicking on the 'List All Objects' from a class information page in the database schema, the list of objects may not display correctly. This is a problem with the IE9's XSL transformation related to elements with content and children.

• Script functions such as 'Mimic.Inset' and 'App.OpenWindow' may not display properly on IE9.

• Hyperlinks to lists may not display correctly due to the cross site scripting security filter in IE9. This also includes links to trends generated using the TrendSpec specification in ClearSCADA. The workaround for this is to disable the Cross-Site Scripting (XSS) filter in the web browser.

Go: Home Back