Virtual ViewX doesn't load correctly - Shows HTML script in browser
EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-12-1102:03 AM
Virtual ViewX doesn't load correctly - Shows HTML script in browser
Hi,
When I try to open Virtual Viewx in a browser (http://localhost:<port>), instead of showing the login screen for Virtual ViewX, the browser shows the HTML script.
Virtual viewx is installed on a VM running Windows Server 2019 hosted in Azure.
GeoSCADA version 2021 August 2022 Update
Thinfinity V3.0.4.102
Since this is an older version, I dont see the recommended "Create Users on Demand" option so I am using "Use these credentials" option with whatever pre-defined VirtualUI credentials (didnt change the password after installation)
1. What could be causing the browser not to load the application login screen?
2. Will the GeoSCADA 2021 Dec 2022 (Virtual ViewX server) be compatible with GeoSCADA 2021 Aug 2022 GeoSCADA Server?
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-02-1108:39 PM
2. If they are on separate servers, then yes. But recommendation would be to match the versions of your servers and clients as much as possible. This is the most likely combination tested by Schneider / AVEVA by a long metric... if you have mismatching versions then you're really into "it should work, but hasn't been tested" territory.
1. It's possible that this is a security thing. Preventing the scripting from operating, potentially even preventing certain cross origin things from being loaded. You should try to access the VVX server using its hostname from a client that is relatively relaxed on security. If that works, then you need to start identifying the differences... perhaps tighten up some of the security settings on the remote to align with the problematic configuration. Once you've identified what breaks it, undo that configure on the problematic machines...
Lead Control Systems Engineer for Alliance Automation (VIC). All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..