Upgrading from v7.8.3 to v8.1.35

I know this was probably a leap of faith thinking that an upgrade from v7.8.3 to v8.1.35 would be smooth but here I am. The upgrade process started well by stopping the Ignition service and backing up the gateway. But that's about the extent of the upgrade success story. From that point I received an error "Unable to extract install into 'C:\Program Files\Inductive Automation\Ignition' The install will be reverted." After clicking on OK it proceeded to undo what it had accomplished ending with another error, "Unable to copy the log file from 'C:\Users\Kevin.DeYoung.ignition\install\install.log' ".

I am able to manually uninstall v7.8.3 and manually install v8.1.35 but that eliminated the action normally carried out by an upgrade.

Is this upgrade possible or are the intermediate steps that need to be taken to accomplish this process?

Restore the v7.8.x gateway backup into the fresh install of v8.1. That should perform the upgrade operations. You will likely need to tweak ignition.conf afterwards, and likely upgrade your JDBC drivers, too.

So in short there is no direct upgrade that can be applied. Kind of what I figured. Thanks for the feedback.

I mean, the upgrade by directly running the installer should have worked. You're more than welcome to file a support ticket so we can collect more information and see about fixing it for the next person - but if you're just interested in getting up and running, Phil's approach will accomplish exactly the same end result.

Thanks Paul. I'll follow that path too so we can get to the bottom of the issue. I'd feel more comfortable knowing what's going wrong.

1 Like

Paul, for whatever reason, maybe phase of the moon or solar flares, when the upgrade was attempted today under the scrutiny of support it worked flawlessly. I have no idea what the difference today versus yesterday is but it worked.

4 Likes

@kevin.deyoung I just read this thread, and I had a similar issue with updating from v8.1.28 to .35...which isn't even a major leap, but it still refused to move past that error screen. I left it and got to troubleshooting through that a day later and it worked so I just assumed I was the crazy one. Glad to know I'm not. :slight_smile:

Did you happen to capture the install.log file from the failed upgrade attempt?

It wasn't able to write that either. That was the final error. So no I didn't.

Glad to know it's not just me that sees these oddities.

I did see that. I was hoping @Estera_Cioroch may have been able to grab one.

Did the server happen to get restarted between upgrade attempts?

No it wasn't restarted/rebooted.

@avaughn unfortunately I didn't, mostly because I didn't think much of it since it installed just fine the next day. Is the log file something that could still be retrieved though (does it store system logs for all time or does it refresh)? The only complication is that in the past month I've changed PCs, but if you really need it I can try to hook it up and get that file anyways.

There should be a new log file for each attempt. No worries if you don't have it though, I was just trying to see if you were seeing it fail at the same point during the runtime extraction as mentioned in this other thread.

1 Like

In my case I walked through the folders with support and were not able to find any trace of the log file from the failed attempts. The last error that was generated during the failed attempts was one indicating it wasn't able to generate the log file.

Were you looking in the install directory? Or the .ignition directory created under your user? The install log should be saved to your user directory under .ignition\install and then copied to the install directory.

Also, did anything show up in the system logs when the install failed or the install log failed to copy?

We looked in several locations for the log file but don't recall the details. at that point support was driving. We didn't look in the Windows logs at all.