Qlik Community

QlikView Connectors

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

SAP Extractor connector error "Invoke Timed Out"

Dear colleagues,

Could you please help to understand the possible reasons for the following issue with SAP Extractor connector?


After a several weeks of normal work the SAP Extractor connector stopped once with the error “Invoke Timed Out”:

2015-12-20 05:37:37     Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.1.0+Build:01015.release/6.1.0

2015-12-20 05:37:37     TraceWinUserName = [off]

2015-12-20 05:37:37     Using Server Host: localhost , Port: 8680

2015-12-20 05:52:37 JOB STATUS: TIMEOUT TRIGGER (UNKNOWN Timeout) SENT TO SERVICE TO ABORT THE SAP JOB

2015-12-20 05:52:42 Err Invoke Timed Out. Please Try Again.

Without any correction actions or changes after the error the same extraction task have been working successfully during the next runs.

What could be a reason?

It’s a painful issue, because stopped all extraction from SAP in the productive QV environment.

We are using QvSAPEXTRConnector  version 6.1.0+Build:01015.release.

Thank you in advance!

Best regards,

Danila Provotorov

1 Solution

Accepted Solutions
Employee
Employee

Re: SAP Extractor connector error "Invoke Timed Out"

Hi Danila,

When interacting with several SAP systems from the same script, it is necessary to have different Qlik SAP Network Servers. This is mentioned in the help page, please see link below:

https://help.qlik.com/Connectors/en-us/connectors/#../Subsystems/SAP_Connectors_Help/Content/6.1/Ins...

Delta Loads: we know only of how to do the repeat in IDoc

The other problems you are facing: please reach out to the Qlik Support (Edit: Ok, I have seen the case as mentioned in your previous post ) using my name and a link to this thread. This will speed up the investigation and fixing of your problems.

Thanks,

Tomas

7 Replies
Employee
Employee

Re: SAP Extractor connector error "Invoke Timed Out"

Hi Danila,

Is the task set up in a QlikView Publisher?

Are there any parallel jobs starting (triggered) at the same time?

Are there multiple connection strings in the job document (script)?


Thanks,

Tomas

Not applicable

Re: SAP Extractor connector error "Invoke Timed Out"

Hi Tomas,


Yes, the task from a QV Publisher.

Yes, there where parallel tasks running on the Publisher but not from SAP that time. We have another errors when SAP Extractor tasks from SAP are running in parallel, please see below.

No, there is only one connection string in the script.

In addition to previous error above we have experienced more different errors with SAP connector last days.

Error type 1:


Qlik SAP Network Server service have been ending unexpectedly several times with event number 7031 on 26.12, 27.12 and before. Please see the screen from Windows System Events Viewer below.  (Sorry for Russian as Windows language on the screen.)

6F25B9D0-99B0-4A0E-8BCC-5EFCBF4D7E6A.png

Error type 1 log:

QvSAPExtr_20151227_014026_txt_get_addr.png

Error type 2:

"Err value with the type RFCTYPE_STRING does not fit into given buffer with the length 147 required buffer length 197"

Error type 2 log (1/2):Server_20160102_000646_txt_rfc_type.png

Error type 2 log (2/2):

QvSAPExtr_20160102_020814a_txt_rfctype.png

Error type 3:

In case when several SAP Extractor tasks were started and running in parallel and ended at about the same time (within 1 minute) the error “NOT all Rows are received yet” was being repeated until reached 2-hour timeout.


The corresponding background job on SAP side ended without errors but data did not reached SAP connector side. So we lost the delta because SAP marked the queue as transferred to the target system.

Error type 3 log (1/2) - NOT all Rows are received yet:

Server_20160101_000638_txt_not_all_rows.png

Error type 3 Log (2/2) - Err Timeout while waiting for SAP data:

QvSAPExtr_20160101_022259_txt_timeout.png


Overall comments to all errors:


- The same tasks could work without errors several days in a row. For example, today and yesterday the same tasks in the same sequence on a Publisher have been ended without errors.

- Because of errors we have lost the delta for the several days but on SAP side the delta was marked as transferred.

Is there any way to repeat the delta from SAP for tRFC method?

In the documentation I can see the option to repeat the delta only for IDoc method.

Thank you in advance for the help!

We really need to resolve  issues with SAP Extractor connector.


The message to technical support was raised with ref "00667868 - SAP connector does not connect to SAP system with unknown error".


Best regards,

Danila

Not applicable

Re: SAP Extractor connector error "Invoke Timed Out"

Hi Tomas,

Based on today errors please find  below additional info for the error type 3 NOT all Rows are received yet” and to the answer on your question "Are there multiple connection strings in the job document (script)?"

