Error with SecureStore when installing EHP2 JAVA CI

[Former Member]

Hi

we are running into this issue while installing JAVA CI EHP2 on windows system.

correct JAVA path exists

DB is up

I think secstore file might have been corrupted but how to generate a new one ....installation hasn't installed config tool yet so how do i generate new secstore property and key file w/o config tool.

Any suggstions would be helpful

PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.pathcom.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB. at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:120)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.inst.jsourcecheck.TaskProcessor.process(TaskProcessor.java:69)

at com.sap.inst.jsourcecheck.SourceChecker.doRun(SourceChecker.java:217)

at com.sap.inst.jsourcecheck.SourceChecker.run(SourceChecker.java:146)

at com.sap.inst.jsourcecheck.JSourceCheck.startAppJob(JSourceCheck.java:231)

at com.sap.inst.lib.app.CommandLineApp.doMain(CommandLineApp.java:111)

at com.sap.inst.jsourcecheck.JSourceCheck.main(JSourceCheck.java:252)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.. at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)

at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)

at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:117)

... 15 more

Caused by: com.sap.security.core.server.secstorefs.WrongKeyException: The encryption key (usually in the key file) is not the key that is required to decrypt the data in the secure store file or the system name (SID) is wrong.

at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:2017)

at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)

at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)

at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)

... 17 more

Caused by: com.sap.security.core.server.secstorefs.InvalidStateException: Internal error during the decryption process.

at com.sap.security.core.server.secstorefs.Crypt.decrypt(Crypt.java:850)

at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1985)

... 20 more

Caused by: javax.crypto.BadPaddingException: Invalid PKCS#5 padding length: 168

at iaik.security.cipher.v.b(Unknown Source)

at iaik.security.cipher.z.b(Unknown Source)

[Former Member]

Hi Jyoti,

Open Config tool and select Secure Storage from the left navigation panel then you will see Key Phrase button in the right side box. You can generate key phrase, save it and resume the installation. If it does not work, better to reinstall from the scratch.

Thanks,

Siva Kumar

[Former Member]

Hi,

Would suggest you to start a clean installation again. There are ways to recreate secstore without the ConfigTool. But it would be too complex and a fresh installation would be an easier approach.

Regards,

Srikishan