Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Prasasiv
Contributor II
Contributor II

ODBC Connection error

Hi,

Can anyone please help me how to fix the below error message: its generated while fetching data from azure data bricks.

QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 61, ErrorMsg: [Simba][Hardy] (61) Server returned error with no error message during operation: FetchResults.

 

Your suggestions will be highly appreciated.Please find the attached log file for reference.

Regards,

Siva Prasad

Labels (2)
1 Solution

Accepted Solutions
Chip_Matejowsky
Support
Support

Hi @Prasasiv,

The error being returned is not a QlikView error per se, as QlikView is simply returning the error it receives from the connector. Typically it is best to contact the connector vendor directly when using third-party connectors or use their user community/forum, as they are likely to have more information. Also suggest reaching out to your internal DBA as they may have a better understanding of the error's meaning and how to resolve.

 

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!

View solution in original post

1 Reply
Chip_Matejowsky
Support
Support

Hi @Prasasiv,

The error being returned is not a QlikView error per se, as QlikView is simply returning the error it receives from the connector. Typically it is best to contact the connector vendor directly when using third-party connectors or use their user community/forum, as they are likely to have more information. Also suggest reaching out to your internal DBA as they may have a better understanding of the error's meaning and how to resolve.

 

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!