2574655 - Java server and Configtool won't start with original SAP<SID>DB user after creating additional SAP<SID>DB user

The Java server has a MSSQL database. An additional SAP<SID>DB user has been created. For example in the case of corruption of the original SAP<SID>DB user or you cannot start the server with the current DB user. Switching back to the original user, after issues with the user are resolved, gives the following errors:

In Configtool:

Error occurred while scanning DB.
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: Could not find a record with key "jdbc/pool/<SID>" in the store..

Caused by: com.sap.security.core.server.secstorefs.NotFoundException: Could not find a record with key "jdbc/pool/<SID>" in the store

Error occurred while loading the Secure Store.
java.lang.StringIndexOutOfBoundsException: String index out of range: -1

In Java bootstrap logs:

com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'J2EE_CONFIG'

SAP NetWeaver Release Independent

Microsoft SQL Server

secstore, sqlcmd, connection pool, db user, recreate, secure store , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , BC-JAS-SF , Startup Framework , BC-JAS-ADM-ADM , Administration , Problem