Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QvSAPConnector 5.5 ==> FETCH_STREAM failed

Hello,

I have install the Qlikview SAP connector according the documentation.
The SAP Slide work Fine when I try the transaction n/QTQVC/SQL
The user is a service and have the QTQVCACCESS

But when I try to get data on Qlikview with the QvSAPConnector, I have the folowing error (Extract from QvSAPConnector log) :


Progress Connected to SAP with C:\ProgramFiles\Common Files\QlikTech\CustomData\QvSAPConnector\QvSAPConnector.dll 5, 5, 8639 IR
Progress Creation of function /QTQVC/OPEN_STREAM
returned after 00:00:00
Progress Creation of function /QTQVC/FETCH_STREAM
returned after 00:00:00
Progress OpenStream called with SQL = "SELECT * FROM T000", PACKETSIZE = 20000, TRACE = "0", TIMEOUT_BATCH = "600", CHECK_SEPARATOR = "1", CONVROUTINE = "1"
Progress OpenStream invoked. Jobnumber is 20110124161417
Progress Jobnumber is 20110124161417
Progress Calling FetchStream
Progress Reply from FetchStream received
Progress Successful fetch of 4 rows
Error The received data record does not have the correct number of fields. It may have been truncated. Check if SAP string contains a NULL-character.
Received data is: "000 ^SAP AG Konzern ^Walldorf ^EUR ^ ^S ^2 ^ ^X ^ ^ ^ ^ ^ ^^00000000 ^ ^"
The incorrect field is number: 1
Statement is: SELECT * FROM T000
Progress Disconnected
Error /QTQVC/FETCH_STREAM failed after 00:00:00 Key = RFC_INVALID_HANDLE (An invalid handle was passed to the API call)



Do you have any ideas ?

1 Solution

Accepted Solutions
pover
Luminary Alumni
Luminary Alumni

I would report this to QlikView support and at the same time I would test other versions of the QV SAP Connector. Recently we had a problem with the 5.5 version, but when we tried the 5.4 version it worked fine. Just make sure to always use the same transport version as the client version.

Regards.

View solution in original post

12 Replies
pover
Luminary Alumni
Luminary Alumni

I've never had this particular error, but I would check if the SAP QV Connector client is the same version as the SAP QV Transports installed. I assume they both should be v5.5 SR2.

Second, I would try to extract another table to see if it has something to do with the values of the table and in particular the null values that the error log states. Although the company table t000 shouldn't have been too much trouble.

Regards.

suniljain
Master
Master

can you post script ?.

pls try try to extract one more table i.e kna1,lfa1 or anyother table and check log file of your application ?.

Not applicable
Author

Hello,

Karl : I think it's the same SAP QV connector version on SAP Server and Qlik Server (It's a Qlikview Installation)

Karl, Sunil : I have the same error with others tables. For exemple the execution log of the ReLoadSAPDD.qvw :


