ViewX not running on server after upgrade from GeoSCADA 2020 to GeoSCADA 2022

[kerro74]

Upgraded GeoSCADA today and all appeared to go well. However, when I start ViewX I get the initial splash screen the it shuts down. Upgraded client and ViewX on client works fine. I have attached the ViewX log file.

Snapshot of error below

2023-05-31 02:48:45.201 Default [1ED8:01] [PrismModule] RegisterTypes (ViewX.Database) : OUT
2023-05-31 02:48:45.201 Default [1ED8:01] [PrismModule] OnInitialized (ViewX.Database) : IN
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] OnInitialized (ViewX.Database) : OUT
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] RegisterTypes (ViewX.Favorites) : IN
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] RegisterTypes (ViewX.Favorites) : OUT
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] OnInitialized (ViewX.Favorites) : IN
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] OnInitialized (ViewX.Favorites) : OUT
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] RegisterTypes (ViewX.HelpViewer) : IN
2023-05-31 02:48:45.253 Default [1ED8:01] [PrismModule] RegisterTypes (ViewX.HelpViewer) : OUT
2023-05-31 02:48:45.262 Default [1ED8:01] [PrismModule] OnInitialized (ViewX.HelpViewer) : IN
2023-05-31 02:48:45.430 Default [1ED8:01] [System.Windows.Application] Uncaught Exception
*** Prism.Modularity.ModuleInitializeException: An exception occurred while initializing module 'ViewX.HelpViewer'.
- The exception message was: The type initializer for 'SchneiderElectric.Scada.ViewX.CefSharp.CefSharpInitializer' threw an exception.
- The Assembly that the module was trying to be loaded from was:SE.Scada.ViewX.HelpViewer, Version=6.85.8390.1, Culture=neutral, PublicKeyToken=9e16b9dd55e2cd53
Check the InnerException property of the exception for more information. If the exception occurred while creating an object in a DI container, you can exception.GetRootException() to help locate the root cause of the problem. ***
at Prism.Modularity.ModuleInitializer.HandleModuleInitializationError(IModuleInfo moduleInfo, String assemblyName, Exception exception)
at Prism.Modularity.ModuleInitializer.Initialize(IModuleInfo moduleInfo)
at Prism.Modularity.ModuleManager.LoadModulesThatAreReadyForLoad()
at Prism.Modularity.ModuleManager.LoadModuleTypes(IEnumerable`1 moduleInfos)
at Prism.Modularity.ModuleManager.LoadModulesWhenAvailable()
at Prism.Modularity.ModuleManager.Run()
at SchneiderElectric.ApplicationFramework.UI.BaseApplication.InitializeModules()

[dahoodman]

Did you ever find a solution to your problem? We have a similar issue that ViewX won't fully load but on 2021. We aren't sure when it started so we don't know if it started when we upgraded from 2020 to 2021 or perhaps after we applied the Dec 2023 updates of 2021 or maybe a MS Update. Interested to know what you found out.

[tfranklin]

There was a version somewhere near there that had an issue with ViewX upgrades related to CEFSharp files not getting cleaned up properly.  I think the CEFSharp files moved from the base location into a nested folder for \Modules\, but there was one release that didn't clean up the old files. 

Check and see if there are any files that start with CEFSharp in the base C:\Program Files (x86)\Schneider Electric\ClearSCADA\ folder.  Validate there are CEFSharp files in the \Modules\ folder.  If there are are CEFSharp in the Modules folder AND also in the base folder, close ViewX, and then delete them from the base folder. 

Other option is to fully uninstall/reinstall, but that's a little more aggressive. 

[sbeadle]

What Trent wrote!

Also, after removing any files you can do a Repair install.

Also - are you sure you:

a) Didn't have Virtual ViewX Server installed, or

b) Did have Virtual ViewX Server installed and you upgraded it too.

If you did have Virtual ViewX Server installed and you did not upgrade it, you can have a similar problem.

[gabarit]

I have encountered this problem many times when I upgraded to a new version of the product.
This is resolved by uninstalling ViewX and reinstalling it or Repair.

[dahoodman]

Yeah the re-install may be our next option. We tried the repair already. Since it's all three of our servers we were hoping to not have to uninstall and re-install. We need to upgrade anyway so I guess this is as good a time as any I guess.