CBS Server Error: CBS failed to communicate with some other server

[former_member205363]

Hi Friends,

I am getting the following error while check-in to NWDI.

Activation failed: CBS Server Error: CBS failed to communicate with some other server( Internal code: COMMUNICATION_ERROR)

Please help us in resolving this issue.

Regards,

Lakshmi Prasad.

[ErvinSzolke]

Hi Lakshmi,

this error comes usually if the NWDI communication user is locked or entered somewhere incorrectly. I mean under NWDI communication user the user maintained on CSM webui - Landscape Configurator - Domain data tab.

I mention this to be on the safe side, because if this is not the same user you are using for NWDI admin operations, then it can happen that while there's no problem with your nwdi admin user, the nwdi communication user is still locked or maintained somewhere incorrectly.

Some remarks to the note 896427 which may help:

- 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 same 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.

Caveat factor:

- 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 and 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.

Cheers,

Ervin

[former_member214355]

Hi

Basically the message says that CBS couldn't talk to DTR. You should find some more detailed error message in the logs of the J2EE engine that runs the CBS.

Could be firewall settings if CBS and DTR are on different servers or missing permissions in DTR for the CMS admin user.

Thanks

Kenny

[dao_ha]

Hi Lakshmi,

The problem caused by a timed out password as Kenny mentioned. Please refer to SAP Note 1239613 for details.

Hope it helps.

Dao

[former_member205363]

Hi Friends,

NWDI Administrator user id is not locked..........

Regards,

Lakshmi Prasad.

[dao_ha]

Hi Lakshmi,

Well, the note doesn't say that the NWDI Admin is locked. It just says that the pwd of whichever userID you're using might need to be changed. Did you try the solution provided in the note, at least?

Dao

[former_member214355]

Hi

Can you check if your NWDI administrator password has expired?

Thanks