cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Installation problem Support Package 13 on WebAS 6.4 (NW04-SR1)

Go to solution
Former Member

on ‎09-19-2005 4:14 PM

0 Kudos

Hello,

i have a serious problem while installing support package 13 on a running webas 6.4

(windows 2000 adv. server, ms sql 2000)

When deploying JDDI (Phase 11 of 24) an error occures in the installation wizard and the installation stops. the log file within sap tells the following:

ERROR 2005-09-19 16:44:12

MUT-02041 SDM call of deploySdaList ends with returncode 4. See output of logfile C:\Program Files\sapinst_instdir\PATCH\ADA\callSdmViaSapinst.log.

ERROR 2005-09-19 16:44:13

MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.

i addad the log file for some more information:

Sep 19, 2005 4:44:08 PM Info: Start logging to console

Sep 19, 2005 4:44:08 PM Info:

Sep 19, 2005 4:44:08 PM Info: ============================================

Sep 19, 2005 4:44:08 PM Info: = Starting to execute command 'deploy' =

Sep 19, 2005 4:44:08 PM Info: ============================================

Sep 19, 2005 4:44:08 PM Info: Starting SDM - Software Deployment Manager...

Sep 19, 2005 4:44:08 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4013.00.0000.20050620162651.0000

Sep 19, 2005 4:44:09 PM Info: SDM operation mode successfully set to: Standalone

Sep 19, 2005 4:44:09 PM Info: Initializing Network Manager (50217)

Sep 19, 2005 4:44:09 PM Info: Checking if another SDM is running on port 50218

Sep 19, 2005 4:44:10 PM Info: -

Starting deployment -

Sep 19, 2005 4:44:10 PM Info: Loading selected archives...

Sep 19, 2005 4:44:10 PM Info: Loading archive 'C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\SYNCLOG.SDA'

Sep 19, 2005 4:44:11 PM Info: Loading archive 'C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\J2EE_JDDSCHEMA.SDA'

Sep 19, 2005 4:44:11 PM Info: Loading archive 'C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\COM.SAP.SECURITY.DBSCHEMA.SDA'

Sep 19, 2005 4:44:11 PM Info: Loading archive 'C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\XML_DAS_SCHEMA.SDA'

Sep 19, 2005 4:44:11 PM Info: Loading archive 'C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\JMS_JDDSCHEMA.SDA'

Sep 19, 2005 4:44:11 PM Info: Selected archives successfully loaded.

Sep 19, 2005 4:44:11 PM Info: Actions per selected component:

Sep 19, 2005 4:44:11 PM Info: Update: Selected development component 'com.sap.security.dbschema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050621161034.0000' updates currently deployed development component 'com.sap.security.dbschema'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041115123517.0000'.

Sep 19, 2005 4:44:11 PM Info: Update: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050623162450.0000' updates currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041118154434.0000'.

Sep 19, 2005 4:44:11 PM Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050628142849.0000' updates currently deployed development component 'tc/TechSrv/XML_DAS_Schema'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041026132059.0000'.

Sep 19, 2005 4:44:11 PM Info: Update: Selected development component 'com.sap.engine.jddischema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712154859.0000' updates currently deployed development component 'com.sap.engine.jddischema'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041026125846.0000'.

Sep 19, 2005 4:44:11 PM Info: Update: Selected development component 'com.sap.jms.jddi.schema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712155016.0000' updates currently deployed development component 'com.sap.jms.jddi.schema'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041117092012.0000'.

Sep 19, 2005 4:44:11 PM Info: The deployment prerequisites finished withtout any errors.

Sep 19, 2005 4:44:11 PM Info: Error handling strategy: OnErrorStop

Sep 19, 2005 4:44:11 PM Info: Update strategy: UpdateLowerVersions

Sep 19, 2005 4:44:11 PM Info: Starting: Update: Selected development component 'com.sap.engine.jddischema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712154859.0000' updates currently deployed development component 'com.sap.engine.jddischema'/'sap.com'/'SAP AG'/'6.4009.00.0000.20041026125846.0000'.

Sep 19, 2005 4:44:11 PM Info: Creating connections to database "MRK".

Sep 19, 2005 4:44:11 PM Info: Creating vendor connection to database.

Sep 19, 2005 4:44:11 PM Error: Creation of vendor connection failed.

Original error message is:

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

Stack trace of original Exception or Error is:

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

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

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

at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)

at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)

at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)

at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)

at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)

at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)

at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)

at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)

at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:115)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:84)

at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)

at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)

at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)

at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)

at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)

at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)

at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)

at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)

at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)

at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)

at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)

at com.sap.sdm.control.command.Command.exec(Command.java:42)

at SDM.main(SDM.java:21)