There is one connection string for one script but we have two scripts for two different SAP systems with two different connection strings (one connection string for each SAP system) and the error “NOT all Rows are received yet” appears when 2 scripts with connection strings for 2 different SAP systems are running in parallel:

  • Extractor 2LIS_02_SCL from SAP ERP;
  • Extractor ZBI_NEW_PILOT from SAP EWM (another SAP system).

The job names are the same for 2 tasks started at the same time in the different SAP systems: ‘REQU_QTQVCEXTR1_20160105021024’.


Could it be a possible reason for the error?

The extractor log is for 2LIS_02_SCL from the SAP ERP system but there is a records received from ZBI_NEW_PILOT as well:

2016-01-05 02:10:22    Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.1.0+Build:01015.release/6.1.0

2016-01-05 02:10:22    TraceWinUserName = [off]

2016-01-05 02:10:22    Using Server Host: localhost , Port: 8680

2016-01-05 02:10:22    Host address using getaddrinfo.

2016-01-05 02:10:22    Connected to SAP (MSHOST): ni5upe

2016-01-05 02:10:22    Making new SAP Request

2016-01-05 02:10:22    EXTRACTOR = 2LIS_02_SCL

2016-01-05 02:10:22    TFRMETHOD = T

2016-01-05 02:10:22    UPDMODE = D

2016-01-05 02:10:22    EXTRLANGUAGE = R

2016-01-05 02:10:22    LOGSYS = QTQVCEXTR1

2016-01-05 02:10:22    EXTRACTOR 2LIS_02_SCL#TFRMETHOD T#UPDMODE D#EXTRLANGUAGE R#LOGSYS QTQVCEXTR1#

2016-01-05 02:10:22    TimeoutSAP    : 28800

2016-01-05 02:10:22    TimeoutInit    : 900

2016-01-05 02:10:22    TimeoutActivity: 7200

2016-01-05 02:10:22    TimeoutData    : 7200

2016-01-05 02:10:22    TCPBufSize    : 1024

2016-01-05 02:10:23    Received Meta Data, No of Fields: 101

2016-01-05 02:10:24    Information from server: INFOMSG : Started job: REQU_QTQVCEXTR1_20160105021024

2016-01-05 02:10:56    Received: /BIC/QAZBI_NEW_PILOT001, Rows: 3944, Total Rows: 3944

2016-01-05 02:11:20    Received: /BIC/QA2LIS_02_SCL001, Rows: 82448, Total Rows: 86392

2016-01-05 02:11:36    Received: /BIC/QA2LIS_02_SCL001, Rows: 82175, Total Rows: 168567

2016-01-05 02:11:44    Received: /BIC/QA2LIS_02_SCL001, Rows: 50275, Total Rows: 218842

2016-01-05 04:11:48    JOB STATUS: TIMEOUT TRIGGER (TimeoutData) SENT TO SERVICE TO ABORT THE SAP JOB

2016-01-05 04:11:53 Err Timeout while waiting for SAP data

2016-01-05 04:11:55    Disconnected

The extractor log for ZBI_NEW_PILOT with the same job name 'REQU_QTQVCEXTR1_20160105021024' in the SAP EWM system:
2016-01-05 02:10:23    Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.1.0+Build:01015.release/6.1.0

2016-01-05 02:10:23    Using Server Host: localhost , Port: 8680

2016-01-05 02:10:23    Host address using getaddrinfo.

2016-01-05 02:10:23    Connected to SAP (ASHOST): 10.50.2.126

2016-01-05 02:10:23    Making new SAP Request

2016-01-05 02:10:23    EXTRACTOR = ZBI_NEW_PILOT

2016-01-05 02:10:23    TFRMETHOD = T

2016-01-05 02:10:23    UPDMODE = D

2016-01-05 02:10:23    EXTRLANGUAGE = R

2016-01-05 02:10:23    LOGSYS = QTQVCEXTR1

2016-01-05 02:10:23    EXTRACTOR ZBI_NEW_PILOT#TFRMETHOD T#UPDMODE D#EXTRLANGUAGE R#LOGSYS QTQVCEXTR1#

2016-01-05 02:10:23    TimeoutSAP    : 14400

2016-01-05 02:10:23    TimeoutInit    : 900

2016-01-05 02:10:23    TimeoutActivity: 7200

2016-01-05 02:10:23    TimeoutData    : 3600

2016-01-05 02:10:23    TCPBufSize    : 1024

2016-01-05 02:10:24    Received Meta Data, No of Fields: 13

2016-01-05 02:10:24    Information from server: INFOMSG : Started job: REQU_QTQVCEXTR1_20160105021024

