Hi Jayson,
The issue was with our last update to 2021 R4 the Database tables were not updated, so the ININ_APP_VERSION was still showing the old Version of PureConnect. This was because we did not have TLS1.0 enabled when updating.
Side note i thought Setup Assistant utilizing TLS1.0 was resolved 2019 R1 (SCR IC-145885). But looks like it is only resolved utilizing Setup Assistant when testing the connection to the database and does not resolve the issue with the DB update scripts utilizing TLS1.0. So looks like TLS1.0 is required for Upgrades.
Thank you,
------------------------------
Scott Williams
Missouri Higher Education Loan Authority
------------------------------
Original Message:
Sent: 05-18-2022 09:01
From: Jayson Aggen
Subject: High Availability Database Configuration
you have to run the Setup Assistant using TLS 1.0 and a SQL SA account and select the upgrade option. If you are trying to use the listener, you will need to use Native Client 11.4.7469.6 and select the option " Multi-subnet failover" under the ODBC connection
------------------------------
Jayson Aggen
Avtex Solutions, LLC
Original Message:
Sent: 05-17-2022 09:31
From: Scott Williams
Subject: High Availability Database Configuration
Hi All,
I am working through the process of moving our system to look at a listener instead of hardcoded to a SQL server and database directly. The issue i have ran into is when i am at the point in setup assistant to enter the database, it tells me
"The named database cannot be used since an earlier version of the database exists. Please upgrade this database or enter another database name"
This is the same database we connected to, just moved to a different SQL server that has High Availability configured. Has anybody ran into this before? my SQL admin says the everything about the database is the same.
#SystemAdministration
------------------------------
Scott Williams
Missouri Higher Education Loan Authority
------------------------------