Unknown error when addressing a point in script

[HHJ]

Good day, we imported a project from a 2019 version into Geo SCADA 2020. When executing a script it gives an error at the first line where a point is addressed. E.g. dim UnitNo and then UnitNo = Server.GetOPCValue (".UnitNumber") It works well on the previous system.

It is the first time we are using the new Windows Server (a very new version).

Is there a setting we may have missed? 

Thank you,

Hartmut

[HHJ]

I don't see any replies to my post (hope it's my own stupidity). However the problem was caused by a new security feature (since Geo SCADA 2019) regarding WebX. It's about certificates and the default setting killed my scripts. 

[BevanWeiss]

I suspect that you don't have the firewall rules / WebX script ports configured correctly.

You will need to allow firewall for port 443 (or other configured HTTPS port), and have appropriate settings for the scripting (on clients) to utilise this.

You haven't mentioned whether you'd tested this on a ViewX client local to the server, but my suspicion is that this works fine, and it's only on remote clients that you have this script problem.

[bamador]

Hi HHJ,

I just had to deal with this on my ViewX clients as well for script interface calls. You'll have to goto "Internet Options" in control panel. Navigate to the "Advanced" Tab and  scroll down in the Settings panel. Then Enable TLS 1.0 and TLS 1.1. 

I believe in Geo SCADA 2022 (when released) this will be handled through IIS so in the future you won't have to deal with this.

Here is a link to the Microsoft article about it: https://support.microsoft.com/en-au/topic/kb5017811-manage-transport-layer-security-tls-1-0-and-1-1-... 

[HHJ]

Thanks to everybody who replied. What you suggest makes sense, but actually I solved the problem (5 weeks ago) by going into Configuration/System configuration/WebX. Under Security, there are more options than we had in Geo SCADA 2019. Unfortunately, my laptop runs on 2019, which does not offer the new security options - so, I can't give you the details (the new servers are already installed at the plant). It had something to do with certificates. 

[geoffpatton]

@bamador 

Thanks I just read this yesterday and today a customer called with one client machine that just started having this problem. TLS 1.0 and 1.1 were not set. The strange thing is that computer has been working for years. Probably something Microsoft pushed out to protect us from ourselves and unchecked them.

[bamador]

@geoffpatton 

It is definitely a security issue that they released on the last October 2022 updates. They don't want people using TLS 1.0 or 1.1 like Geo SCADA uses currently. TLS 1.2 and greater is pretty much the standard now. Glad my comment helped you out.

Regards!