Caused by: java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

at java.net.URLClassLoader$1.run(URLClassLoader.java:199)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:187)

at com.sap.sdm.is.classloaders.impl.SDMClassLoader.findClass(SDMClassLoader.java:249)

at com.sap.sdm.is.classloaders.impl.SDMClassLoader.loadClass(SDMClassLoader.java:234)

at java.lang.ClassLoader.loadClass(ClassLoader.java:235)

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

... 30 more

caused by

java.lang.ClassNotFoundException: com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

at java.net.URLClassLoader$1.run(URLClassLoader.java:199)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:187)

at com.sap.sdm.is.classloaders.impl.SDMClassLoader.findClass(SDMClassLoader.java:249)

at com.sap.sdm.is.classloaders.impl.SDMClassLoader.loadClass(SDMClassLoader.java:234)

at java.lang.ClassLoader.loadClass(ClassLoader.java:235)

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

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

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

at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)

at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)

at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)

at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)

at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)

at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)

at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)

at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)

at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:115)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:84)

at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:179)

at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)

at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)

at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)

at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)

at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)

at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)

at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)

at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)

at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)

at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(SyntaxChecker.java:37)

at com.sap.sdm.control.command.Command.exec(Command.java:42)

at SDM.main(SDM.java:21)

Sep 19, 2005 4:44:12 PM Error: Aborted: development component 'com.sap.engine.jddischema'/'sap.com'/'SAP AG'/'6.4013.00.0000.20050712154859.0000':

Db connect failed.

Sep 19, 2005 4:44:12 PM Error: -

At least one of the Deployments failed -

Sep 19, 2005 4:44:12 PM Info: Summarizing the deployment results:

Sep 19, 2005 4:44:12 PM Error: Admitted: C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\SYNCLOG.SDA

Sep 19, 2005 4:44:12 PM Error: Aborted: C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\J2EE_JDDSCHEMA.SDA

Sep 19, 2005 4:44:12 PM Error: Admitted: C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\COM.SAP.SECURITY.DBSCHEMA.SDA

Sep 19, 2005 4:44:12 PM Error: Admitted: C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\XML_DAS_SCHEMA.SDA

Sep 19, 2005 4:44:12 PM Error: Admitted: C:\temp\2\J2EE-RUNT-CD\J2EE-ENG\JDD\JMS_JDDSCHEMA.SDA

Sep 19, 2005 4:44:12 PM Error: Processing error. Return code: 4

Thanks for your help

kind regards

Michael

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎09-20-2005 8:18 AM
0 Kudos

Hi Mike,

thanks for your idea. I tried the note but my problem is still there...

Does anyone have another idea?

Kind regards

Michael

Show replies
Show replies
Former Member
‎09-20-2005 9:35 AM
0 Kudos

Hello Mike,

Which is the base patch level from which you are trying to upgrade the Engine to SP13?

From the stack trace of the exception it seems that the properties for the JDBC connections were updated but you still have the old driver in the jdbc directory. Can you check if the sqlserver.jar contains the new jdbc classes and that the jdbc settings in the secure store correspond to the driver in jdbc directory?

Kind Regards

Vyara

Former Member
‎04-10-2008 5:54 AM
0 Kudos

Hi Vyara

>Can you check if the sqlserver.jar contains the new jdbc classes and >that the jdbc settings in the secure store correspond to the driver in >jdbc directory?

Can you tell how can we find sqlserver.jar contain the new jdbc classes? Also how to check the secure store have the new jdbc directory?

Answers (2)

Answers (2)

Former Member
‎09-20-2005 11:20 AM
0 Kudos

Hi Vyara,

thanks for your answer.

My system is now running on SP13!

Kind regards

Michael

Show replies
Show replies
Former Member
‎09-29-2005 7:55 PM
0 Kudos

Michael,

What did you do to resolve this problem?

Thanks

Jim

Former Member
‎09-30-2005 3:01 PM
0 Kudos

nevermind I figured it out.

Jim

Former Member
‎10-11-2005 4:03 PM
0 Kudos

Hi,

I have the same issue, can you tell me how did you fix this issue?

Roger

Former Member
‎10-12-2005 7:42 AM
0 Kudos

Hello Roger,

Since SP13 the jdbc driver for the J2EE Engine was changed (note 872060). It seems that the connection settings were changed in the secure store but the jdbc driver was not updated. Please make sure that you have the new JDBC driver and the new connections settings or vice versa (old driver and old JDBC driver).

Best Regards

Vyara

Former Member
‎09-20-2005 2:21 AM
0 Kudos

Hi Michael,

You can check whether a situation/solution described in the OSS note 872060 is applied to your case.

Regards,

Mike

Show replies
Show replies
Ask a Question