Error while deployment

[Former Member]

Dear Experts,

I am trying to deploy one of my application on to J2ee via NWDS, but deployment gets aborted.

The error that I am getting is :

Jun 22, 2010 11:32:26 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR: 
[001]Deployment aborted 

Settings
SDM host : ceerpepd
SDM port : 50118
URL to deploy : file:/C:/DOCUME~1/sdhruv/LOCALS~1/Temp/temp2081sap.com~ITDec.ear

Result
=> deployment aborted : file:/C:/DOCUME~1/sdhruv/LOCALS~1/Temp/temp2081sap.com~ITDec.ear
Aborted: development component 'ITDec'/'sap.com'/'LOKAL'/'0.2010.06.22.11.31.57'/'0':Cannot login to the SAP J2EE Engine 
using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure 
Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 
701654.com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials 
detected while trying to obtain connection to the J2EE Engine. (message ID: 
com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)

Deployment exception : The deployment of at least one item aborted

Any help would be appreciated.

Thanks

Amita

Edited by: amita arora on Jun 22, 2010 11:14 AM

[former_member214651 · Accepted solution]

Hi,

The Log mentions the userid / password used for deployment is not valid. Confirm the credentials for deploying the file and also check if the id has credentials to deploy on the WAS.

Regards,

Poojith MV

[Former Member · Accepted solution]

Dear Poojith,

I have tried this, but the problem still persists.

Thanks,

Amita

[former_member214651 · Accepted solution]

Hi,

Try logging into the portal using the userid and password which u are using for deployment to check if the pasword has expired or locked?

If yes, u can reset the password and try.

Check this link also:

Regards,

Poojith MV

[Former Member]

resolved the issue

[Former Member]

Hi Amita,

i am facing the same problem right now.

Can you please explain me how u solved it, cause u just said u resolved the issue.

Regards,

Marcus

[Sharathmg]

Marcus,

The error while deployment happens due to mis-match in the SDM password(which is stored in two places).

Follow this SAP Note: 701654

https://websmp130.sap-ag.de/sap/support/notes/convert2pdf/0000701654?sap-language=EN

Excerpt from the SAP Note:

"

Reason and Prerequisites

The administrator user's password is not only stored in the active user store, but also in secure

storage in the file system so that certain applications such as the Software Deployment Manager

(SDM) can use it to connect to the J2EE Engine.

Therefore, when you change the administrator user's password in the user store, you must also update

the entry in secure storage in the file system. Otherwise, the SDM attempts to connect to the J2EE

Engine using the old password and you receive the error message mentioned above.

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.

"

Regards,

Sharath

[blanca_serrano]

Hello Amita,

Then, please try with the following:

1.- Check id SDM user is locked (It should be visible in the current SDM logs)

2.- Check if the data maintained on the Runtime Systems tab in CMS are wrong, you can check it easily. There is an Icon on the runtime systems in CMS, it calls

"View/Edit Deployment Substitution Parameters". If you click on it, then the SDM details will be displayed. You can find it by all the runtime systems you maintained.

If in the expanded view you can see the details of SDM, then the connection is fine. If not, you need to review those settings. This way you can also ensure that all the other data

like hostname and port are correct.

3.- Try also the following. Start the SDM RemoteGUI directly, and attempt logon.

If you cannot logon, proceed this way:

- stop SDM using JCMON

- cd /usr/sap/<SID>/<instance>/SDM/program

- sdm jstartup "mode=standalone"

- sdm changepassword "newpassword=<newpass>"

- sdm jstartup "mode=integrated"

- start SDM using JCMON

Obviously at changepassword step use the same password as before, which you also use on the runtime systems tab for the corresponding SDM.

Let's see if any of these options help you.

Regards,

Blanca

[blanca_serrano]

Hi Amita,

Can you please check note 1228507? Maybe there is a problem saving the password in the secure store.

Regards,

Blanca

[Former Member]

Dear Blanca,

I have already checked this note, but it didn't seem to help.

Thanks,

Amita

[blanca_serrano]

Hello Amita,

Normally such errors are solved by note 701654:

-Have you already implemented it?

- Have you already checked the logon information on Config Tool according to mentioned note ? I would update the configtool password and

retry the deployment:

Use the ConfigTool to change the entry in secure storage as follows:

1. Start the Config Tool:

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.

I hope this helps you.

Regards,

Blanca

[Former Member]

Dear Blanca,

I have certainly checked for all these options, but still the same problem is there. Do u see any other probable reason for this?

Thanks,

Amita