Installation fails at Register SDM targets

[Former Member]

Hi @all,

at first hello all this is my first post but I read a lot before.

Win 2000 advanced server patch 4

win 2000 sql server actual patch (german language installation)

My Installations stops at the step of "Register SDM targets":

- DB created (P64)

- All users and groups (OS and DB) successfully created

installation log:

1)

WARNING 2004-09-11 16:38:11

Execution of the command "D:\programme\j2sdk1.4.2_05/bin/java.exe '-Xmx256M' '-Djava.ext.dirs=D:\usr\sap/P64/JC05/SDM/program/lib;D:\programme\j2sdk1.4.2_05/jre/lib/ext' '-jar' 'D:\usr\sap/P64/JC05/SDM/program/bin/SDM.jar' 'deploy' 'list=C:\Program Files\sapinst_instdir\WEBAS_640_J2EE_ONLY\CUS/SDAS_TO_BE_DEPLOYED.LST' 'onerror=stop' 'sdmhome=D:\usr\sap/P64/JC05/SDM/program' 'logfile=C:\Program Files\sapinst_instdir\WEBAS_640_J2EE_ONLY\CUS/callSdmViaSapinst.log'" finished with return code 4. Output: Starting SDM - Software Deployment Manager...tc/SL/SDM/SDM/sap.com/SAP AG/6.3003.00.0000.20031126161800.0000Initializing Network Manager (50517)Checking if another SDM is running on port 50518Processing error. Return code: 4

2)

ERROR 2004-09-11 16:38:11

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

3) callSdmViaSapinst.log

Sep 11, 2004 4:38:04 PM Info:

Sep 11, 2004 4:38:04 PM Info: ============================================

Sep 11, 2004 4:38:04 PM Info: = Starting to execute command 'deploy' =

Sep 11, 2004 4:38:04 PM Info: ============================================

Sep 11, 2004 4:38:04 PM Info: Starting SDM - Software Deployment Manager...

Sep 11, 2004 4:38:05 PM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3003.00.0000.20031126161800.0000

Sep 11, 2004 4:38:06 PM Info: SDM operation mode successfully set to: Standalone

Sep 11, 2004 4:38:07 PM Info: Initializing Network Manager (50517)

Sep 11, 2004 4:38:07 PM Info: Checking if another SDM is running on port 50518

Sep 11, 2004 4:38:07 PM Info: -

---

Starting deployment -

---

Sep 11, 2004 4:38:07 PM Info: Loading selected archives...

Sep 11, 2004 4:38:07 PM Info: Loading archive 'D:\sapinst\webas\WebAS640SP3_Full\J2EE1\J2EE-ENG\JDD\SYNCLOG.SDA'

Sep 11, 2004 4:38:07 PM Info: Selected archives successfully loaded.

Sep 11, 2004 4:38:07 PM Info: Error handling strategy: OnErrorStop

Sep 11, 2004 4:38:07 PM Info: Update strategy: UpdateLowerVersions

Sep 11, 2004 4:38:07 PM Info: Starting to execute deployment action (deploy) for "synclog".

Sep 11, 2004 4:38:09 PM Info: Creating connections to database "P64".

Sep 11, 2004 4:38:10 PM Info: Creating vendor connection to database.

Sep 11, 2004 4:38:11 PM Error: Creation of vendor connection failed.

Original error message is:

java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Fehler bei der Anmeldung fu00FCr den Benutzer 'SAPP64DB'.

Stack trace of original Exception or Error is:

java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Fehler bei der Anmeldung fu00FCr den Benutzer 'SAPP64DB'.

at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)

at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)

at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)

at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)

at com.ddtek.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)

at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)

at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)

at com.ddtek.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)

at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)

at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at SDM.main(SDM.java:21)

Sep 11, 2004 4:38:11 PM Error: Execution of deployment action for "synclog" aborted:

Db connect failed.

Sep 11, 2004 4:38:11 PM Error: Deployment NOT successful for synclog

Sep 11, 2004 4:38:11 PM Error: -

---

At least one of the Deployments failed -

---

Sep 11, 2004 4:38:11 PM Info: Summarizing the deployment results:

Sep 11, 2004 4:38:11 PM Error: Aborted: D:\sapinst\webas\WebAS640SP3_Full\J2EE1\J2EE-ENG\JDD\SYNCLOG.SDA

Sep 11, 2004 4:38:11 PM Error: Processing error. Return code: 4

The second thing is and I do think thes is a follow up or root cause of the upper problem:

Inside the SAPMMC I can see that a process can not start, jcontrol.exe J2EE server could not start, trace:

Connot open file
tst-rbg06\saploc\P64\JC05\work\dev_jcontrol

The system cannot find the file specified

Inside my file system the folder dev_jcontrol is not available, the share permissions and folder rights are set correctly. "D:\usr\sap\P64\JC05\work\"

- All Java paths are correct inside the registry

- Java Version 1.4.2_05 installed (no previus installation)

- OS newly installed befor

Any Ideas?

Any Help?

Best Regards Markus

[gregorw]

Hello Jan-Markus,

try to use the english SQL Server version or MSDE. Reboot after every installation step.

Regards

Gregor

[Former Member]

Hi Gregor,

I did not know that it is possible to run Web AS together with a MSDE, so I will try that, thanks.

Regard Markus

[gregorw]

Hello Markus,

it is possible. Look at this thread /message/12152#12152 [original link is broken] for the installation instructions.

Regards

Gregor

[Former Member]

Hi @all,

so thanks for your help, but this all was not the solution. There is the same error message with the MSDE then I had with the SQL Server installation, it stops at "Register SDM Targets" at the synclog. That is one of the last steps

What does the synclog do?

Sep 12, 2004 6:37:02 PM Info: Loading archive 'D:\sapinst\webas\WebAS640SP3_Full\J2EE1\J2EE-ENG\JDD\SYNCLOG.SDA'

Sep 12, 2004 6:37:02 PM Info: Selected archives successfully loaded.

Sep 12, 2004 6:37:03 PM Info: Error handling strategy: OnErrorStop

Sep 12, 2004 6:37:03 PM Info: Update strategy: UpdateLowerVersions

Sep 12, 2004 6:37:03 PM Info: Starting to execute deployment action (deploy) for "synclog".

Sep 12, 2004 6:37:04 PM Info: Creating connections to database "P64".

Sep 12, 2004 6:37:04 PM Info: Creating vendor connection to database.

Sep 12, 2004 6:37:05 PM Error: Creation of vendor connection failed.

Original error message is:

java.sql.SQLException: [DataDirect][SQLServer JDBC Driver][SQLServer]Login failed for user 'SAPP64DB'.'

The user exists and is able to logon (manually checked).

The settings for collation are correctly in the DB.

I restarted the system after every step.

I deinstalled everything on the machine I need for sap and installed it again.

No changes at all.

Regards Markus

Message was edited by: Jan-Markus Wilhelm

[Former Member]

Hi guis,

I found the problem

But that is strange, its beend the password for the DB user. I've chosen one is ok for our security guidelines and this PW contained lpper and lower cases, digits and special chars. So now I tried a quite simple pw and everything worked all right.

Regards Markus