2011-01-24 19:26:00 Progress Connected to SAP with C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPConnector.dll 5, 5, 8639 IR
2011-01-24 19:26:01 Progress Creation of function /QTQVC/OPEN_STREAM returned after 00:00:00
2011-01-24 19:26:01 Progress Creation of function /QTQVC/FETCH_STREAM returned after 00:00:00
2011-01-24 19:26:01 Progress OpenStream called with SQL = "SELECT * FROM /QTQVC/CONTROL", PACKETSIZE = 20000, TRACE = "0", TIMEOUT_BATCH = "600", CHECK_SEPARATOR = "1", CONVROUTINE = "1"
2011-01-24 19:26:01 Progress OpenStream invoked. Jobnumber is 20110124192601
2011-01-24 19:26:01 Progress Jobnumber is 20110124192601
2011-01-24 19:26:01 Progress Calling FetchStream
2011-01-24 19:26:01 Progress Reply from FetchStream received
2011-01-24 19:26:01 Progress Successful fetch of 87 rows
2011-01-24 19:26:01 Error The received data record does not have the correct number of fields. It may have been truncated. Check if SAP string contains a NULL-character.
Received data is: "200^20110112172603^17260400^16 ^/QTQVC/READ_DATA ^A^vsapd01_BID_10 ^172600 ^20110112 ^5 ^DATA512 ^0^LOGOUSSAN ^2011/01/12 16:26:03 ^2011/01/12 16:26:36 ^vsapd01_BID_10 ^0^010^"
The incorrect field is number: 1
Statement is: SELECT * FROM /QTQVC/CONTROL
2011-01-24 19:26:01 Progress Creation of function /QTQVC/OPEN_STREAM returned after 00:00:00
2011-01-24 19:26:01 Progress Creation of function /QTQVC/FETCH_STREAM returned after 00:00:00
2011-01-24 19:26:01 Progress OpenStream called with SQL = "SELECT * FROM /QTQVC/JOB_SQL", PACKETSIZE = 20000, TRACE = "0", TIMEOUT_BATCH = "600", CHECK_SEPARATOR = "1", CONVROUTINE = "1"
2011-01-24 19:26:08 Progress OpenStream invoked. Jobnumber is 20110124192602
2011-01-24 19:26:08 Progress Jobnumber is 20110124192602
2011-01-24 19:26:08 Progress Calling FetchStream
2011-01-24 19:26:13 Progress Reply from FetchStream received
2011-01-24 19:26:13 Progress 1 ms delay
2011-01-24 19:26:13 Progress Calling FetchStream
2011-01-24 19:26:19 Progress Reply from FetchStream received
2011-01-24 19:26:19 Progress 10 ms delay
2011-01-24 19:26:19 Progress Calling FetchStream
2011-01-24 19:26:24 Progress Reply from FetchStream received
2011-01-24 19:26:24 Progress 10 ms delay
2011-01-24 19:26:24 Progress Calling FetchStream
2011-01-24 19:26:29 Progress Reply from FetchStream received
2011-01-24 19:26:29 Progress 10 ms delay
2011-01-24 19:26:29 Progress Calling FetchStream
2011-01-24 19:26:32 Progress Reply from FetchStream received
2011-01-24 19:26:32 Progress Successful fetch of 64 rows
2011-01-24 19:26:32 Error The received data record does not have the correct number of fields. It may have been truncated. Check if SAP string contains a NULL-character.
Received data is: "200^20110112172603^10 ^select ^"
The incorrect field is number: 1
Statement is: SELECT * FROM /QTQVC/JOB_SQL
2011-01-24 19:26:32 Progress Creation of function /QTQVC/OPEN_STREAM returned after 00:00:00
2011-01-24 19:26:32 Progress Creation of function /QTQVC/FETCH_STREAM returned after 00:00:00
2011-01-24 19:26:32 Progress OpenStream called with SQL = "SELECT * FROM /QTQVC/TRACE", PACKETSIZE = 20000, TRACE = "0", TIMEOUT_BATCH = "600", CHECK_SEPARATOR = "1", CONVROUTINE = "1"
2011-01-24 19:26:40 Progress OpenStream invoked. Jobnumber is 20110124192633
2011-01-24 19:26:40 Progress Jobnumber is 20110124192633
2011-01-24 19:26:40 Progress Calling FetchStream
2011-01-24 19:26:45 Progress Reply from FetchStream received
2011-01-24 19:26:45 Progress 1 ms delay
2011-01-24 19:26:45 Progress Calling FetchStream
2011-01-24 19:26:50 Progress Reply from FetchStream received
2011-01-24 19:26:50 Progress 2 ms delay
2011-01-24 19:26:50 Progress Calling FetchStream
2011-01-24 19:26:55 Progress Reply from FetchStream received
2011-01-24 19:26:55 Progress 4 ms delay
2011-01-24 19:26:55 Progress Calling FetchStream
2011-01-24 19:27:00 Progress Reply from FetchStream received
2011-01-24 19:27:00 Progress 8 ms delay
2011-01-24 19:27:00 Progress Calling FetchStream
2011-01-24 19:27:01 Progress Reply from FetchStream received
2011-01-24 19:27:01 Progress Resetting Server Context
2011-01-24 19:27:01 Progress Creation of function /QTQVC/OPEN_STREAM returned after 00:00:00
2011-01-24 19:27:01 Progress Creation of function /QTQVC/FETCH_STREAM returned after 00:00:00
2011-01-24 19:27:01 Progress OpenStream called with SQL = "SELECT * FROM /QTQVC/USERCONT", PACKETSIZE = 20000, TRACE = "0", TIMEOUT_BATCH = "600", CHECK_SEPARATOR = "1", CONVROUTINE = "1"
2011-01-24 19:27:02 Progress OpenStream invoked. Jobnumber is 20110124192702
2011-01-24 19:27:02 Progress Jobnumber is 20110124192702
2011-01-24 19:27:02 Progress Calling FetchStream
2011-01-24 19:27:02 Progress Reply from FetchStream received
2011-01-24 19:27:02 Progress Resetting Server Context
2011-01-24 19:27:02 Progress Creation of function /QTQVC/OPEN_STREAM returned after 00:00:00
2011-01-24 19:27:02 Progress Creation of function /QTQVC/FETCH_STREAM returned after 00:00:00
2011-01-24 19:27:02 Progress OpenStream called with SQL = "SELECT * FROM /QTQVC/TABLECONT", PACKETSIZE = 20000, TRACE = "0", TIMEOUT_BATCH = "600", CHECK_SEPARATOR = "1", CONVROUTINE = "1"
2011-01-24 19:27:03 Progress OpenStream invoked. Jobnumber is 20110124192703
2011-01-24 19:27:03 Progress Jobnumber is 20110124192703
2011-01-24 19:27:03 Progress Calling FetchStream
2011-01-24 19:27:03 Progress Reply from FetchStream received
2011-01-24 19:27:03 Progress Resetting Server Context
2011-01-24 19:27:03 Progress Disconnected
2011-01-24 19:27:03 Error /QTQVC/FETCH_STREAM failed after 00:00:00 Key = RFC_INVALID_HANDLE (An invalid handle was passed to the API call)



