-
RFC_COMMUNICATE_FAILURE (to SAP)
s j Nov 7, 2010 1:47 AM (in response to Anders Tolf)pls check whether sufficient authorization given qlikview user id created in SAP.
-
SV:Re: RFC_COMMUNICATE_FAILURE (to SAP)
Anders Tolf Nov 8, 2010 4:20 AM (in response to s j)Hi Sunil!
I use the same Client, System Number, Username and Password as they use live in USA today. The only different on my installation is the IP to the server (extern)
Do you know if anything needs to be "changed/added" on the SAP server to allow this client to access?
-
SV:Re: RFC_COMMUNICATE_FAILURE (to SAP)
alxtoth Nov 8, 2010 5:03 AM (in response to Anders Tolf)Hi,
Compare the hosts files from both machines, C:\Windows\system32\drivers\etc\hosts . Sometimes SAP systems are listed there.
Try also from command line "telnet machine port" to see that firewall is really opened. Black screen means OK
Than try to connect with same SAP user from other tool, and try to query same tables. It is easier to fix authorization problems from "approved" SAP tool, than start explaining what is QlikView
-Alex
-
SV:Re: RFC_COMMUNICATE_FAILURE (to SAP)
s j Nov 8, 2010 7:36 AM (in response to Anders Tolf)Dear Anders,
pls assign QTQVACCESS role to qlikview user created in SAP to extract data from SAP.
Regards
Sunil
-
-
-
-
RFC_COMMUNICATE_FAILURE (to SAP)
Rakesh Mehta Apr 20, 2011 11:53 AM (in response to Srini r)It seems you are missing Data files for the transports. Please make sure you unzip the transport contents and place Kxx file under user/sap/trans/cofiles folder (or something like it based on your SAP directories) adn Rxxx file under /user/sap/trans/data folder. Then repeat tp addtobuffer and see how it goes.
Rakesh
-
-
RFC_COMMUNICATE_FAILURE (to SAP)
Sravan Puppala Apr 21, 2011 4:37 AM (in response to Srini r)Hi srini,
what is the SAP BASIS version of your SAP System and what transports did u install?Regards
Sravan
-
RFC_COMMUNICATE_FAILURE (to SAP)
Srinivasan Radhakrishnan Apr 21, 2011 9:43 AM (in response to Sravan Puppala )We use SAP BASIS 7.00 and SAP QVC 5.40
-
RFC_COMMUNICATE_FAILURE (to SAP)
Sravan Puppala Apr 21, 2011 9:49 AM (in response to Srinivasan Radhakrishnan )Are these your transports which you imported in SAP?
Normal 0 21 false false false DE X-NONE X-NONE MicrosoftInternetExplorer4
1.1.1 SAP BASIS system 6.40 and 7.00
For these systems, the following transports should be installed on the SAP System:
1) E6DK900064 (Data extraction)
2) E6DK900051 (User profile)
The transports must be installed in the above order. The first is cross-client; the second transport is client-specific and has to be installed in all clients where it is intended to be used.
If these are the transports and still it is not working? Then the transports are not installed in the above order.
Bestthing you can do is import the transports correctly in the above order.It must overwrite the existing ones.
Regards
Sravan
-
RFC_COMMUNICATE_FAILURE (to SAP)
Srini r Apr 21, 2011 9:52 AM (in response to Sravan Puppala )Yes, i have requested my SAP team to do in the order. I'm waiting for their reply.
-
RFC_COMMUNICATE_FAILURE (to SAP)
s j Apr 25, 2011 5:14 AM (in response to Srini r)are you solved this issue or what ?
-
RFC_COMMUNICATE_FAILURE (to SAP)
Srini r Apr 25, 2011 6:04 AM (in response to s j)Hi Sunil,
No, not yet.
I'm still waiting for their reply. Thery are located in US, hence the time gap.
Before using Qlikview connector, should i test with Std GUI?.
I'm still facing the RFC Communcation Failure problem and i hope he face transporter installation Problem.Do you have any documentation for Configuring/Administration for SAP system, which can help me.
Regards,
Srini.-
RFC_COMMUNICATE_FAILURE (to SAP)
s j Apr 25, 2011 7:32 AM (in response to Srini r)Can I know whether SAP Basis person assigned required authorization to qlikview user id through which you are extracting data.?.
-
RFC_COMMUNICATE_FAILURE (to SAP)
Srini r Apr 25, 2011 8:49 AM (in response to s j)He created a seperate user to access the SAP and given that credentials to me.
But in documentation, they have mentioned QV user should be provided QTQVCACCESS. Unless we install the transporter in SAP system, we can't able to create the user with the role.First i can't able to connect the SAP system. I get this RFC problem.
-
RFC_COMMUNICATE_FAILURE (to SAP)
candogu Apr 25, 2011 9:03 AM (in response to Srini r)Hi,
how many network cards u have on your qlikview server? If you have more than one and one of them are disabled, then you need to check the order of those network cards.
it seems there is a problem with the communication of QV and sap system..
one more thing is that, from my previous expirences, may be the version of SAP's librfc32.dll is older. keep this option also in your mind.
BR
-
RFC_COMMUNICATE_FAILURE (to SAP)
Srini r Apr 25, 2011 11:23 AM (in response to candogu )Hi, i can able to connect the SAP system using SAP Front End.
But when i try to Connect using QV i get RFC Error.
-
RFC_COMMUNICATE_FAILURE (to SAP)
Srini r Apr 26, 2011 6:08 AM (in response to Srini r)Hi,
One thing i forgot to tell you.
We have SAP system in US and our IT support created another IP to connect the SAP system.
Is there any problem in this access method?Regards,
Srini.-
RFC_COMMUNICATE_FAILURE (to SAP)
s j Apr 26, 2011 7:05 AM (in response to Srini r)Dear Srini,
Can I Know whether you have clustering in SAP Server ?. if you have then you can connect and also extract data with the help of qlikview connector.
-
-
-
-
-
-
-
-
-
-
-
-
RFC_COMMUNICATE_FAILURE (to SAP)
s j Apr 21, 2011 5:48 AM (in response to Srini r)Dear Srini,
As per your posted screen shots . it clear that tranposrt is not sended properly.
pls send both transport once again. it will just overwrite the existing one .
-
-
-
-
SV:RFC_COMMUNICATE_FAILURE (to SAP)
Anders Tolf Apr 26, 2011 7:08 AM (in response to Anders Tolf)Hi!
Must tell my case is solved. The problem was the infrastructure. It was not possible to connect the SAP outside the subnet. They change it and move the QlikView Server in SWE to the same subnet and then it works.
I don't understand anything of this but this is an answer from a mail conversation to the SAP hosting partner in the US
"Yes, unfortunately, SAP will only use specific IPs in your case XXX.XX.X.XX. It does not consider anything else that was changed by NAT. In some cases addressing this with netbios name instead of IP will work. Set the RFC with a node name. That way, the IP is resolved via DNS. I had this same issue with another company using 2 SAP servers in 2 different subnets. There were specific RFC calls that the 2 servers were having issues with. At a glance everything works but things like gateway resets, TMS approvals were very unstable. The only fix was placing the servers in the same subnet."