on 11-23-2012 6:00 AM
Dear all,
I'm trying to set up Data Services 4.0 connectivity with BW (7.3 SP7) on HANA (rel. 34). I have done everything exactly in the same way as I did earlier for "normal" BW, i.e. TCP/IP RFC connection on BW side with a ProgramID, then RFC server instance on Data Services side. The problem, though, is that I'm getting a connectivity error when testing the connection in SM59:
Logon | Connection Error |
Error Details | Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67 |
Error Details | ERROR: program DS40PROGRAMID not registered |
Error Details | LOCATION: SAP-Gateway on host BWONHANA.corp.local / sapgw00 |
Error Details | DETAIL: TP DS40PROGRAMID not registered |
Error Details | COMPONENT: SAP-Gateway |
Error Details | COUNTER: 18536 |
Error Details | MODULE: gwr3cpic.c |
Error Details | LINE: 1806 |
Error Details | RETURN CODE: 679 |
Error Details | SUBRC: 0 |
Error Details | RELEASE: 720 |
Error Details | TIME: Fri Nov 23 16:56:30 2012 |
Error Details | VERSION: 2 |
Kinda stuck here after scouring OSS Notes and SCN. And, by the way, using Data Services to write directly to HANA tables corresponding to e.g. BW DSO is not considered.
Thanks!
I've been able to fix the issue finally, yet our Basis admin and I differ about the causes.
My view: Gateway security prohibited registration of external TPs. So I have created sec_info and reg_info files and allowed all TPs, HOSTs and USERs (this is an internal system, so security is not in focus).
Basis admin's view: application and gateway host names are case-sensitive.
I'm pretty sure I had tried all possible case combinations and even the IP addresses directly without success before doing my fix. The Basis admin's argumentation is that by default gateway security allows all TPs to register.
Now as it's working, I have no time to investigate who was right here, so listing both things to check.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Roman,
We had the same issue and it is reoslved by creating sec_info and reg_info files. Although I have seen this post well before talking to SAP support I had to hold this procedure off as our Basis Admin was not ready to create those files.
SAP support will be releasing a note on this may be next week.(the note is unpublished right now)
Thanks,
Pramod
Hi Roman
The "Not registered" error message you are getting when testing the RFC connection in transaction SM59, means that the program has not been registered on the source/target system.
It is similar to an issue I usually have when setting up a connection between BW 7.3 and MDM 7.1 systems. Once the connection is created on BW, the error message is displayed, to resolve this issue we normally reboot/restart the MDM server (in some cases we also reboot/restart the BW ABAP instance as well).
You may have to restart your BW and DS instances.
Regards
Derek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.