SWPM SAPHANADB cannot be set during Primary Application Server installation

[dan_pfingsten2]

This is a new installation.
Installing S4Hana 2023 on Hana 2.0 using SWPM 2.0 sp18.
The ASCS was installed, the database installed and now installing the Primary Application Server.

In the define parameters phase it asks for the Database Schema password.
The schema name is already filled in and grayed out with SAPHANADB.
The guide says to just specify a password for SAPHANADB.
The schema does not yet exist in the database, as mentioned this is just the Define Parameters phase so nothing has been executed yet.

This error shows up:
The database connection with database user SAPHANADB cannot be set up. Check that the database is online and the password of user SAPHANADB is correct.

The installed database is up and available.

Have tried various iterations of password letters/numbers/length and also mimicked the basic password policy of the Master Password.
The install logs shows errors  INVALID_USER_PASSWORD and also 'authentication failed'.

Wondering if that's the actual error as the user doesn't exist yet, how can the password be invalid and authentication fail if it's just going to create the user?

Log excerpt with server name, port and SID mocked up.
Fri Jul 26 21:26:51 CDT 2024 | com.sap.hdb.core.main.cmd.HdbCmdMain | Start new command section
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.core.main.cmd.HdbCmdMain | Version of com.sap.hdb.core.jar | Changelist: 212394 | Release: lmts_027_REL | API-Version: 00
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.core.main.cmd.HdbCmdMain | Version of com.sap.hdb.sl.lib.jar | Changelist: 213789 | Release: lmts_027_REL | API-Version: 35
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.core.main.cmd.HdbCmdMain | Name of HdbCmdClazz: class com.sap.hdb.sl.lib.utils.cmd.clazz.IsConnectPossible
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.sl.lib.connection.sql.JdbcDriver | URI: file:/tmp/sapinst_instdir/S4HANA2023/CORE/HDB/INSTALL/DISTRIBUTED/ABAP/APP1/ngdbc.jar
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.sl.lib.connection.sql.JdbcConnection | Instance is a multiple-container system.
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.sl.lib.connection.sql.JdbcConnection | Start new connection with connect URL: jdbc:sap://<server_name>.mikl.com:<port>/?databaseName=<SID> connect user: SAPHANADB
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.sl.lib.utils.cmd.clazz.IsConnectPossible | HDBSLLIB Exception: [INVALID_USER_PASSWORD] com.sap.db.jdbc.exceptions.SQLInvalidAuthorizationSpecExceptionSapDB: [10]: authentication failed
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.core.main.cmd.HdbCmdMain | End of HdbCmdClazz section: class com.sap.hdb.sl.lib.utils.cmd.clazz.IsConnectPossible
Fri Jul 26 21:26:52 CDT 2024 | com.sap.hdb.core.main.cmd.HdbCmdMain | *************************************************************

Any feedback appreciated.

[dan_pfingsten2 · Accepted solution]

Found an issue with the preceding schema database load, SAPHANADB should have existed in the database.  Since it didn't, authentication failed. Upon successful load of S4Core Exports in to the Tenant database the issue was resolved.