Orion 2022.3 - Configuration Wizard Error - Invalid Column Name NodeID

***Edit: Together with support, we identified that the NTA module (which we had installed at some point and then removed) had leftover remnants in our DB. Support provided a clean up query, which after ran, the configuration wizard completes the upgrade without issues. I am leaving this post here in case anyone else ever runs into this during an upgrade, and as always, be sure to have working backups - thank you to SW support for the assist!***

Upgrading our Orion 2020.2.6 deployment to 2022.3 and the configuration wizard keeps failing at around 5% with the error message:

Database configuration failed: Error while executing scripts - Invalid column name 'NodeID'.

Invalid column name 'NodeID'.

Invalid column name 'NodeID'.

Invalid column name 'NodeID'.

Invalid column name 'NodeID'.

Invalid column name 'NodeID'.

Then the only option is to quit the configuration wizard, which leaves the entire deployment unreachable.

We've tried both an upgrade and a clean uninstall/reinstall, both of which ended with the same error. I tried telling support this would be the case since it fails on the database scripts, not the platform installation, but they pretty much ignored me and kept asking me to do a clean install. The clean install failed in the same spot (as expected).

Has anyone else seen this in their 2020.2.6 > 2022.3 upgrade?

Find more posts tagged with

error

2022.3

configuration wizard

Accepted answers

Kita

We will provide a NTA clean up tool which should help.

All comments

Kita

It is likely a database clean up that is needed to upgraded to 2022.3. If there are older DB tables entries from previous installation that may no longer used, then this cause problems during the upgrade to 2022.3. Can you please provide the case number so we can take a deeper review of the logs you've provided?

CodingEthos

I ran the DB maintenance tool on 2020.2.6 before running the upgrade, but it doesn't appear to have removed any invalid columns. It almost looks like NTA module might be the cause, but support couldn't confirm or deny. They did escalate the case to the dedicated team that handles these types of failures about 2 hours ago, so maybe they'll have some more information. The case number is 01185317. Thanks.

Kita

We will provide a NTA clean up tool which should help.

CodingEthos

This was indeed the fix. We are up to 2022.3 without any issues now. Thank you!

abbasciaj

Is there a link to the clean up tool? I'm having the same issue.

Thanks.

visom0023

I'm having the same issue. Is there a script or tool to remove NTA? I don't even want to install NTA.

riggs.clough

Hello,

Please open a support ticket, and we can provide you with this script/tool for removal.