Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
“A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond”
This error occurs exactly after 600 seconds of waiting for the first data retrieval on 6.5.1 and 6.6 (the extraction job is still running from SAP side at this time).
Even though timeout parameter from SQL connector has been changed (TimeOutBatch, TimeOutFetch, TimeOutStartBatch).
1. Qlik Sense November 2017 patch1
2. Qlik SAP Connector 6.5.1: Extractor connector and Qlik SAP Connector 6.6: Extractor connector
3. Reloading User Account : Member of administrator group
4. Connection string : CUSTOM CONNECT TO "provider=QvSAPExtractorConnector.exe;SRVHOST=localhost;SRVPORT=8680;servertype=0;ASHOST=gbqci01;CLIENT=100;SYSNR=10;logonlanguage=system_default;Timeout=3600;advancedProperties=true;TimeoutSAP=14400;SocketTimeout=9000;TimeoutInit=9000;TimeoutActivity=7200;TCPBufSize=4096;MultipleServicesOverride=false;TraceWinUserName=true;"
5. Values of Parameters:
The values of the following parameters were exactly 600 seconds. So the customer changed it to 6000 and tested it, but it did not work.
gw/deallocate_timeout : default 600 -> change 6000
rdisp/max_wprun_time : default 600 -> change 6000
rdisp/shutdown/abap_trigger_timeout : default 600 -> change 6000
rdisp/shutdown/idle_wp_timeout : default 600 -> change 6000
rdisp/shutdown/j2ee_timeout : default 600 -> change 6000
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.