User getting locked while connecting through NWDS

[Former Member]

Hi,

This is very critical issue.

User is getting locked while connecting to NWDS.User is hitting SLD and

getting locked in SLD.Apparently i have kept the password of user to

same in NWDI and SLD.Please check at earliest as user are unable to

develop application.I have attached screeprint.Once i reset the password for user

he is able to check in and after some time password is expired in SLD.

[ErvinSzolke · Accepted solution]

Hi,

please read this note carefully first:

#896427 - NWDI Admin User/Password update

Some more general remarks one this:

• If you save a track, then the NWDI user/password (maintained on the 'Domain Data' tab) will be stored inside the buildspaces of that track.
• This information is necessary for communicating NWDI elements like in case of DTR sync.
• If the buildspace has an incorrect password which differs from the one on the Domain Data tab, and/or the User store, then it doesn't matter how many times you change the password in UME and CMS, the user will be sooner or later locked again if you start to use those tracks.
• There's only one way to update the user/pass pair in the buildspaces is if you resave the track. If it is lower than 700 SP13 then you need to make a dummy change on the track before saving, otherwise it won't be recognized as a save. See the note for details. 

If you face a similar problem, then

- Unlock the user in the user store,
- Ensure you can logon to CMS, CBS, SLD and DTR WebUI without problems.
- Resave the involved tracks to update the user/pass pairs, to avoid possible communication problems.
- Since you changed on the track configuration, it is recommended to reimport the software to the buildspaces
- If it is lower than 700 SP13, then consider the correspondings steps of the note.
- If you have a lot of tracks and you resolved the problem as per the note, but you forget to apply the note for one single track, then as soon as you start to use
that track, then again your NWDI admin will be locked, since the buildspace(s) of that track are still having old user/pass information and that will fail by any
authentication during the development.
- Notice, very often the case is that SLD is on a different instance, and that instance is a double stack (abap+java).
This case the nwdi communication user must also exist on that instance, in the abap user store, i.e. you need to doublecheck the user in transaction SU01

I hope this helps.

Best Regards,

Ervin

[Former Member · Accepted solution]

HI Ervin,

Thanks for your reply,

I have SLD and NWDI on sap Netweaver 7.3.Also Admin user is not getting locked,User id of the developer getting locked still we need to follow the steps per note you mentioned.

Regards

Siddhesh

[ErvinSzolke · Accepted solution]

Hi Siddhesh,

did you manage to resolve this problem in the meantime?

Cheers,

Ervin

[Former Member · Accepted solution]

Hi Ervin,

I have opened customer message and sap has come with note 1493272 for reproducing the issue.

Regards

Siddhesh

[ErvinSzolke · Accepted solution]

Hello Siddhesh,

I have corrected the component to an NWDI related one.

Regards,

Ervin

[Former Member · Accepted solution]

Thanks Ervin.

[Former Member · Accepted solution]

Hi Ervin,

Issue seems to have fixed.Fix was Once you define the intial password in nwdi and sld,you will have to set new password and that should be identical in both sld and nwdi.

Thanks for guidance