Skip to main content

QVConnect logging for troubleshooting ODBC/OLEDB

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

QVConnect logging for troubleshooting ODBC/OLEDB

Last Update:

Dec 14, 2023 3:50:43 AM

Updated By:

Sonja_Bauernfeind

Created date:

Oct 13, 2017 4:10:56 AM

There are specific log settings that can be turned on to enable logging from QVConnect. This can be useful when troubleshooting generic ODBC/OLEDB connection issues.

Resolution

The following options can be set in the Settings.ini for the QlikView Desktop or the QlikView reload engine. If the reload is carried out in the Desktop client, the Desktop client .ini needs to be changed. If the reload is executed by the QlikView Publisher, the reload engine or batch .ini needs to be changed.

Verbosity can also be set to 900 for the debug level.

These lines need to be added:

SELOG_QVSConnector=1
Verbosity=700
ExtendedErrorLoggingMode=1

For information on how to modify the settings.ini files, see:

How to change the settings.ini in QlikView Desktop and QlikView Internet Explorer Plugin 
How to find and modify the QlikView QVB settings file to find the QlikView QVB settings file 

This will result in a QlikViewError.Log being created in the User Document folder. After reload, it will contain lines like:

Info    General    GenericConnect.cpp    582    [0X00000868] GetNextReply(1) reply: (res: 11) msg: 'SQL##f - SqlState: 08004, ErrorCode: 12154, ErrorMsg: [Oracle][ODBC][Ora]ORA-12154: TNS:could not resolve the connect identifier specified

 

Environment:

QlikView 

Labels (2)
Comments
Anonymous
Not applicable

Hi @Sonja_Bauernfeind 

 

I made the changes but cannot see where is the log "QlikViewError.Log" being created in the "User Document folder".

Could you please tell me where exactly is this Folder path?

 

NOTE: I added parameters 

SELOG_QVSConnector=1
Verbosity=900
ExtendedErrorLoggingMode=1

 

in the C:\Users\<MyUser>\AppData\Roaming\QlikTech\QlikView\Settings.ini

but I can't find any qlikerror.log after a reload of a document using odbc connection.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Anonymous 

The log file will be created where you have stored the .QVW which is being reloaded. So directly next to it, just like a document reload log.

If you are reloading it locally in the QlikVIew Client, it'll be next to wherever you have that .QVW stored. If you reload it from the QlikView Server (no Publisher) it will be stored next to the document in the User Documents folder you have configured (or the default one if you left it default). For the Publisher, I am not 100% sure if it is stored next to the Source Document or with the task and document logs. 

All the best,
Sonja 

 

Anonymous
Not applicable

I made all the steps:

1. In C:\Users\<MyUser>\AppData\Roaming\QlikTech\QlikView\Settings.ini  and after added params:

[QlikView]
ExamplesFolder=Examples
[Settings 7]
SELOG_QVSConnector=1
Verbosity=900
ExtendedErrorLoggingMode=1
InterfaceLanguage=Spanish
InstalledLIBID110={15B258E8-415E-11D1-934D-0040333C91CC}
ServerLogFolder=C:\ProgramData\QlikTech\QlikView
CanDynamicUpdate=1

.

.

.

 

2. Then I make a reload to my qvw and reproduce a connection error but no QlikViewError.Log is generated aside my qvw file.

 

What am I missing?

Version QV12 May2021

Contributors
Version history
Last update:
‎2023-12-14 03:50 AM
Updated by: