Error in Extractor Connector after Upgrade 5.8 SR4 to 6.3.2

[#1]

Dear experts!

after QV Upgrade to 12.10.2 SR2 we did also an upgrade of the QV-SAP-Connector (Old: 5.8 SR4 / New: 6.3.2).

We did only the Windows-Upgrade (uninstall old version & install new version; service for Qlik SAP Network Server stopped during this). We didn't make any changes in SAP environment.

We only use the Extractor Connector.

The QV-Server is connected to three SAP-Server with these logical systems:

SAP-DEV: QVEXTR0000

SAP-TEST: QVEXTR9999

SAP-PROD: QVEXTR9999

The same naming of TEST and PROD is chosen because of SAP System copies. This worked fine with the old connector.

Within the QV application the "Test Connection" after creating the connection string is successful.

But script execution differs. On SAP-DEV it is successful, on TEST and PROD it fails with the following error:

FAILED  Error: field 'RLOGSYS' not found

SQL EXTRACTOR 0COMP_CODE_TEXT

TFRMETHOD T  

UPDMODE F  

EXTRLANGUAGE E  

LOGSYS QVEXTR9999

The DataSource does not matter, it is always the same behavior.

Can someone help me?

Thanks!

[Hakan_Ronningberg]

Hi Markus,

For the systems where it is not working, can you attach the Extractor connector log (named like QvSAPExtr_20160830_122350.txt) and the service log (named like SrvService_20160614_091022.txt or Server_20160516_111212.txt)? The Service log is found on the server where the Extractor service is running.

Path to log files: C:\ProgramData\QlikTech\Custom Data\QvSAPConnector\Log.

Regards,

Hakan

[#3]

Hi Hakan,

here ist the log:

Thanks!

[Hakan_Ronningberg]

Hi Markus,

For the system not working, I can see that you are using a SAP transport with your own naming (E20K902849).

The system that is working is using the Qlik original transport E66K900047.

Please check that the transport E20K902849 is really a copy of E66K900047.

Thanks,

Hakan

[Hakan_Ronningberg · Accepted solution]

Hi,

Unfortunately the backward compatibility is not working for older connector versions if the Qlik original transport is not used. From release 6.1.2 the backward compatibility is working regardless of the name of the used tranport.

To make it work in your case, you need to import the original Qlik SAP transport E66K900047 directly into all systems.

Regards,

Hakan

[#6]

Hi Hakan,

thanks, that should be the reason. As we installed the 5.8 SR4 connector on SAP side, we switched the objects to a SAP transport using our naming convention.

So as you proposed, now we are using 6.1.2 on windows side (and again do not change anything on sap side).

Now we're getting another error for all systems: "Unable to connect: missing HOST and/or PORT."

If we use the "Test connection" in script everything is fine. But if we execute the script (without any load statement and only with the connection string) the error above occurs.

Here is the Server-Log:

2017-04-06 21:43:08     Server: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\SrvService.exe Ver: 6.1.2+Build:01065.origin/release/6.1.2

2017-04-06 21:43:08     Server Port Number: 8680

2017-04-06 21:44:55     FAILED

LOCATION    CPIC (TCP/IP) on local host with Unicode

ERROR       partner '173.29.155.23:3300' not reached

TIME        Thu Apr 06 21:44:55 2017

RELEASE     720

COMPONENT   NI (network interface)

VERSION     40

RC          -10

MODULE      nixxi.cpp

LINE        3271

DETAIL      NiPConnect2: 173.29.155.23:3300

SYSTEM CALL connect

ERRNO       10060

ERRNO TEXT  WSAETIMEDOUT: Connection timed out

COUNTER     1

2017-04-06 21:44:57     Closing the endPointThread id: 1

And the QvSAPExtr-Log

2017-04-06 21:54:46     Connector: C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPConnector\QvSAPEXTRConnector.dll Ver: 6.1.2+Build:01065.origin/release/6.1.2

2017-04-06 21:54:46 Err Unable to connect: missing HOST and/or PORT.

2017-04-06 21:54:48     Socket timeout parameter (s): 900

2017-04-06 21:54:48 Err Connection failed.

END AT:

2017-04-06 21:56:34

Total run time: 00h 01m 48s

Are there problems with the downgrade?

-We stopped the service, uninstalled the service and did the uninstall for 6.3.2.

-We installed 6.1.2, installed and started the service.

-We applied the licence.

Thanks & Best Regards,

[Hakan_Ronningberg]

Hi Markus,

Sorry if my answer was a bit unclear. What I meant was that you need to import the SAP transport of release 6.1.2 or later (copied to your own naming convention) to make the backward compatibility work. Or import the original Qlik SAP transport E66K900047.

But as you need to import a transport, I would strongly recommend to import the latest release 6.3.2 or wait for release 6.4 which will be available in near future.

Regards,

Hakan

[#8]

Hi Hakan,

after importing the SAP Transport with the orginal name again everything is working fine.

We did not have to change anything on sap side and now we have on SAP side 5.8 SR4 and on Windows side 6.3.2.

Thanks again!

[#9]

Hi Markus,

Before upgrading to 6.3.2, have you done any testing on connector?

If yes, Please let me know what kind of testing you performed?

Thanks and Regards,

Rasool.

[#10]

Hi Markus,

Before upgrading to 6.3.2, have you done any testing on connector?

If yes, Please let me know what kind of testing you performed?

Thanks and Regards,

Rasool.