Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

Problems with Teradata ODBC connector

Hi everyone.

I have a fresh install of QV Server with external Publisher server. 11.20 SR7

ODBC connectors work fine except for the Teradata and it's a show stopper.

Desktop client reloads no problems.  QMC task hates it but has no issues with other connections

It's established via system dsn with the ID with access to the Tera db

.  I've reinstalled the Tera utilities suite v15.  The TPT connector starts the load but fails at the SQL select statement - with or with out data sense.

Error:

(2015-01-13 17:39:58) Error: QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=\\<server>\<file location path>\Test.qvw.

(2015-01-13 17:39:58) Error: at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult)

(2015-01-13 17:39:58) Error: at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)

(2015-01-13 17:39:58) Error: --- End of inner exception stack trace ---

This is peculiar.  Let me know if everyone has an idea to try or feedback to answer further inquiries.

Thanks.

Jayson

1 Solution

Accepted Solutions

Re: Problems with Teradata ODBC connector

Can you install QV Desktop on the publisher server and create a test app with the server based DSN to load data from Tera? This should help identify the problem.

15 Replies

Re: Problems with Teradata ODBC connector

The log you have uploaded is the Distribution log. The error shows the reload failed, so you need to enable the document log and look at that for the error.

One possibility is that the reload may be connecting to the database using the QDS credentials. Does the QDS service login have permissions to access the data?

Not applicable

Re: Problems with Teradata ODBC connector

Thanks Colin.

The System DSN ODBC connection credentials is set to the Tera DB - different than the Service QV Account.

Here's the doc log error.  Only an issue when reloaded through the QMC, it's fine to manaul reload with the desktop client.

------------------------

1/13/2015 5:39:56 PM: 0017  ODBC CONNECT32*XUserId*XPassword*
1/13/2015 5:39:57 PM:       Error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
1/13/2015 5:39:57 PM:       General Script Error
1/13/2015 5:39:57 PM:       Execution Failed
1/13/2015 5:39:57 PM:      Execution finished.
-----------------------------

Thanks for your thoughts.

Jayson

Re: Problems with Teradata ODBC connector

>>..Data source name not found and no default driver specified

Does the ODBC DSN exist on the server with the same name as defined on the desktop where the reload works?

Are any ODBC drivers required for Tera DB and are they installed on the server?

Not applicable

Re: Problems with Teradata ODBC connector

aahhhh Let me check that one.

Re: Problems with Teradata ODBC connector

The drivers need to be on the Publisher server as that is where the QVB.exe reload tasks are run by the QDS service.

Not applicable

Re: Problems with Teradata ODBC connector

Thanks Colin.  I didn't have the ODBC connection set up on the publisher server.  Quick easy to set up but didn't resolve it.  Even restarted it just in case.

New error message ...

-----------------------

1/14/2015 9:07:14 AM: 0017  ODBC CONNECT32*XUserId*XPassword*
1/14/2015 9:07:14 AM:       Error: SQL##f - SqlState: IM003, ErrorCode: 160, ErrorMsg: Specified driver could not be loaded due to system error  126: The specified module could not be found. (Teradata, C:\Program Files (x86)\Teradata\Client\15.00\ODBC Driver for Teradata\Lib\tdata32.dll).
1/14/2015 9:07:14 AM:       General Script Error
1/14/2015 9:07:14 AM:       Execution Failed
1/14/2015 9:07:14 AM:      Execution finished.
------------------------

hmmmm ... file is located in the location in both publisher and QV servers ...  I tried applkying the 64bit and re-establish the report connection with that one.  Same result.  Instead the logs says can not locate in C:\Program Files\...

-------------------

1/14/2015 9:21:12 AM: 0018  ODBC CONNECT*XUserId*XPassword*
1/14/2015 9:21:12 AM:       Error: SQL##f - SqlState: IM003, ErrorCode: 160, ErrorMsg: Specified driver could not be loaded due to system error  126: The specified module could not be found. (Teradata, C:\Program Files\Teradata\Client\15.00\ODBC Driver for Teradata nt-x8664\Lib\tdata32.dll).

-------------------

Thanks for your help Colin.

Re: Problems with Teradata ODBC connector

Hi Jayson,

Is the desktop that the load works on a 64-bit or 32-bit OS?

Are the server ODBC drivers 64-bit or 32-bit?

You may need to use  CONNECT32 rather than CONNECT in the connection string to force a 32-bit connection?

Re: Problems with Teradata ODBC connector

You may also need to connect on the server Control Panel to the 32-bit ODBC DSN configuration utility not 64-bit ODBC Config utility.

Not applicable

Re: Problems with Teradata ODBC connector

OS is Server 2012 - 64Bit

Yes worked with both Connect32 and Connect in the script connection string to test out both cases and have both ODBC connections set up on QV Server and Publisher Server.

Now moved back to just 64b connections.  Even added the QV Admin group to the teradata folder permissions to test that theory too.

Community Browser