Skip to Content
0

How can I disconnect the SAP Cloud Connector from my Trial Account?

Jan 19, 2017 at 09:21 AM

231

avatar image

I do have a "Not connected" SAP Cloud Connector from a former project. Unfortunately I do have no access to the SCC Server. So I have no glue how to disconnect this Cloud Connector form my Trial Account.

Using the function "Force Disconnect" is not working. I get the following message:

Connected Cloud Connector Instance could not be disconnected. Remote disconnect is supported starting with version 2.8.

Now I'm facing the issue that I'm blocked to establish a new SAP Cloud Connector instance.
I get the following message when I try to do so:

Unable to connect: A different SAP HANA Cloud Connector instance is already connected to this account

What can I do to get rid of this road blocker?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Ervin Szolke
Jan 24, 2017 at 09:53 PM
0

Hi,

Indeed this should be disconnected from the SCC application I guess (to which you have no access) but is there a console client command that would help to get rid of this connection?

https://help.hana.ondemand.com/help/frameset.htm?56e309f496cc446ba441d862db94cb18.html

If this is not helping then I als try to ask an SCC expert, I am sure there is a way out. Let me know.

(I wish we had already the mention feature in place to notify people like @markus.tolksdorf, @antal.perger)

Regards

Ervin

Share
10 |10000 characters needed characters left characters exceeded
Markus Tolksdorf
Jan 25, 2017 at 08:45 AM
0

Hi Klaus,

Cloud Connectors can be disconnected from cloud side only if the SCC version is at least 2.8. Versions below cannot be disconnected and you need to disconnect it from SCC side. Even if we terminate the connection in a hard manner, the re-connectz mechanism of will immediately re-establish the connection.

Best regards,
Markus

Share
10 |10000 characters needed characters left characters exceeded
Balázs Horváth Jun 08, 2017 at 10:44 AM
0

Hi!

Our solution to this problem was to change the sccClientId in the scc_config.ini file to the Connection ID what the cloud want.

Best regards,
Balazs

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

Hi Balazs,

this is not a good idea as still requests will get to the wrong instance of Cloud Connector - connection might be established but you will randomly face issues. Only way to a real fix: disconnect the undesired SCC instance.

Best regards,

Markus

0