Deployment aborted - SDM error

[Former Member]

Hi

When we try and deploy application from NWDS, we're getting the following error:

11-Jul-2008 04:38:05 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:

[001]Deployment aborted

Settings

SDM host : iwdfvm2160

SDM port : 51018

URL to deploy : file:/C:/WINNT/TEMP/temp37982OM3b.ear

Deployment exception : Server iwdfvm2160 did not accept login request as apiadmin on port 51018 - Connection between SDM client and server is broken

Inner exception was :

Server iwdfvm2160 did not accept login request as apiadmin on port 51018 - Connection between SDM client and server is broken

We have tried:

1. Restarting the server

2. Changing the SDM password

3. Running SDM in both standalone and integrated modes.

None of these help. Anyone any ideas? We're not sure what the apiadmin user is for - not much documentation on it.

Thanks

Trish

[nikhil_bose · Accepted solution]

Trish,

are you able to ping iwdfvm2160 (J2E server machine) ?

nikhil

[Former Member · Accepted solution]

Yes, I can ping the server fine.

[nikhil_bose · Accepted solution]

don't forget to change SDM mode to "integrated"

nikhil

[Former Member · Accepted solution]

Nikhil

We haven't changed the j2ee admin password. Have tried the steps you suggest anyway, but still deployment fails with the same error. We're happy that the SDM and j2ee passwords are correct.

Any other ideas?

Trish

[nikhil_bose · Accepted solution]

or try this solution too. hope you are not in VPN

1.Go to Visual Admin --> Security Provider --> service.naming.

2.Select NO for the authentication template.

3.Remove the CreateTicketLoginModule. (This login module can be used only by Web applications.)

nikhil

[Former Member · Accepted solution]

Hello again

We changed the setting to 'no', but couldn't see CreateTicketLoginModule. (would it be in service.naming also?)

Restarted everything and still the same error. Thanks for your help so far .... any more ideas?!

Trish

[Former Member]

We discovered that this was due to a DNS change made on the server! Thanks for everyone's help.

Trish

[nikhil_bose]

log in using remoteGUI.bat

\usr\sap\<SID>\DVEBMGS<nr>\j2ee\program\RemoteGUI.bat

or try changing SDM password.

1. Stop the SDM Server.

2. Start SDM in standalone mode:

C:\usr\sap\<SID>\DVEBMGS<nr>
SDM\program>sdm jstartup "sdmhome=C:\usr\sap\<SID>\DVEBMGS<nr>
SDM\program" "mode=standalone"

3. Reset the password:

C:\usr\sap\<SID>\DVEBMGS<nr>\SDM\program>sdm changepassword "sdmhome=C:\usr\sap/<SID>/DVEBMGS<nr>/SDM/program" "newpassword=Password1"

4. change SDM to integrated mode:

C:\usr\sap\<SID>\DVEBMGS<nr>\SDM\program>sdm jstartup "sdmhome=C:\usr\sap\<SID>\DVEBMGS<nr>\SDM\program" "mode=integrated"

Then deploy.

nikhil

[Former Member]

(See thread below) Passwords are ok - changing in secure storage didn't help.

Any other ideas?

Thanks

Trish

[nikhil_bose]

can you try resetting password of Administrator in useradministation?

http://<server>:<port>/useradmin

1) Log in as administrator

2) change password to a dummy

3) save and log off.

4) re-log in with administrator

5) dummy password 'd have expired now, enter desired password

let me know the status

nikhil

[Former Member]

Hi

We've changed the j2ee_admin password using the URL you suggest. Unfortunately - still get the same error when deploying.

Trish

[nikhil_bose]

One of the reason.

You may have changed Administrator password and is not updated in secure storage. Please refer note 701654.

Solution

Use the Config Tool to change the entry in secure storage as follows:

1. Start the Config Tool.

(Execute <SAPj2eeEngine_install_dir> \configtool\configtool.bat.)

2. Select the secure store node.

The configuration for the secure storage in the file system appears.

3. Select the admin/password/<SID> entry.

4. Enter the administrator user's new password in the "Value" field and choose "Add".

5. Choose "File" --> "Apply" to save the data.

Note: Contrary to the message that appears, you do not need to restart the server or cluster for this change to take effect.

6. Finally restart SDM server.

nikhil

[Former Member]

Hi,

Refer to this link

Regards,

Apurva