Resolving Automation Interface Connection Failures

[Anonymous user]

📖 Home  Back  

Note: Client side automation is disabled by default for new installations of Geo SCADA 2022 (85) onward for improved security. It can be enabled from the "System Configuration \ ViewX" page in the Server Configuration tool.

There are a number of errors that could appear when connecting to the ClearSCADA database server. When the errors are not trapped in the code, they will display a generic automation interface error such as the one shown below using VBA in Microsoft Excel.

Run-time error '-2147467259 (80004005)':
Automation error
Unspecified error

Connections to the server using the automation interface are performed through the connect method on the ScxV6Server object. This object expects a valid, enabled system (defined in the client connections) as well as valid user credentials. Without these things, the connection will always fail.

To capture the error description in a VB or VBA routine, the following syntax can be used.

'be careful using this line - error handling is now up to you
On Error Resume Next

...

'try and connect
objserver.connect "system name", "username", "password"
'now display any error message
msgbox Err.Description

Cannot find the ClearSCADA system specified

This error is typically shown when the system name defined is disabled or does not exist. Check that the system name used in the automation interface code matches the defined system name exactly. The system name is case sensitive so it is important that it match exactly.

A running server for the system could not be found

This error means that the system name used is valid and enabled, but the server(s) referred to in the connection are not running, then the automation interface will report.

Another reason for this error could be the automation interface being blocked by firewalls in the system, or by invalid network routing. In some cases ViewX may work, but firewalls block the automation interface independently.

Logon Failed

If the system name is valid and the server is running, but the authentication is incorrect (ie username and password), then the automation interface will report a logon failed. Check that the username and password defined permit sufficient permissions in the database.

Go: Home Back