What should I check if Virtual ViewX does not work?
The Release Notes for Geo SCADA 2019 provide a comprehensive guide for setup, particularly when upgrading systems. It has advice to help you upgrade to Virtual ViewX.
Please read the following sections for additional guidance.
Earlier Versions - The 'Prepare' Step
Have you remembered to execute the 'Prepare' step? This is necessary on Geo SCADA 2019 Initial Release and the January 2020 release. Find this on the .ISO image installer main page, under the Virtual ViewX installation link.
If Virtual ViewX does not appear in the list of applications tab in Virtual ViewX manager, then Prepare has not been run.
You must reboot before the prepare step, as advised by the Virtual ViewX installer.
We advise you to use a later version of Geo SCADA which does not require this step.
Setup for Performance
We recommend that when more than 5 clients are to be run, you check and set the session properties in Virtual ViewX Manager.
These are the 'Mode: Multiple browser per session' setting and set the Session count to 5. (Later versions set this up automatically).
The image here shows the settings needed:
Annotation 2020-10-05 145049.png
If using more than 10 clients per server, you also need to increase the number of client advise ports accordingly. This is simply set using the Configure Connections tool in the start menu. Set the range to include the maximum number of clients you will need to support. Note that this need only arises if the Virtual ViewX Server is Geo SCADA 2019 or the SCADA Server is Geo SCADA 2019.
The example below shows a range of 5500 to 5519, suitable for 20 clients.
Setup for Security
Important.We recommend that you restrict address parameters from the client browser, as required by the security notification SEVD-2020-343-02. From the Virtual ViewX Manager app, find and double-click the VirtualViewX application in the list below:
Then UNCHECK the setting 'Allow Browser Arguments':
Virtual ViewX uses a 'Disconnected Remote Desktop Session' which means that it can be terminated if a Registry or Group Policy setting is incorrect. Virtual ViewX manages its sessions, therefore the Windows setting should not be used to apply a time limit.
The registry setting is:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal ServicesMaxDisconnectionTime - key should not be present.
The Group Policy Setting is:
Remote Desktop Services | Remote Desktop Session Host | Session Time Limits | Set time limit for disconnected sessions- state should be 'Not Configured'.
Windows 10 Operating System Support
Virtual ViewX uses the Remote Desktop technology within Windows to help create its displays. This means that there are some limitations within Windows 10 support of Remote Desktop which change the behavior of Virtual ViewX when you use a Windows 10 operating system PC as the Virtual ViewX Server.
On Windows 10, the Virtual ViewX setup will use the console user as the 'host' for the server. This is implied by the blank settings here:
So when a user logs in to Virtual ViewX, it is important that a user is logged into the PC console - either by the screen/keyboard locally or remotely via a remote desktop connection. If no user is logged in, then the Virtual ViewX session may return an error or may display only limited screen content.
Should you wish to create a user manually to remove this restriction, please create a new user, set a password and enter credentials into the same box:
(Note that should you change a PC's name, the credentials here and in the Applications | ViewX tab also need to be changed).
Then you can use one or more Virtual ViewX sessions without the console user being logged in. (Note that if a console user does log in then current Virtual ViewX sessions are logged out automatically by Windows, but they are permitted to log in again straight away).
Licensing and Installation
Once you have used a 'real' license, you can not then install a demonstration license.
For good results, a demonstration license needs a new, unique email address each time you create one.
Read this particularly if you see 'Error 1327' appearing after login.
There are two windows accounts used by Virtual ViewX. Use the Administrative Tools | Computer Management application to check these. Open the folder Local Users and Groups | Users. Check that the two users 'VVXLocalUser' and 'VirtualUI' users have 'User must change password at next logon' clear, 'Account is disabled' is clear and 'Password never expires' is set.
For each of these users, change their passwords to a suitable long and complex password. Do this by right-clicking them within the users list.
Check that the VVXLocalUser is a member of the Users group. Check that the VirtualUI user is a member of the Remote Desktop Users group.
Then use the EcoStruxure Geo SCADA | Virtual ViewX Manager application to set up these passwords in Virtual ViewX. Do this on the Sessions tab for the user VirtualUI (check the domain), and do this also for the VVXLocalUser user, which you will find on the Applications tab - (a) double-click the Virtual ViewX entry in the table and then click 'Credentials' in the form which pops up.
On Windows Server
Virtual ViewX uses a port internally, set up using the Virtual ViewX Manager on the first tab. You may choose a 'Bind to IP' setting of 127.0.0.1 to restrict access to this local PC (recommended).
Please check this setting if you have problems - the port must be set to 6580. This port is dynamically routed to an Internet Information Server port using ports 85 and 453 by default. You can configure these externally facing ports using the IIS Manager application.
Should you wish users to bypass IIS and use the internal Virtual ViewX port directly, you may simply disable the IIS ports and reconfigure the 'Bind to IP' setting and port number using the Virtual ViewX Manager application.
On Windows 10
Virtual ViewX uses a port set up using the Virtual ViewX Manager on the first tab. You may choose a 'Bind to IP' setting to allow that address to be used by clients.
How do I enable Virtual ViewX Logging?
In order to enable the logs for VirtualUI please follow these steps:
- Stop VirtualUI Service - Create the '.ini' files below and paste them to the "bin64" folder.
- Edit the .ini files and select a different output directory for each. - Make sure these output directories exist and are writable. - Start VirtualUI services. - Reproduce the error. - Stop VirtualUI services. - Send the *.sil files generated to the TRSS support team.
If the support team request maximum logging, enable with this line in each of the three ini files: logtypemask=$7FFFFFFF
There is an additional log feature you can enable using the Virtual ViewX Manager application. Find its setting in the 'Folders' tab. Click 'Enable Logging' and enter a suitable log folder name.
Upgraded Windows Servers
If your server was upgraded at some time from a previous Windows Server version, there may be a need to run an additional step to prepare the server.
The symptom is 'Error 5, Access is denied' when you try to use Virtual ViewX. This issue occurs because the discretionary access control list (DACL) for the Secondary Logon service is not set correctly when you upgrade from Windows Server 2003 or from Windows Server 2008. This problem prevents a standard user from starting this service and from running an application as a different user.
To solve the problem, please execute the following command from a cmd prompt window:
net stop seclogon
sc sdset seclogon "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWRPDTLOCRRC;;;IU)(A;;CCLCSWDTLOCRRC;;;SU)(A;;CCLCSWRPDTLOCRRC;;;AU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
Make sure to copy this command correctly, including the quotation marks.