I was nervous applying a “file overlay” patch so I tested it on a test system running the RC. Everything seems fine.
Then I did the same thing on my demo system. Then I ran a perspective session and it loads the login screen as usual. When I hit the button to log in I get a server error (HTTP Error 500). I can run instances of perspective sessions on my test system so I am definitely having problems on my demo system that I didn’t have on my test system.
Here are some more details on what isn’t working on the demo system…
I can log into the config website no problem. I downloaded and installed the designer launcher from the config site.
I tried running designer launcher. I get this error
with the details…
I browsed to the project files and they appear to be intact. I don’t know which specific part has the project manifest but I copy/pasted my entire data directory to another system before doing this upgrade so I should have it. I also have a gateway backup and tag database dump.
Let me know if you need any other details. I’m interested in any steps I need to perform to fix my demo system.
Designer launcher was downloaded from the upgraded system.
I pivoted to do some development on my test station because it can launch a perspective session and I noticed that it doesn’t have a perspective module in the designer. I think I need to load that module independently. Trying that now.
I uninstalled the designer and deleted my cache (deleted the .igntion folder) on my test station which is able to go into the designer under 8.0.1 but not able to see the perspective module. I used the batch files in the install root to restart Ignition. It still can’t see the perspective module in designer. I see the module from the configuration website.
I haven’t tried anything new on the other station that can’t open designer.
Both systems are able to get to the internet so I could share my screen if you want to look into things.
I just want to confirm that when you say “file overlay” patch you are talking about upgrading using the zip installer. If so, are you certain you deleted the lib folder when upgrading your demo system? I know it is something that happens to me every once in a while an leads to issues like this.
I don’t know of this zip installer thing. Where do I find it? Also, what are my recovery steps?
Edit:
To be clear. I stopped ignition, opened the zip file and drag dropped the files into the application root. I told it to overwrite all files. Naturally, that made me nervous so I backed up everything.
Based on the steps you provided, you were using the ZIP file installation method of Ignition. Based on the steps provided, you missed one very important step of deleting lib folder in the current installation after stopping Ignition. There should be a README file in the ZIP archive that contains the upgrade instructions, but here is an example from the Windows ZIP archive:
Upgrading existing installation *
If you have Ignition running out of a previous unzipped folder, and you would like to upgrade, follow these steps:
Take a Gateway backup from the running system and store in a safe location.
Stop Ignition. Run stop-ignition.bat
Delete the Ignition lib folder.
Unzip the new zip into the current folder and allow files to be overwritten.
Unzip the new jre-win runtime in lib\runtime
The data/ignition.conf file may have changed if this is a major upgrade. To update it, run this command in a terminal in the ignition folder:
lib\runtime\jre-win\bin\java.exe -classpath “lib/core/common/common.jar” com.inductiveautomation.ignition.common.upgrader.Upgrader . data logs file=ignition.conf
Start Ignition. Run start-ignition.bat
To fix this situation, just rerun the upgrade (same ZIP archive) follow the instructions making sure to delete the lib folder before dragging/dropping the files. It will ensure you have the correct versions of libraries needed are deployed for Ignition to run smoothly.
I didn't notice the readme file. I guess the most important step was reading that lol
I applied these steps to both servers. My test station now sees perspective in the designer and client appears to work.
The Demo station that was getting the error from the screenshots above gave me this error on step 6 but can now run a runtime. I haven't looked over things enough to know if it's completely fixed but I think it is.
Thanks for your help (both of you). I think you can close this one. I'll let you know if anything else is broken that I haven't noticed yet. I think it's all good.
