I'm encountering a problem in Ignition Designer – I can't access views. Initially, I can open it, but upon closing and reopening, I receive the following error message:
ExecutionException: java.lang.Exception: Unable to get the view config: View config is undefined.
caused by Exception: Unable to get the view config: View config is undefined.
I've tried a restore using an old backup, but to no avail. I also uninstalled and reinstalled Ignition, cleared the cache, yet the error persists. Any insights or suggestions on resolving this would be greatly appreciated.
I am using 8.1.32
I encounter this issue exclusively on this particular gateway. When utilizing the views on other gateways, I do not experience the same problem.
The gateway is hosted on a server. I'm concerned that restarting the server might cause potential disruptions or failures.
I've had this same issue for a while now. I created a ticket and was told it's a known issue but they are having trouble replicating so they can't narrow down the root cause.
For me, performing a save will sometimes make it open. Also, restarting the Perspective module might help, but I don't know what ill effects that may have.
FWIW, I downloaded a copy of the designer launcher from the gateway which is a slightly different version and I have not had it happen again. I wondering if the designer launcher version vs. gateway version plays a role?
Seems to be an issue when a view has many many custom properties.. I have to try at least 25 times to open a particular view before I can finally get it to open.
Adding to the conversation here. I am new to Perspective but very long time Vision expert. 1st post on these forums too. Love Ignition 7/8 (Vision). Still on the fence with Perspective.
The below is my development PC. The SCADA PC matches.
The mentioned issue happens sort of randomly. When this issue surfaces the only way I can open a/any view is to close the Designer then open it again. Once I do the restart of Designer it is okay for a random amount of views to open.
I can use either Save + Exit or Exit and both have the same effect. Meaning that when the java error surfaces it is not a corrupt project. As stated below the view popup by mouse hover shows the view. The issue is only opening the view (consistently in my case....both PCs). So, this is most definitely a Perspective issue.
I think I may have noticed something that may cause this. I will bullet this below to help IA try to fix this painful issue.
The hover view display shows the view popup. So the JSON is there and the view is still in the projects.
I double click on the view to edit it. Usually (99.9%) the first view (tab) opens for editing.
I double click on the 2+ view to edit it (I copy and paste from templates). This is when the issue surfaces. The entire view is basically white and will not open. I have to click the X to close the view then the error popup shows.
My views are K.I.S.S. style SCADA. Meaning I make my background in GIMP so the entire background is 1 image (1920x1080). This eliminates graphic hitches.
The Data, Icons, and Switches are standard Ignition objects with the only custom things is the Visible Binding tied to Tag or Security.
I do use the Text Styles as well for ease of formatting.
That is it.
IA, Please fix this. I hope this information helps you folks fix this.
*TLDR: * This is a current Perspective Bug (big/bad one). It is easy and common for SCADA PCs to be Ryzen 9 class with NVME. There is no reason Perspective should not work with these modern CPUs. Vision does not have this issue. I recommend that Vision is used until IA publishes a fix for this.
Working with Beatriz (IA Support) we found that it is something to do with objects (mostly Labels at this point) with Bindings (Data Tags) and the speed at which those Bindings are loaded in the CCS format Perspective is using.
We found that the quantity was around 25-ish for the Ryzen 9 6900HX (see more info below).
We also did a Wireshark test to look at the Bindings load and it always failed at -1 of the Bindings on that page. Example: If there are 30 Labels with Bindings Wireshark would show failed at 29 iterations.
Example:
I am/was developing on my new Ryzen 9 6900HX and this is where the issue appears 100%.
On my customer's PC, Ryzen 5 5560U this does surface but does so more rarely. It depends upon the number of objects with Bindings. Denser pages will show this issue.
My work laptop, Legion 5 Ryzen 7 5800H, this issue surfaces like the Ryzen 9 but more randomly. Almost like some sort of edge case.
The above is 100% replicable.
Vision does not have this issue (any issues really). It is relatively easy to switch the license from Perspective to Vision with IA. A nice phone call with your IA account manager (Sales) can make this happen.
Most things are the same except the Vision vs Perspective module.
Displays and things are different and cannot be copied and pasted between Vision and Perspective but a rebuild is not difficult (in my opinion).
Vision is super reliable and robust.
Final note.
I 100% understand that Perspective is the direction forward. I was pleased with how well the web page tabs worked in Edge. It was snappy and looked great (same as Vision with my graphics package). Containers in Perspective suck, especially compared to how brilliant the Vision Grouping is. Tag Binding in Perspective is easy and the Styles work great.
We have two more customers for SCADA and we will be sticking with Vision. It is 100% reliable and robust. Vision is not going anywhere and now that I am almost 58 our company will stick with what works.
Just wanted to send a quick follow-up to this issue. (Also, posted here)
All tickets that went through support and were linked to the internal bug ticket had the same preceding error in the Designer console. This error showed the rootViewDefaultSize being undefined and resulted in the view not loading. Then when closing the view, the Unable to get the view config: View config is undefined error message would be displayed. The root cause was determined to be a race condition when opening views. A fix has been merged and will be available in 8.1.44.
If anyone is consistently seeing this issue, but have a different error unrelated to the rootViewDefaultSize the best course of action would be to reach out to support for further investigation.
