Skip to Content
author's profile photo Former Member
Former Member

WAS Installation 6.40 SP3 SunSolaris / Oracle

Hi,

I have a big problem when installing the WAS 6.40 SP3.

When installing the installation stops at the step "SAP J2EE Engine Server Core" with the message:

"Error occured while connecting to database (UploadFile). Msg: No such algorithm:

DESede

"

I don't have any clue what is going wrong here.

The Database is up and running (9.2.0.5)

Details are attached:

CJS-20011 J2EE engine configuration error. DIAGNOSIS: Error when configuring J2

EE Engine. See output of logfile /nwinst/batchconfig.log: 'My Library Path is: /

usr/j2se-1.4.2_05-b04/jre/lib/sparc/client:/usr/j2se-1.4.2_05-b04/jre/lib/sparc:

/usr/j2se-1.4.2_05-b04/jre/../lib/sparc:/tmp/sapinst_exe.2819.1102671491:/usr/op

enwin/lib:/usr/lib

ElementInfoTask has finished successfully on dispatcher

ConsoleLogsTask has finished successfully on dispatcher

ChangeManagerPropsTask has finished successfully. Manager: LockingManager on dis

patcher

ChangeManagerPropsTask has finished successfully. Manager: ClusterManager on dis

ConsoleLogsTask has finished successfully on dispatcher

ChangeManagerPropsTask has finished successfully. Manager: LockingManager on dis

patcher

ChangeManagerPropsTask has finished successfully. Manager: ClusterManager on dis

patcher

ElementInfoTask has finished successfully on server

ConsoleLogsTask has finished successfully on server

ChangeManagerPropsTask has finished successfully. Manager: LockingManager on ser

ver

ChangeManagerPropsTask has finished successfully. Manager: ClusterManager on ser

ver

ChangeServicePropsTask has finished successfully. Service: dbpool on server

ChangePasswordsTask finished successfully.

Error occured while connecting to database (UploadFile). Msg: No such algorithm:

DESede

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 13, 2004 at 11:36 AM

    The database is up and running, but you cannot connect. Is the Oracle Listener running? The listener needs to run if you want to make any connection to the database. You can check the listener with the command "lsnrctl status". If it is not running, start it with "lsnrctl start"

    Regards,

    Pascal.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      I'm experiencing a similar problem trying to install on HPUX.

      ERROR 2004-12-17 13:38:25

      CJSlibModule::writeLogEntry()

      CJS-20011 J2EE engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile /tmp/sapinst_instdir/WEBAS_640_J2EE_ONLY/CS/CUS/batchconfig.log: 'My Library Path is: /hpsauce_2/weblogic/8.1.3/jdk142_03/jre/lib/PA_RISC2.0:/hpsauce_2/weblogic/8.1.3/jdk142_03/jre/lib/PA_RISC2.0/server:/hpsauce_2/weblogic/8.1.3/jdk142_03/jre/../lib/PA_RISC2.0:/tmp/sapinst_exe.17388.1103308615:/hpsauce_3/oracledb/9.2.0.5/lib32:/hpsauce_3/sap640/J2E/exe:/hpsauce_2/hongj/crn/bin::/usr/lib

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

      at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:300)

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

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

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

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

      Caused by: java.sql.SQLException: Io exception: Invalid number format for port number

      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)

      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)

      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)

      at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3678)

      at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:352)

      at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:365)

      at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:547)

      at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:347)

      at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)

      at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:549)

      at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:262)

      at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:251)

      ... 12 more

      -


      caused by -


      java.sql.SQLException: Io exception: Invalid number format for port number

      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)

      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)

      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)

      at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3678)

      at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:352)

      at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:365)

      at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:547)

      at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:347)

      at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)

      at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:549)

      at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:262)

      at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:251)

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

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

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

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

      When I look in the system.log file, the following message is listed.

      #1.5#C0000A40001E00000000000001843A750003EB6375E06998#1103237342055#/Sys

      tem/Server##com.sap.engine.core.configuration#######main##0#0#Info#1#com

      .sap.engine.core.configuration#Plain###OpenSQLDataSource successfully

      created with secure store.#

      #1.5#C0000A40001E00000000000101843A750003EB6375EAA6B0#1103237342734#/Sys

      tem/Database/sql/jdbc##java.lang.Class#######main##0#0#Error#1#java.lang

      .Class#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL

      error occured on connection jdbc:oracle:thin:@hpsauce:undefined:J2E:

      code=17,002, state="null", message="Io exception: Invalid number format

      for port number".#5#17002#<null>#Io exception: Invalid number format

      for port number#jdbc:oracle:thin:@hpsauce:undefined:J2E#<null>#

      It doesn't seem to pick up the port number for the Oracle instance.

      When I test sqlplus at the command line, though, I can successfully connect to the database.

      Why is this happening? Is it because I didn't use the default /oracle directory as the db server's installation location?

      The install has a lot of directories hard-wired.

      Thanks,

      Joyce

  • author's profile photo Former Member
    Former Member
    Posted on Jan 26, 2005 at 10:14 AM

    I have fixed the problem.

    I have set the right JAVA_HOME path but there where some other JDK versions on the host.

    With "which java" I got the right java executable, but I still got the DESede problem.

    SOLUTION:

    I removed all other JDK's from the machine except the JDK 1.4.X.

    After that the installation succeeded.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.