Skip to Content
0
Former Member
Mar 19, 2009 at 05:16 PM

Error installing Dialog Instance ABAP+JAVA

78 Views

Hi,

We're having a little issue with installation of a ERP dialog instance. The problem is, when the initial

installation was made, it was a system copy but not in the traditional way, the partner performed a copy

in OS level (cp -rp .... , etc). Once it was finished, renaming of certain this happended.

As we can see, DEV was the initial installation (normal way) but QAS and PRD were copies of DEV ( oracle

schema in PRD is SAPDEV too) this apparently doesn't cause a problem. But now the installer of a dialog

instance stops with this error:

PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.path

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

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>

(DBConnectionPool.java:115)

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.engine.configtool.batch.BatchConfig.go(BatchConfig.java:47)

at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:83)

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:112)

... 11 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)

... 13 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)

... 16 more

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

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

at iaik.security.cipher.w.a(Unknown Source)

at iaik.security.cipher.w.engineDoFinal(Unknown Source)

at javax.crypto.Cipher.doFinal(DashoA12275)

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

... 17 more

Error while connecting to DB.

The error occurs when the installer tries to connect to oracle via jdbc, but the files

SecStore.properties and SecStore.key are from DEV, and they were created with the values of DEV, so when

the installer tries with PRD as central instance name, it doesn't work, how can we recreate this files or

reconfigure the j2ee engine so the installer can connect and finish installation ?

Thanks in advance