Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
mrov5903
Contributor
Contributor

Error: Mismatch Error in TransportsHaveCorrectVersion

Hello,

we have a follow message error:

Error: Mismatch Error in TransportsHaveCorrectVersion: Mismatch between SAP Transport and connector versions. Please import the correct SAP transport. Transport with version E6DK900873 installed on date 2018-02-23 was found on system with SAP basis 701. This connector requires SAP Transport with version WRONG_TRANSPORT.

04/05/2018 11:24:55:       General Script Error

04/05/2018 11:24:55:       Execution Failed

04/05/2018 11:24:55:      Execution finished.

On the sap sever with release sap : sap_basis 701 it  have been installed the change request  in this sequence:

on date 04.04.2017 ,   E6DK900804, E6DK900594 and E6DK900774

on date 23 of february 2018 , E6DK900873 and  E6DK900818

Is it a problem of QlikView Version ,  on the client is 11.20.12852.0?

6 Replies
Peter_Cammaert
Partner - Champion III
Partner - Champion III

Which SAP Connector version are your trying to use to extract SAP tables? The SAP Connector version o nthe Windows side must match the transports up to a certain point.

mrov5903
Contributor
Contributor
Author

Hi Peter,

i don't know which sap connector version is used by application team, but i suppose that the last update with cr E6DK900873 is used and regards release 6.5.

Is possible call the old release (6.3).

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Maybe you should ask your Application Team then. It can only be one version.

Tomas_Sommergyll
Employee
Employee

Hi Mauro,

It would be helpful if you could attach the log file, see folder C:\ProgramData\QlikTech\Custom Data\QvSAPConnector\Log.

The first few lines showing the connector name and version are essential, and also the lines showing the error text.

Thanks,

Tomas

mrov5903
Contributor
Contributor
Author

Hi Tomas , follows the first lines:

04/05/2018 11:24:51:      Execution started.

04/05/2018 11:24:51:      QlikView Version:11.20.12852.0

04/05/2018 11:24:51:      CPU Target                    x64

04/05/2018 11:24:51:      Operating System              Windows Server 2008 R2 Enterprise Service Pack 1 (64 bit edition)

04/05/2018 11:24:51:      Wow64 mode                    Not using Wow64

04/05/2018 11:24:51:      MDAC Version                  6.1.7601.17514

04/05/2018 11:24:51:      MDAC Full Install Version     6.1.7601.17514

and the last lines:

04/05/2018 11:24:55:       Error: Mismatch Error in TransportsHaveCorrectVersion: Mismatch between SAP Transport and connector versions. Please import the correct SAP transport. Transport with version E6DK900873 installed on date 2018-02-23 was found on system with SAP basis 701. This connector requires SAP Transport with version WRONG_TRANSPORT.

04/05/2018 11:24:55:       General Script Error

04/05/2018 11:24:55:       Execution Failed

04/05/2018 11:24:55:      Execution finished

Peter_Cammaert
Partner - Champion III
Partner - Champion III

That is not the log file contained in the directory that Thomas mentioned in his reply. You posted part of the DocumentLog which is a different log file detailing the script statements as they are read, translated and executed (and their result).

At a certain point in your script, the engine encounters a CUSTOM CONNECT statement which causes the script engine to load a particular connector as detailed in the connect statement. That connector is a separate program that generates a different log file. To find out which Connector version has been installed at your place, we need the SAP Connector log. See here for the exact location on your QlikView server:

It would be helpful if you could attach the log file, see folder C:\ProgramData\QlikTech\Custom Data\QvSAPConnector\Log.

The SAP Connector log of recent Connector versions has a pretty long file name formatted like this:

QvSAPSqlConnector-YYYYMMDDHHMMSSFFF-XXXXXXXX_XXXXXXXX_XXXXXXXX_XXXXXXXX.log

The YYYYMMDDHHMMSSFFF-part specifies a timestamp so that you can figure out which log corresponds to which script run.

If you don't have access to the QlikView server machine, ask someone who does have access.