Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
Juliancrg95
Partner - Contributor
Partner - Contributor

Qlik SAP connector: Connector reply error: Mismatch detected. The SAP generated spool file cannot be

After the upgrade from the Qlik SAP Connector 7.0.0 to the 7.0.3 version (With Transports) we get this error when running our extraction. 

Connector reply error: Mismatch detected. The SAP generated spool file cannot be read. (count: LINES 16013, LINES_BUFFER 16016)

---

The error occurred here:

Select SAPREPORT (REPORT (RM07MLBS), VARIANT (Z_CIERREMPKQLI), ROWS_PER_RECORD (1), FIELD_AUTO_COLUMNS (3))

We verified the spool file is generated in SAP.

1 Solution

Accepted Solutions
Juliancrg95
Partner - Contributor
Partner - Contributor
Author

Hi Hakan.

Thanks for your quick response.

we solved this issue redoing the extraction using qlikview.

there were some text fields that couldnt load because they applied a num to them, we excluded the text records. and the issue was solved.

 

Julian

View solution in original post

3 Replies
Hakan_Ronningberg

Hi,

There is a workaround that should solve this error:

Step 1. Create a new folder named 'QvSAPReportConnector' and put that next to the folder QvSAPConnector in the path: C:\Program Files\Common Files\QlikTech\Custom Data.

Step 2. Move the file QvSAPReportConnector.dll from the folder QvSAPConnector to the folder QvSAPReportConnector.

Step 3. Temporary install the SAP connector release 6.6 on another server. Release 6.6 is available on the Qlik download site. Copy the files
icudt34.dll
icuin34.dll
icuuc34.dll
libicudecnumber.dll
libsapucum.dll
sapnwrfc.dll
from the folder QvSAPConnector on this server to the newly created folder QvSAPReportConnector on the release 7.0.3 server.

Step 4. Remove the release 6.6 folders from the temporary installation.

Restart QlikView and then it should work!

Regards,
Håkan

Juliancrg95
Partner - Contributor
Partner - Contributor
Author

Hi Hakan.

Thanks for your quick response.

we solved this issue redoing the extraction using qlikview.

there were some text fields that couldnt load because they applied a num to them, we excluded the text records. and the issue was solved.

 

Julian

AlexOmetis
Partner Ambassador
Partner Ambassador

We have this issue having upgraded from 7.0.0 to 8.0.0 (Connector only - transports are still 7.0.0). I'm going to have to try something similar to what @Hakan_Ronningberg suggested to get it working again... Unless the advice has been updated? 

 

EDIT: The process is slightly different for going from 8.0.0 to 7.0.0 than @Hakan_Ronningberg outlined - there's already a QvSAPReportConnector folder so you just have to empty this and replace it with the 7.0.0 files (some of which have slightly different names - 50 instead of 34 at the end). This worked for me - but is very much a workaround not a fix! 

Qlik Partner Ambassador 2024