Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Java CI Installation - Issue of SecureStore files

We are in a process of installalling Java on target host using distributed installation in which we have installed SCS and afterwards we have started CI installtion in which we have below issue.

We have got this error after giving Instance # for installation, below is the error.

(1st error)

========================= ********start of error ********============================

<html> <head> </head> <body> <p> An error occurred while processing option <i>SA                                                                                        P Business Suite 7i 2013 Support Release 2 > EHP3 for SAP CRM 7.0 Java Support R                                                                                        elease 2 > Oracle > SAP Systems > Application Server Java > Distributed System >                                                                                         Primary Application Server Instance( Last error reported by the step: Assertion                                                                                         failed: in

function () {

    if (!NWInstall.getSystem(context.get("sid")).isSecStoreAvailable()) {

        ASSERT(arguments.callee, !installer.onUnix(), "SecureStore files must be                                                                                         available on Unix. Check if the global directory is mounted.");

        context.makeChangeable("secStoreSrcDir");

        var client = new ClientMapping();

        client.mapContextParameter("secStoreSrcDir", "'secStoreSrcDir'");

        installer.setKdbClient(client.getMapping());

        gui.invokeDialog({sid:"d_nw_ask_secstore_files"});

    } else {

        context.makeUnchangeable("secStoreSrcDir");

    }

}

: SecureStore files must be available on Unix. Check if the global directory is                                                                                         mounted.)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i><br>to repeat the                                                                                         current step. </li> <li> Choose <i>Log Files</i><br>to get more information abou                                                                                        t the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log                                                                                         files are written to /temp/syscopy/wj3javainst. </p> </body></html>

======================== ********End of error ********************  =============================

we have checked and see that there are no secure files cretaed under /sapmnt/SID/global/security/data

directory. We copied the below two files from other host to the directory

/sapmnt/<SID>/global/security/data  on application host

SecStore.key

SecStore.properties

Then We observed the follwoing error:

(2nd error)

================******Start of error *************=========================

<html> <head> </head> <body> <p> An error occurred while processing option <i>SAP Business Suite 7i 2013 Support Release 2 > EHP3 for SAP CRM 7.0 Java Support Release 2 > Oracle > SAP Systems > Application Server Java > Distributed System > Primary Application Server Instance( Last error reported by the step: Error when running UMConfiguratorLoad. DIAGNOSIS: See output of log file umconfigurator_loadtype.log: '

   INFO: Loading tool launcher...

r~impl.jar, /temp/syscopy/bj3javainst/install/lib/sap.com~sl~ctc~import.jar, /oracle/client/11x_64/instantclient/ojdbc6.jar]

   INFO: Start

Aug 3, 2015 2:59:09 AM   Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "checkClean"

Aug 3, 2015 2:59:10 AM   Error: main()

[EXCEPTION]

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

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

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

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

r~impl.jar, /temp/syscopy/bj3javainst/install/lib/sap.com~sl~ctc~import.jar, /oracle/client/11x_64/instantclient/ojdbc6.jar]

   INFO: Start

Aug 3, 2015 2:59:09 AM   Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "checkClean"

Aug 3, 2015 2:59:10 AM   Error: main()

[EXCEPTION]

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

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

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

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

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

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

        at com.sap.security.tools.UMConfiguratorLoad$UMConfigModel.<init>(UMConfiguratorLoad.java:994)

        at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:232)

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

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

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

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

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

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

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

        ... 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:2071)

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

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

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

        ... 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:863)

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

        ... 16 more

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

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

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

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

        at javax.crypto.Cipher.doFinal(DashoA13*..)

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

        ... 17 more

================== ******End of error*************=========================

For the second error , we tried by working on the steps in note # note 2022318, but still we are getting the same error.

Does anyone have an idea how to solve this problem?

Not what you were looking for? View more on this topic or Ask a question