topic Re: QvTPTConnector (Teradata Parallel Transporter) - Timeout Limit in QlikView

QvTPTConnector (Teradata Parallel Transporter) - Timeout Limit

Thu, 16 Feb 2017 21:58:34 GMT

Hi,

I have successfully installed all the Teradata tools and the QvTPTConnector add in. It seems to be working well with one exception: I need to increase the timeout limit. The default is set to 90 seconds, and I need around 15 to 20 minutes for my test connection to succeed (this is the benchmark discovered in my BTEQ test).

Does anyone know where on my C drive I find the config.xml file that contains the timeout settings?

This link has some hints for me, but it is for server installations whereas I am looking for my PC installation/config files:

Qlikview sessions time out on our users

The place where I thought it would be let me down: C:\ProgramData\QlikTech

Any other ideas?

Best Regards,

Re: QvTPTConnector (Teradata Parallel Transporter) - Timeout Limit

Thu, 16 Feb 2017 22:02:22 GMT

Additionally,

I have found where the QvTPTConnector log gets written:

C:\ProgramData\QlikTech\Custom Data\QvTptConnector\Log

Here is a log example when I test out my connection:

EventID Date and Time Username Severity Message

000000 2017-02-16T16:17:13.845-05:00 AD005\z003du2z Notice QvxLibrary version 2.0.9993.0

000001 2017-02-16T16:17:13.845-05:00 AD005\z003du2z Notice QvTptConnector version 1.0.0.27914

000003 2017-02-16T16:17:21.471-05:00 AD005\z003du2z Notice QvxLibrary version 2.0.9993.0

000004 2017-02-16T16:17:21.471-05:00 AD005\z003du2z Notice QvTptConnector version 1.0.0.27914

000005 2017-02-16T16:21:05.068-05:00 AD005\z003du2z Error Error executing bteq: *** Warning: RDBMS CRASHED OR SESSIONS RESET. RECOVERY IN PROGRESS.

000006 2017-02-16T16:22:06.137-05:00 AD005\z003du2z Error Error executing bteq: The process did not complete in the within timeout limit.

000007 2017-02-16T16:22:06.143-05:00 AD005\z003du2z Error Tool output:

000008 2017-02-16T16:22:06.150-05:00 AD005\z003du2z Error BTEQ 15.10.01.01 Thu Feb 16 16:20:36 2017 PID: 7088

000009 2017-02-16T16:22:06.155-05:00 AD005\z003du2z Error

000010 2017-02-16T16:22:06.159-05:00 AD005\z003du2z Error +---------+---------+---------+---------+---------+---------+---------+----

000011 2017-02-16T16:22:06.161-05:00 AD005\z003du2z Error .SET ERROROUT STDERR;

000012 2017-02-16T16:22:06.164-05:00 AD005\z003du2z Error *** Error messages now directed to STDERR.

000013 2017-02-16T16:22:06.167-05:00 AD005\z003du2z Error +---------+---------+---------+---------+---------+---------+---------+----

000014 2017-02-16T16:22:06.169-05:00 AD005\z003du2z Error .SET ECHOREQ OFF;

000015 2017-02-16T16:22:06.172-05:00 AD005\z003du2z Error +---------+---------+---------+---------+---------+---------+---------+----

000016 2017-02-16T16:22:06.175-05:00 AD005\z003du2z Error +---------+---------+---------+---------+---------+---------+---------+----

000017 2017-02-16T16:22:06.178-05:00 AD005\z003du2z Error +---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+-

000018 2017-02-16T16:22:06.181-05:00 AD005\z003du2z Error *** Warning: RDBMS CRASHED OR SESSIONS RESET. RECOVERY IN PROGRESS.

000019 2017-02-16T16:22:06.184-05:00 AD005\z003du2z Error The process did not complete in the within timeout limit.

000020 2017-02-16T16:22:06.188-05:00 AD005\z003du2z Notice bteq executed in 00:01:30.1360236

000021 2017-02-16T16:22:06.191-05:00 AD005\z003du2z Notice Test connection failure details:

000022 2017-02-16T16:22:06.195-05:00 AD005\z003du2z Notice BTEQ 15.10.01.01 Thu Feb 16 16:20:36 2017 PID: 7088

000023 2017-02-16T16:22:06.198-05:00 AD005\z003du2z Notice

000024 2017-02-16T16:22:06.201-05:00 AD005\z003du2z Notice +---------+---------+---------+---------+---------+---------+---------+----

000025 2017-02-16T16:22:06.204-05:00 AD005\z003du2z Notice .SET ERROROUT STDERR;

000026 2017-02-16T16:22:06.208-05:00 AD005\z003du2z Notice *** Error messages now directed to STDERR.

000027 2017-02-16T16:22:06.211-05:00 AD005\z003du2z Notice +---------+---------+---------+---------+---------+---------+---------+----

000028 2017-02-16T16:22:06.215-05:00 AD005\z003du2z Notice .SET ECHOREQ OFF;

000029 2017-02-16T16:22:06.218-05:00 AD005\z003du2z Notice +---------+---------+---------+---------+---------+---------+---------+----

000030 2017-02-16T16:22:06.222-05:00 AD005\z003du2z Notice +---------+---------+---------+---------+---------+---------+---------+----

000031 2017-02-16T16:22:06.226-05:00 AD005\z003du2z Notice +---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+---------+-

000032 2017-02-16T16:22:06.230-05:00 AD005\z003du2z Notice *** Warning: RDBMS CRASHED OR SESSIONS RESET. RECOVERY IN PROGRESS.

000033 2017-02-16T16:22:06.233-05:00 AD005\z003du2z Notice The process did not complete in the within timeout limit.

Re: QvTPTConnector (Teradata Parallel Transporter) - Timeout Limit

petter — Fri, 17 Feb 2017 01:54:51 GMT

Have you looked in c:\programdata\qliktech\webserver ?

Re: QvTPTConnector (Teradata Parallel Transporter) - Timeout Limit

Fri, 17 Feb 2017 13:35:09 GMT

I tried to find that webserver folder, but I think that is only something made for server installations. I don’t think it is on my PC.

Here is a screenshot of my Qliktech folder:

Re: QvTPTConnector (Teradata Parallel Transporter) - Timeout Limit

Fri, 17 Feb 2017 14:00:48 GMT

Aha!!

I found hints by paying attention during a re-installation. The config file is located at:

C:\Program Files (x86)\Common Files\QlikTech\Custom Data\QvTPT Connector\QvTptConnector.exe.config

For future reference, it contains the following:

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<configSections>

<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >

<section name="TptConnector.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />

</sectionGroup>

</configSections>

<applicationSettings>

<TptConnector.Settings>

<setting name="OutputScriptFile" serializeAs="String">

<value>False</value>

</setting>

<setting name="LogDebugInfo" serializeAs="String">

<value>False</value>

</setting>

<setting name="ConnectionTimeout" serializeAs="String">

<value>90000</value>

</setting>

</TptConnector.Settings>

</applicationSettings>

</configuration>