Connection between SDM client and server is broken

[Former Member]

Hi All,

On importing to "test" environment my custom sca are not getting imported, i get the following error :"Info:Error during SDM deployment:communication error: Server <server host name> did not accept login request as apiadmin on port no. - Connection between SDM client and server is broken

But the surprising part is the standard sca are getting imported such as "sap.com_SAP_JTECHS", " sap.com_SAP_BUILDT " and "sap.com_SAP-JEE"

Regards,

Vishal

[sid-desh]

Hi Vishal,

The three base SCA's are not deployed on any system but are just imported in the workspaces and buildspaces.

The error may be because there already is a connection open to the SDM server. Like for e.g. using an SDM GUI client.

Please check whether a connection is already open.

Regards

Sidharth

[Former Member]

Hey,

I had entered message server port no. which we enter in NWDS for deployment in the runtime system SDM port no, which is different.

Now its resolved, thanks everyone.

[Former Member]

Tip: Always check if your SDM credentials for the runtime system are correct by expanding the Substitution Variables table. If it's empty, your credentials are incorrect.

[Former Member]

Hi Vishal,

I met the same problem with you. Could you give a little more information about how you solve your problem?

Thanks very much!

Regards,

Hui

> Hey,

>

> I had entered message server port no. which we enter

> in NWDS for deployment in the runtime system SDM port

> no, which is different.

> Now its resolved, thanks everyone.

[Former Member]

In Runtime systems you need to enter the SDM Port No.--- which usually is 50____ something, which is different from what you enter in your NWDS which is the message server port 36__ something. Check you SDM port No ?

Hope this helps.

[Former Member]

it's the tab "runtime systems" in the CMS landscape configurator - you have to enter the fully qualified host name of your runtime system, the SDM port number of the runtime system - which is 5<instance number>18 and the SDM password for the runtime system which you set during the installation.

Best regards

Cornelia

[Former Member]

Hi Vishal,

that's strange - did you check if the CMS-user you configured in the track can still log on to the NWDI system?

Also, you should check if the SDM is still running in your test system (and if the password you entered in the track configuration is correct).

If that doesn't help: I once solved a similar problem by creating the CMS-user in the runtime system with the same password than in the NWDI system (normally that should not be necessary, but it worked for me once....)

Best regards,

Cornelia