Connector reply error: *** Can I get the full message without *** in a script ?

[aguirre]

Hello,

because one table doesn't exist

I get the following error on the load script window, when I execute an sql on non existing table:

The following error occurred:

Connector reply error: SQL##f - SqlState: HY000, ErrorCode: 0, ErrorMsg: Parser: 15 - Table name doesn't exist

I would like to trap this message and do something when it occurs.

But if  I get it with a variable this way:

           LET v_errore = ScriptErrorDetails;

The v_error variable contains: Connector reply error: *** 

Why this happens? How can I parse the full message ?

Thanks

[Alan_Slaughter]

Hi Aguirre, Please review this article:

https://community.qlik.com/t5/Official-Support-Articles/Native-Path-System-error/ta-p/1717101

[aguirre]

Thanks, but this doesn't address the problem.

I would like to read the error message instead of  ***

The complete error message shows up in the console at execution but if I put it in a variable so that I can deal with it I get ***

I hope it's more clear now.

[Alan_Slaughter]

Hi Aguirre,  normally this type of error is caused by the SQL driver and you would have to reach out to that provider. 

Maybe this article could provide some help:

https://community.qlik.com/t5/New-to-Qlik-Sense/Transform-ScriptErrorDetails-Into-a-usable-Text/td-p...

[aguirre]

Thanks, but my problem is not understanding  the error.

I know what causes the error.

I need to read the error programmatically and do something if I get a certain error.

Unfortunately I cannot read the error message because 

  LET v_errore = ScriptErrorDetails;

contains the *** and not the full error message (which appears in the console though)

[marcus_sommer]

I fear it's not possible anymore because if I look for errormode and the error-variables within the Qlik help there is no ScriptErrorDetails listed which would contain the specific odbc/oledb errors of the scripterrors 3 + 4. Within an old QV manual from 2015 this error-variable did exists. So it means this feature was removed or is at least deactivated (in this case there might be an option within the easter egg).

@Alan_Slaughter please take the topic to the R&D to query when and why the feature was removed/disabled and if there are any possibilities to get this information in another way (the information itself exists).

- Marcus