18 Replies Latest reply: Sep 20, 2017 7:42 AM by m m RSS

    Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"

    m m

      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

        • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
          Hakan Ronningberg

          Hi,

           

          Have you selected 'Server name for RFC' according to this part of the Online help?

           

          Setting up Qlik Extractor administration ‒ Qlik Connectors

           

          Otherwise use the 'Modify' option described.

           

          Regards,

          Hakan

            • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
              m m

              Hi, Hakan

              This is the answer our SAP admins have provided to me.

               

              Yes, we used correct Server name for RFC.

              Also we try to modify RFC.

               

              Here is a screen of generated RFC:

              22.png

               

              But TEST RFC connection doesn’t work:

              33.png

              Is it correct?

               

              There is no direct net connection  between Qlickview and SAPBW, only through saprouter (BW server in DMZ, through saprouter), looks like Qlickview try to connect directly to BW by 3300 port (without saprouter string).  Test connect is OK, but when we try extract data error appears:


              44.png

               

              Thanks.

            • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
              Tobias Vogt

              Hi,

               

              it's also a good idea to check whether the services file is maintained (especially if there's no SAP GUI installed) and maybe double check that there is no Recinfo / Secinfo active that prohibits your program call.

              Maybe your settings have to be added here.

              (Transaction SMGW - I think )

               

              Regards,

              Tobias

              ===

                • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                  m m

                  Hi, Tobias

                   

                  We have installed SAP GUI on Qlick server, but it does not resolve the problem. On SAP BW system parameter gw/acl_mode is set to 0, and there are no files reg_info and sec_info, that means all programs must be registered, without any problems.

                    • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                      Hakan Ronningberg

                      Hi,

                       

                      Upgrading to the latest connector release (6.5.1) is always a good thing! The error might not be resolved but there can be improvements in the logging which makes it more easy to understand the cause of the error.

                       

                      Since there is a backwards compatibility towards the SAP transports (not necessary to import the latest SAP transports), you would only have to install the Windows files. In that case, don't forget to restart the Qlik SAP Network Server after the installation.

                       

                      Regards,

                      Hakan

                        • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                          m m

                          Hi, Hakan

                           

                          We have updated connector to 6.5 and reinstalled all transports on the SAP system. However we still getting the same issue.

                           

                          We can connect to SAP router by telnet, but not to BW Server. 

                          Should there be direct connection between QlikServer and BW Server?

                           

                          Also is it normal that we get error in transaction SM59 when we test RFC connection?

                          33.png

                           

                          Connector Log text:

                          2017-08-31 16:12:31     Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.5.1+Build:02045.origin/release/6.5.1

                          2017-08-31 16:12:31     Using Server Host: localhost , Port: 8680

                          2017-08-31 16:12:31     Socket timeout parameter (s): 900

                          2017-08-31 16:12:31     Socket created OK

                          2017-08-31 16:12:31     DNS: getaddrinfo

                          2017-08-31 16:12:31     Connected to SAP (ASHOST): /H/saprouter/H/172.27.1.16

                          2017-08-31 16:12:31     Making new SAP Request

                          2017-08-31 16:12:31     EXTRACTOR = /CPMB/8IZDN8GYM

                          2017-08-31 16:12:31     TFRMETHOD = T

                          2017-08-31 16:12:31     UPDMODE = F

                          2017-08-31 16:12:31     EXTRLANGUAGE = SYSTEM_DEFAULT

                          2017-08-31 16:12:31     LOGSYS = QTQVCEXTR5

                          2017-08-31 16:12:31     EXTRACTOR /CPMB/8IZDN8GYM#TFRMETHOD T#UPDMODE F#EXTRLANGUAGE SYSTEM_DEFAULT#LOGSYS QTQVCEXTR5#

                          2017-08-31 16:12:53 Err FAILED  Error:

                          LOCATION    CPIC (TCP/IP) on local host with Unicode

                          ERROR       partner '172.27.1.16:sapgw00' not reached

                          TIME        Thu Aug 31 16:12:53 2017

                          RELEASE     720

                          COMPONENT   NI (network interface)

                          VERSION     40

                          RC          -10

                          MODULE      nixxi.cpp

                          LINE        3271

                          DETAIL      NiPConnect2: 172.27.1.16:3300

                          SYSTEM CALL connect

                          ERRNO       10060

                          ERRNO TEXT  WSAETIMEDOUT: Connection timed out

                           

                          Trace.log on saprouter

                          Fri Aug 25 11:27:58 2017

                          ***LOG Q0I=> NiIRead: P=172.22.4.168:57056; L=saprouter:3299: recv (104: Connection reset by peer) [/bas/742_REL/src/base/ni/nixxi.cpp 5386]

                          *** ERROR => NiIRead: SiRecv failed for hdl 665/sock 37

                              (SI_ECONN_BROKEN/104; I4; ST; P=172.22.4.168:57056; L=172.22.4.15:3299) [nixxi.cpp    5386]

                            • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                              Hakan Ronningberg

                              Hi,

                               

                              It works in our system... I'm using a connection string like:

                               

                              CUSTOM CONNECT TO "Provider=QvSAPEXTRConnector.dll;ASHOST=/H/10.76.xxx.xx/S/sapdp99/H/10.76.xxx.xx;SYSNR=06;CLIENT=800;SRVHOST=localhost;SRVPORT=8680;USERIP=10.88.x.xx;XUserId=STRDGUJOHTWB;XPassword=BGdULUdNMLZSGXFGfE;";

                               

                              Maybe there can be some useful information in this document on the pages 3-4 and 10-11.

                               

                              Qlik Connector for SAP - Tips and Tricks v1.6

                               

                              The 'Test connection' in transaction SM59 only works when there is a successful extraction job going on. So it is normal that it fails otherwise.

                               

                              I assume you have allowed the connection in SAPROUTTAB?

                               

                              Regards,

                              Hakan

                                • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                  m m

                                  Hi,

                                   

                                  Could you please write line from your SAPROUTTAB file?


                                  Our SAP admins have added record in SAPROUTTAB for our connection. Just to make sure we did it in the right way.

                                   

                                  Thanks

                                  • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                    m m

                                    Hi Hakan,

                                    saprouttab configured. (we can connect via SAP GUI, also test connection in Qlik is OK)

                                     

                                    We still cannot extract data. It works fine with SQL, but doesn't with SAP Extractor.

                                     

                                    We tried to Troubleshoot of the Extractor connector (page 9 of guide), but there no jobs in SM37 (jobs name like  "BIREQU_QTQVCEXTR1_xxx") What does it mean?

                                      • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                        Hakan Ronningberg

                                        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

                                          • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                            m m

                                            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:

                                             

                                            070707.png

                                            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?

                                              • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                                Hakan Ronningberg

                                                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

                                                  • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                                    m m

                                                    Hi Hakan

                                                    We found a workaround - we modified RFC connection manually via SM59 by adding saprouter string in gwhost section:

                                                    08080.png

                                                    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:

                                                    1. 08.09.2017 16:24:14 Job started
                                                    2. 08.09.2017 16:24:15 Step 001 started (program SBIE0001, variant &0000000000009, user ID QTQVCACCESS)
                                                    3. 08.09.2017 16:24:15 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
                                                    4. 08.09.2017 16:24:15 DATASOURCE = /CPMB/8IZDN8GYT
                                                    5. 08.09.2017 16:24:15 RLOGSYS    = QTQVCEXTR5
                                                    6. 08.09.2017 16:24:15 REQUNR     = REQU_QTQVCEXTR5_20170908162414
                                                    7. 08.09.2017 16:24:15 UPDMODE    = F
                                                    8. 08.09.2017 16:24:15 LANGUAGES  = RU
                                                    9. 08.09.2017 16:24:15 *************************************************************************
                                                    10. 08.09.2017 16:24:15 *          Current Values for Selected Profile Parameters *
                                                    11. 08.09.2017 16:24:15 *************************************************************************
                                                    12. 08.09.2017 16:24:15 * abap/heap_area_nondia......... 8000000000                              *
                                                    13. 08.09.2017 16:24:15 * abap/heap_area_total.......... 8000000000                              *
                                                    14. 08.09.2017 16:24:15 * abap/heaplimit................ 40000000                                *
                                                    15. 08.09.2017 16:24:15 * zcsa/installed_languages...... ER                                      *
                                                    16. 08.09.2017 16:24:15 * zcsa/system_language.......... R                                       *
                                                    17. 08.09.2017 16:24:15 * ztta/max_memreq_MB............ 2047                                    *
                                                    18. 08.09.2017 16:24:15 BEGIN EXIT_SAPLRSAP_002 139
                                                    19. 08.09.2017 16:24:15 END EXIT_SAPLRSAP_002 139
                                                    20. 08.09.2017 16:24:15 PSA=0 USING & STARTING SAPI SCHEDULER
                                                    21. 08.09.2017 16:24:15 Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
                                                    22. 08.09.2017 16:24:15 IDOC: Info IDoc 2, IDoc No. 48317, Duration 00:00:00
                                                    23. 08.09.2017 16:24:15 IDoc: Start = 08.09.2017 16:24:15, End = 08.09.2017 16:24:15
                                                    24. 08.09.2017 16:24:15 tRFC: Data Package = 1, TID = AC1B01105DD259B26FCF0061, Duration = 00:00:00, ARFCSTATE = CPICERR
                                                    25. 08.09.2017 16:24:15 tRFC: Start = 08.09.2017 16:24:15, End = 08.09.2017 16:24:15
                                                    26. 08.09.2017 16:24:15 Asynchronous transmission of info IDoc 3 in task 0003 (0 parallel tasks)
                                                    27. 08.09.2017 16:24:15 IDOC: Info IDoc 3, IDoc No. 48318, Duration 00:00:00
                                                    28. 08.09.2017 16:24:15 IDoc: Start = 08.09.2017 16:24:15, End = 08.09.2017 16:24:15
                                                    29. 08.09.2017 16:24:15 Synchronized transmission of info IDoc 4 (0 parallel tasks)
                                                    30. 08.09.2017 16:24:15 IDOC: Info IDoc 4, IDoc No. 48319, Duration 00:00:00
                                                    31. 08.09.2017 16:24:15 IDoc: Start = 08.09.2017 16:24:15, End = 08.09.2017 16:24:15
                                                    32. 08.09.2017 16:24:15 Job finished

                                                     

                                                     

                                                     

                                                     

                                                    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?

                                  • Re: Has anyone faced same issue "ERROR partner '*.*.*.*:sapgw00' not reached"
                                    m m

                                    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.