2016-01-05 04:10:24    JOB STATUS: TIMEOUT TRIGGER (TimeoutActivity) SENT TO SERVICE TO ABORT THE SAP JOB

2016-01-05 04:10:29 Err Timeout while waiting for SAP data

2016-01-05 04:10:31    Disconnected

Additional information:

Extractor 2LIS_02_SCL with connection string for the SAP ERP system:

CUSTOM CONNECT TO “Provider=QvSAPEXTRConnector.dll;MSHOST=ni5upe;R3NAME=UPE;GROUP=SAPQlikView;CLIENT=400;SRVHOST=localhost;SRVPORT=8680;USERIP=10.50.1.169;TraceWinUserName=0;TimeoutData=7200;TimeoutSAP=28800;”;


Extractor ZBI_NEW_PILOT with connection string for the SAP EWM system:

CUSTOM CONNECT TO “Provider=QvSAPEXTRConnector.dll;ASHOST=10.50.2.126;SYSNR=00;CLIENT=740;SRVHOST=localhost;SRVPORT=8680;USERIP=10.50.1.169;”;

Srvservice Log file extract:

"2016-01-05 02:11:22    Sent Job finished update to SAP: 2LIS_02_SGR

2016-01-05 02:11:26    JOB STATUS: FINISHED, Total Rows: 214444, Id: 19, Name: 2LIS_02_ITM, Run Time: 62 seconds

2016-01-05 02:11:26    Sent Job finished update to SAP: 2LIS_02_ITM

2016-01-05 02:11:35    Received: 2LIS_02_SCL, Id: 17, rows: 82175, Total rows: 168567

2016-01-05 02:11:43    Received: 2LIS_02_SCL, Id: 17, rows: 50275, Total rows: 218842

2016-01-05 02:11:46    rqState 9: Reported complete by SAP, id: 17

2016-01-05 02:11:55    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 02:12:26    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 02:12:57    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 02:13:28    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 02:13:59    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 02:14:00    Received: ZBI_NEW_EBAN, Id: 21, rows: 63790, Total rows: 63790

2016-01-05 02:14:03    JOB STATUS: FINISHED, Total Rows: 63790, Id: 21, Name: ZBI_NEW_EBAN, Run Time: 217 seconds

2016-01-05 02:14:03    Sent Job finished update to SAP: ZBI_NEW_EBAN

2016-01-05 02:14:04    rqState 9 (ext): Reported complete by SAP.

2016-01-05 02:14:30    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 02:15:01    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:09:12    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:09:43    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:10:14    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:10:24 Err Id: 18. Sent Job ABORTED update to SAP. Timeout type: TimeoutActivity, Extractor: ZBI_NEW_PILOT

2016-01-05 04:10:45    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:11:16    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:11:47    NOT all Rows are received yet: 2LIS_02_SCL

2016-01-05 04:11:48 Err Id: 17. Sent Job ABORTED update to SAP. Timeout type: TimeoutData, Extractor: 2LIS_02_SCL"


On the screenshot from the Publisher below all tasks in the group are from SAP ERP system except  SAP Extractor Group_A_002 ZBI_NEW_PILOT DELTA, which is from SAP EWM:

publisher.png

Best regards,

Danila

Not applicable

Re: SAP Extractor connector error "Invoke Timed Out"

So, if I got it correctly, to avoid this type of error (NOT all Rows are received yet) the name for the logical system in the second system should be changed from QTQVCEXTR1 to QTQVCEXTR2.

Since the logical system name is a part of the job name, it would make the job name unique between different SAP systems.

Am I right in my understanding?

Employee
Employee

Re: SAP Extractor connector error "Invoke Timed Out"

Hi Danila,

When interacting with several SAP systems from the same script, it is necessary to have different Qlik SAP Network Servers. This is mentioned in the help page, please see link below:

https://help.qlik.com/Connectors/en-us/connectors/#../Subsystems/SAP_Connectors_Help/Content/6.1/Ins...

Delta Loads: we know only of how to do the repeat in IDoc

The other problems you are facing: please reach out to the Qlik Support (Edit: Ok, I have seen the case as mentioned in your previous post ) using my name and a link to this thread. This will speed up the investigation and fixing of your problems.

Thanks,

Tomas

Employee
Employee

Re: SAP Extractor connector error "Invoke Timed Out"

Please see my response with the link below.

BR,

Tomas

Not applicable

Re: SAP Extractor connector error "Invoke Timed Out"

Hi Tomas,

Thank you very much for the right questions which helped a lot to find the reason and recommended solution!

The additional  server for “Qlik SAP Network Server service” was installed on another server to have separate SAP servers for each SAP source system.

Best regards,

Danila Provotorov