Skip to Content

session: sdk failure when tried to login from the client machine

Jan 11 at 10:57 AM


avatar image


BODS is installed on the server and we are able to connect. Now we have installed the BODS on the Client machine and when tried to connect to the server machine from the client we are facing the SDK failure issue. Please help me with this ASAP.

Also find the screen shot of the error below.

sdk-issue.png (44.3 kB)
capture.png (5.7 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Arun Sasi Jan 11 at 02:46 PM

Its a very common error. Simply googling will give you so many results

Refer SAP note 1601655 - Session: SDK failure error when trying to log on to Designer - Data Services


Arun Sasi

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Thanks Arun for the response, but I am unable to open SAP note 1601655.

I am able to login bods from server machine but unable to connect to the server machine from client machine.



Below is the description of SAP Note 1601655. You must have access to SAP Support Portal to access the SAP Note.


The communication from DS Designer to CMS is via CORBA SDK. The SDK failure error can happen because a firewall is blocking ports or a name resolution issue.


Designer will connect to <CMSName>:<CMSPort> and then use a random high port(49152-65535) for communication. If there is a firewall between the Designer client and the CMS server, you must ensure that you open up the required ports bi-directionally in the firewall.

If there is no firewall, it could be a name resolution issue. Test by using telnet or nslookup to check if the client can reach <CMSName> <CMSPort> and if the server can reach <ClientMachine>. Then update the hosts file accordingly. For example, on the Designer client add: servername
Where is the IP address of the CMS server

In certain cases when name resolution is suspected, changing host identifier to the fully qualified hostname instead of auto-assign will then broadcast the FQDN and resolves some issues. Then flush and update DNS


Arun Sasi