Skip to main content
Announcements
Live today at 11 AM ET. Get your questions about Qlik Connect answered, or just listen in. SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
MalcolmCICWF
Creator III
Creator III

11.2 Upgrade: Protocol Error TDS Stream

I have been looknig around and unable to find someone with the answer to this error. After the 11.2 upgrade, I an getting this for only one of my reports that ran fine before the upgrade. Does anyone know how to solves this? What caused it in the 11.20 upgrade?

Capture.JPG.jpg

12 Replies
Not applicable

I believe this error not in Qlikview and this is error with sql server network connection problem.

Please try to connect to sql server manually , after that try to reload in qlikview

MalcolmCICWF
Creator III
Creator III
Author

Well, if it is not a Qlikview error, why have myself and others received this  immediately after an upgrade to 11.2 version? Logistically that would direct the issue to Qlikview's end, not ours.

Not applicable

I believe, this is some network connection problem sql server and qlikview 11.2. Please check ODBC/OLEDB drivers were compatible with 11.2 version.

maxgro
MVP
MVP

Does it happen only for this query to sql server or any query to sql (from qlikview)?

Did you try to execute the same query on the same host but using a different software (not Qlikview)?

Clever_Anjos
Employee
Employee

Are you retrieving A.*, right?

Are you sure A.* does not return a column with same name of other columns?

This could lead to unexpected issues

qlikpahadi07
Specialist
Specialist

I believe the same its Network issue ... you can create a Simple connection String and check whether its working or not.

Not applicable

I experienced the same error and it was very frustrating. I tested a lot and in one case I was repeating the ODBC connect function for the same connection. When I deleted that part of the script, it worked well. When I put that part of the script back in, the error occurred.

Can this help you? Or did you find another solution?

Clever_Anjos
Employee
Employee

Did you check if there´s two columns with same name?

Not applicable

Yep, that was not the case. As I mentioned above, I did make the same connection twice. When I deleted the redundant connection, it worked fine.