topic Re: Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg: in QlikView

Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

Eston_Sello — Tue, 30 Jul 2019 11:35:56 GMT

Good day,

Could any one advise what does this error indicates :

Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

I am getting the above error when try to load a specific table it hangs and return the error but I can successfully load other tables.

Thanks in advance.

Eston

Re: Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

Gysbert_Wassenaar — Tue, 30 Jul 2019 11:48:44 GMT

Usually there is an actual error message after 'ErroMsg:' that will have more information about what happened.

Re: Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

Anil_Babu_Samineni — Tue, 30 Jul 2019 12:00:21 GMT

I understand that message after "You may don't have permission to specific Table?

Re: Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

Eston_Sello — Tue, 30 Jul 2019 12:52:17 GMT

Hi,

This is what i get nothing more.

ODBC error

Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

TableABC:

SQL SELECT "Field_Name",
"Field_Name",
"Field_Name",
"Field_Name",
"Field_Name",
"Field_Name",
"Field_Name",
"Field_Name",
Field_Name,
Field_Name,
"Field_Name",
"Field_Name",
Field_Name,
Field_Name,
"Field_Name",
"Field_Name",
"START_DATE",
"Field_Name",
"Field_Name",
"Field_Name"
FROM CCDW30."TableABC"
where TO_CHAR( CCDW30."TableABC"."START_DATE",'DD-MM-YYYY') = '01-Jul-2019'

Re: Connector reply error: SQL##f - SqlState: 00000, ErrorCode: 0, ErrorMsg:

Brett_Bleess — Wed, 21 Aug 2019 19:19:12 GMT

Eston, what this tells us is the Connector is getting hung up, and I am referencing the ODBC/OLE DB driver/connector in this case, it is not returning any message to us to return in our log. I do not know if something is timing out or what, but the issue is most likely in the DB driver side I believe, but I am not sure what may be the issue. Your best bet may be to reach out to the DBA's, or hit the DB vendor support site as well and see if you can find anything there that fits the symptoms. One other thing you could try is use Excel or something and the same connection string/DSN and see what you get there, if that pulls properly, then we may have an issue on the Qlik side somewhere after all. Hopefully this helps you move things forward.

Regards,
Brett