Skip to Content
avatar image
Former Member

EP installation error at UME configurator .

Hello All,

While installing EP 7.0 using netweaver 7.0 sr2 we are getting error at import java dump and

configure ume stages. The issue seems like the sapinst is not detecting the MS SQL instance JEP

Here are the details of the server

OS : Microsoft Windows server 2003 IA64

DB: MS SQL 2005

RAM: 7.98 G.B

j2sdk : 1.4.2_13

##

C:\Documents and Settings\support>java -version

java version "1.4.2_13"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)

##

When we set the environment variable SAPINST_SKIP_ERRORSTEP = true , the error at import java dump

is not occurring any more. However the error at configure ume still occurs.

Here are the log details

from sapinst.log

###

ERROR 2008-04-08 16:11:07

CJS-30059 Java EE Engine configuration error.<br>DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile umconfigurator.log: 'Apr 8, 2008 4:10:53 PM Info: UME configurator (com.sap.security.tools.UMConfiguratorLoad) called for action "setup"PerfTimes : loadNativeLayer: loading jperflib failed. no jperflib in java.library.pathApr 8, 2008 4:11:07 PM Error: main() [EXCEPTION] 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:360) at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125) 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:60) at com.sap.security.tools.UMConfigModel.<init>(UMConfigModel.java:79) at com.sap.security.tools.UMConfiguratorLoad.main(UMConfiguratorLoad.java:179) 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: java.sql.SQLException: [NWMss][SQLServer JDBC Driver][NWMss][SQLServer JDBC Driver]The requested instance is either invalid or not running. at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source) at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source) at com.sap.nwmss.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source) at com.sap.nwmss.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source) at com.sap.nwmss.jdbc.base.BaseConnection.connect(Unknown Source) at com.sap.nwmss.jdbc.base.BaseConnection.setupImplConnection(Unknown Source) at com.sap.nwmss.jdbc.base.BaseConnection.open(Unknown Source) at com.sap.nwmss.jdbc.base.BaseDriver.connect(Unknown Source) at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215) at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608) at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285) at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302) ... 12 more

ERROR 2008-04-08 16:11:07

FCO-00011 The step runUMConfigurator with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_UME_Configuration|ind|ind|ind|ind|1|0|NW_UME_Configuration_Standalone|ind|ind|ind|ind|0|0|runUMConfigurator was executed with status ERROR .

###

from jlog.

###

08.04.08 12:08:45 com.sap.inst.jload.Jload main

SEVERE: couldn't connect to DB

08.04.08 12:08:45 com.sap.inst.jload.Jload logStackTrace

SEVERE: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver.

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

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

at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)

at com.sap.inst.jload.db.DBConnection.connectViaSecureStore(DBConnection.java:105)

at com.sap.inst.jload.db.DBConnection.connect(DBConnection.java:149)

at com.sap.inst.jload.Jload.main(Jload.java:580)

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: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)

at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)

at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:141)

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

###

Guys can you please give some tips to solve the issue. I will reward full points.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Apr 09, 2008 at 05:56 PM

    Hi,

    The root cause of the problem is that SAP Java cannot load the database driver for MSSQL

    "SEVERE: com.sap.sql.log.OpenSQLException: Could not load class com.sap.nwmss.jdbc.sqlserver.SQLServerDriver."

    Because of this it reports it cannot find the database, but it actually hasn't tried at all.

    There seems to be a solution reference in this thread (note 872060)

    installation-problem-support-package-13-on-webas-6

    Regards

    Dagfinn

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Dagfinn

      Thanks for the help. But interesting thing is that I was able to install EP 7.0 successfully with the same installation dump on development. Only when i am installing on the production it is getting stucked at java import dump and ume configaration.

      I did contacted SAP regarding this but got no response from them yet,

      Do you have any other work arounds?

  • avatar image
    Former Member
    Apr 09, 2008 at 10:22 AM

    Hai,

    Check whether the installation of MSSQL is completed or not. and also check all the services are started or not.Is the Database is opened and can you able to login into the SQL Enterprise Manager.

    Check the Serverproperty('Collation') and changefrom SQL_ Latin1_General_CP850_BIN to SQL_ Latin1_General_CP850_BIN2.And start the installation and try.

    Thanks and Regards,

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Venketa,

      I executed the select serverproperty('collation') and got the result as

      SQL_Latin1_General_CP850_BIN2 . So the note is not applicable for me.

      Also I found that note is for MS SQL 2000 while my installation is MS

      SQL 2005 while the note 675939 is for SAP Web AS 6.40 while mine

      is Web AS 7.00

      Do you have any other suggestions?