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

SAP Knowledge Base Article - Preview

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

Symptom

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'


Read more...

Environment

SAP NetWeaver Release Independent

Microsoft SQL Server

Product

SAP NetWeaver 7.4

Keywords

secstore, sqlcmd, connection pool, db user, recreate, secure store , KBA , BC-JAS-SEC , Security, User Management , BC-JAS-SF , Startup Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.