Thanks to interest my problem.

pover
Luminary Alumni
Luminary Alumni

I would report this to QlikView support and at the same time I would test other versions of the QV SAP Connector. Recently we had a problem with the 5.5 version, but when we tried the 5.4 version it worked fine. Just make sure to always use the same transport version as the client version.

Regards.

suniljain
Master
Master

when I installed QVC 5.5 at that time i get same error but when I run ReLoadSAPDD.qvw second day it worked fine.

so pls execute it one more time.

Pls Perform following exercise in SAP R/3 so that I will clear where is actual problem.

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

1.1.1 Testing SQL Statements - /QTQVC/SQL

This transaction makes it possible to test SQL Select statements. After installing the transports and creating a User, you can use this transaction to test that everything has been installed correctly; Log on with the newly created User and try this transaction: /n/QTQVC/SQL.

    • Key in the SQL statement.
    • Click on the "Open Stream"-button.
    • Click on the Fetch Stream"-button to view the result.

if this is working then error is in QV side not a SAP Side.


Not applicable
Author

Hy,

I have downgrade the connector to v5.4 on the Qlikview server slide and it's works fine.
I have send a ticket to Qlikview.


Thank's for your help

Not applicable
Author

Hi there,

We have the same problem. Has QlikTech resolved your issue yet??

Dave.

Not applicable
Author

Hi,

I don't know if they have a new release of v5.5, but if you want to solve you're problem you have to installe the v5.4 on the Qlikview server.

Not applicable
Author

Hi Pacard,

Thanks, yes we have reverted back to sap connector v5.4 GA.

We have tried v5.5 SR3 on a sap bw test box and a 32bit test PC and get the same problem even though backend transports and front end clients are in synch. It will be interesting to see how fast QlikTech respond to your ticket. Anyway I will keep checking http://global.qlik.com/download/ to see when a new version of the sap connector pops up.

Cheers.

Dave.