Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear Colleagues,
We are planning to use QlikView in our organization. We decided to build apps based on data from SAP. For this reason we are using QlikVIew SAP connector version 6.2 and SAP version is 7.4 .
We have followed all the instructions from the QlikView SAP connector manual. We have created user QTQVCACCESS with all the roles and imported all transports to SAP. Also, created needed extractors.
We were able to successfully connect to SAP BW and get some data using SQL connector.
However, we are facing some issues when we try to use extractors. We were facing different errors.
Which we solved by adding proper records in hosts and services files. Also, we have added all grants in saproutertab
Currently we stopped at this error and could not find any way around it.
Could you, please, share some thought and ideas on solving this issue.
Below is the content of log file.
Thank you.
2017-08-23 16:39:45 Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.2.0+Build:02016.origin/release/6.2.0
2017-08-23 16:39:45 Using Server Host: localhost , Port: 8680
2017-08-23 16:39:45 Socket timeout parameter (s): 900
2017-08-23 16:39:45 Socket created OK
2017-08-23 16:39:45 DNS: getaddrinfo
2017-08-23 16:39:45 Connected to SAP (ASHOST): /H/172.*/H/172.*
2017-08-23 16:39:45 Making new SAP Request
2017-08-23 16:39:45 EXTRACTOR = /CPMB/8IZIKSKQ
2017-08-23 16:39:45 TFRMETHOD = T
2017-08-23 16:39:45 UPDMODE = C
2017-08-23 16:39:45 EXTRLANGUAGE = R
2017-08-23 16:39:45 LOGSYS = QTQVCEXTR1
2017-08-23 16:39:45 EXTRACTOR /CPMB/8IZIKSKQ#TFRMETHOD T#UPDMODE C#EXTRLANGUAGE R#LOGSYS QTQVCEXTR1#WHERE#/B28/S_IZDBJ7T I EQ 2017.6#
2017-08-23 16:39:45 TimeoutSAP : 14400
2017-08-23 16:39:45 TimeoutInit : 900
2017-08-23 16:39:45 TimeoutActivity: 7200
2017-08-23 16:39:45 TimeoutData : 3600
2017-08-23 16:39:45 TCPBufSize : 1024
2017-08-23 16:40:07 Err FAILED Error:
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '172.*:sapgw00' not reached
TIME Wed Aug 23 16:40:07 2017
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -10
MODULE nixxi.cpp
LINE 3271
DETAIL NiPConnect2: 172.*.*.*:3300
SYSTEM CALL connect
ERRNO 10060
ERRNO TEXT WSAETIMEDOUT: Connection timed out
COUNTER 1
2017-08-23 16:40:09 Disconnected
2017-08-23 16:40:11 Closing the Socket
Hi,
On the Qlik download site you can find an installation guide for release 6.5.1. Please check page 19 and forward to make sure you have done all necessary configuration.
If you don't find any job in transaction SM37, it means that the extraction job in SAP has not started. Is there still no useful information in the Extractor connector log or in the Qlik SAP Network Server Service log?
Does the SAP server you have chosen for RFC communication have dialog processes?
Is there any related error in the System log (transaction SM21) or is there any related dump in transaction ST22?
Regards,
Hakan
Hi,
We found another worked fine landscape (Qlik+BW).
We tried to connect our Qlik to another BW system, and it works fine (extracted data).
Also we consider difference between BW systems, on the working fine system installed old transports.
We found difference between generated RFC connections, you can see there no GW host on the working fine system:
Also we tried to delete GW string on the our not working system, but Qlik is getting error “GWHOST or GWSERV missing in RFC Destination, NOTE: For all Logical systems use the option 'Modify' in transaction n/QTQVC/EXTRACTOR_ADM”
May be that situation help you to understand.
Why on working system gw options is missing and Qlik extract data fine?
Hi,
In release 6.1.0 of the Extractor connector , there was an improvement to make the connection more stable. To achieve that it was necessary to use 'Gateway Host' and 'Gateway Service' in SM59. So if it is working without 'Gateway Host' and 'Gateway Service', you must be using an older version of the connector.
It is hard to say why the latest release is not working in your system. I think the best way forward is that you open a case at Qlik Support. You can refer to me and to this thread.
Regards,
Hakan
Hi Hakan
We found a workaround - we modified RFC connection manually via SM59 by adding saprouter string in gwhost section:
Gwhost now identified successfully, but now we have new problem,
Qlik cannot extract data:
QvSAPExtr.LOG:
2017-09-08 16:08:53 Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.5.1+Build:02045.origin/release/6.5.1
2017-09-08 16:08:53 Using Server Host: localhost , Port: 8680
2017-09-08 16:08:53 Socket timeout parameter (s): 900
2017-09-08 16:08:53 Socket created OK
2017-09-08 16:08:53 DNS: getaddrinfo
2017-09-08 16:08:53 Connected to SAP (ASHOST): /H/172.20.1.15/H/172.27.1.16
2017-09-08 16:08:53 Making new SAP Request
2017-09-08 16:08:53 EXTRACTOR = /CPMB/8IZDN8GYT
2017-09-08 16:08:53 TFRMETHOD = T
2017-09-08 16:08:53 UPDMODE = F
2017-09-08 16:08:53 EXTRLANGUAGE = SYSTEM_DEFAULT
2017-09-08 16:08:53 LOGSYS = QTQVCEXTR5
2017-09-08 16:08:53 EXTRACTOR /CPMB/8IZDN8GYT#TFRMETHOD T#UPDMODE F#EXTRLANGUAGE SYSTEM_DEFAULT#LOGSYS QTQVCEXTR5#
2017-09-08 16:08:53 TimeoutSAP : 14400
2017-09-08 16:08:53 TimeoutInit : 900
2017-09-08 16:08:53 TimeoutActivity: 7200
2017-09-08 16:08:53 TimeoutData : 3600
2017-09-08 16:08:53 TCPBufSize : 1024
2017-09-08 16:08:54 Received Meta Data, No of Fields: 3
2017-09-08 16:08:54 Information from server: INFOMSG : Started job (INITRNR): REQU_QTQVCEXTR5_20170908162414
SrvService_.LOG:
2017-09-08 16:08:53 Incoming client from IP address: 127.0.0.1, Id: 9
2017-09-08 16:08:53 9 : Connection properties: ASHOST=[/H/172.20.1.15/H/172.27.1.16], SYSNR=[00], CLIENT=[300], SRVHOST=[localhost], SRVPORT=[8680], USERIP=[172.22.4.168]
2017-09-08 16:08:53 Connected to SAP, Id: 9
2017-09-08 16:08:53 SAP Transport information - CurRel: 060500, current: E66K900092, transp date: 20170830, transp time: 173454, basis: 740, Id: 9
2017-09-08 16:08:54 Retrieved gwserv: sapgw00, gwhost: /H/172.20.1.15/H/172.27.1.16
2017-09-08 16:08:54 [Service Record Info] This Service is already registered, Id: 9
2017-09-08 16:08:54 Registered GWHOST: /H/172.20.1.15/H/172.27.1.16
2017-09-08 16:08:54 Registered GWSERV: sapgw00
2017-09-08 16:08:54 Starting the SAP packet listener
2017-09-08 16:08:54 Using System Default language: R, Id: 9
2017-09-08 16:08:54 Requesting a new SAP Data job: /CPMB/8IZDN8GYT, logical system: QTQVCEXTR5, ASHOST: /H/172.20.1.15/H/172.27.1.16, Id: 9
2017-09-08 16:08:54 9 : Started job (INITRNR): REQU_QTQVCEXTR5_20170908162414
2017-09-08 16:09:30 Closing SrvEndPoint: 8
2017-09-08 16:09:31 Closing the receiverThread Id: 8
SM37 log:
As you can see QvSAPExtr see that job REQU_QTQVCEXTR5_20170908162414 is started and running, but in SM37 job BIREQU_QTQVCEXTR5_20170908162414 is already done (duration 2 sec).
Any thoughts?
Hi,
From the SM37 log:
08.09.2017 16:24:15 tRFC: Data Package = 1, TID = AC1B01105DD259B26FCF0061, Duration = 00:00:00, ARFCSTATE = CPICERR
Meaning:
Calls w/ Communication Errors – CPICERR
Number of tRFC calls that were not executed due to problems creating the connection or the communication with the target system or an external component; depending on the settings (transaction SM59), the attempt may be repeated a number of times.
Press the 'tRFC' button in SM59. Set the number of retries in 'Connection attempts up to task'.
Look for more information in transaction SM58.
Regards,
Hakan
So we have finally found solution. We installed older version of transports. I think 5.8
We were able to extract dictionaries (list of products, companies, time, etc.) with less than 1k records
However, when we try to extract data from main info-cubes we get following errors.
« Err FAILED /CPMB/8IZIKSKQ Error: Error: WRONG DATA SELECTION reported from SAP»
« Err Error: WRONG DATA SELECTION reported from SAP, Id: 73. rqState5: Transfer structure field not contained in DataSource»
It is advised to :
1. Deactivate the Extractor in transaction /n/QTQVC/DEACTIVATE
2. Replicate in transaction RSA1
3. Activate the Extractor in transaction /n/QTQVC/ACTIVATE
We have done it 2 times. However, results are same.
Have you seen such error before?
At the end we downgraded transports and connector to version 6.0, and assigned some extra roles to that mentioned in the instructions. It all made us able to extract data from BW.
So there is some issue with SAP connectors after version 6.1, when gwhost and gwport are required. However, then conenction goes directly to BW server, not through saprouter. We will ask our partner to create ticket on Qlik Support.
HI, have you tried to regenetrate the datasource as well?
Deactivate (/n/QTQVC/DEACTIVATE)
Regenerate (RSA1)
Activate (/n/QTQVC/ACTIVATE)
/ Mats
Yes, we did it twice.