Initialization of repository destination JCoDemoSystem failed

[Former Member]

Hello Experts,

We are trying to connect on premise CRM from HCP using RFC destination, We have done the destination settings on HCP and mapping to virtual to internal system in SCC, However we are getting following error -

Exception occurred while executing STFC_CONNECTION in system JCoDemoSystem

com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Initialization of repository destination JCoDemoSystem failed: Opening connection to backend failed:

I Have attached the screen shot for HCP and SCC Settings and also the full exception.

Any pointer and help would be appreciated.

Thanks & Regards

Jeetendra

Exception.txt.zip

[Ulrich_Schmidt · Accepted solution]

Hi Jeetendra,

the Cloud Connector denied the connection, because it can't find a matching mapping.

The virtual port in the hostname mapping needs to match the definition in the JCo destination, so if you defined jco.client.sysnr = 33 in the destination, then you need to specify virtual port = sapgw33 in the system mapping on SCC side.

Best Regards, Ulrich

[Former Member · Accepted solution]

Hi Ulrich Schmidt,

Thanks very much for the response, I have updated the virtual to internal system mapping but still facing the same problem.

Thanks & Regards

Jeetendra

Exception.txt.zip

[Ulrich_Schmidt · Accepted solution]

Hi Jeetendra,

hmm, you still get

"Opening connection denied. Expose the system in your SAP HANA Cloud connector in case it was a valid request."

So there must still be something wrong in the mapping. Can you show me the error message in the SCC Audit Log? (If necessary, set the Audit Log to the highest level, before sending another request from JCo.)

Regards, Ulrich

[Former Member · Accepted solution]

Hi Ulrich,

in audit log i can see below error

2015-04-10 13:30:39, Denying access for user SAPUSER to system xxx.xxx.x.xxx:sapgw33 [connectionId=1739146140]

Can it be because we are using local ip - xxx.xxx.x.xxx in cloud connector virtual to internal system mapping, however i highly doubt this should be the case.

Attached is the audit log for the error.

Thanks & Regards

Jeetendra

Audit log.txt.zip

[Ulrich_Schmidt · Accepted solution]

Hi Jeetendra,

is xxx.xxx.x.xxx what you use for "jco.client.ashost" in the JCo destination? In that case, the virtual host in the SCC system mapping needs to be the same. So:
virtual host = xxx.xxx.x.xxx

virtual port = sapgw33

internal host = real hostname or IP address of SAP system

internal port = real gateway service of SAP system

(Virtual host and port cannot be edited, as they are "keys", so you need to create a new mapping with these values.) With that kind of mapping, the RFC call should work.

Best Regards, Ulrich

[Former Member · Accepted solution]

Hi Ulrich,

After i did the changes suggested by you, the error slightly changed

Exception occurred while executing STFC_CONNECTION in system JCoDemoSystem

com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Initialization of repository destination JCoDemoSystem failed: Opening connection to backend failed: LOCATION CPIC (TCP/IP) on local host ERROR service 'sapgw33' unknown TIME Fri Apr 10 15:01:29 2015 RELEASE 742 COMPONENT NI (network interface) VERSION 40 RC -3 MODULE /bas/742_REL/src/base/ni/nixxsl.cpp LINE 189 DETAIL NiSrvLGetServNo: service name cached as unknown COUNTER 6

It says - ERROR service 'sapgw33' unknown.

Thanks & Regards

Jeetendra

[Ulrich_Schmidt · Accepted solution]

Hi Jeetendra,

great, now it almost works...

Problem now is: the etc/services file on the operating system, where SCC is installed, is not customized correctly. Two solutions:

• "Simple solution": just use "internal port = 3333" in the system mapping.
• "Complete solution" (will also take care of similar problems in the future, for example if you want to use SAPGui, SAP Business Connector or similar SAP software on the computer where SCC is now istalled): open the file /etc/services  (or C:\windows\system32\drivers\etc\services on Windows -- needs admin privileges!) and add the following line:
  sapgw33   3333/tcp
  Afterwards restart the SCC. (Some operating systems may also require a reboot after changing the network settings?! Not sure.)

Best Regards, Ulrich

[Former Member · Accepted solution]

Hi Ulrich,

Thank you very much. It works now I proceeded with simple solution though .

Thanks & Regards

Jeetendra