Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
rolmontero
Partner - Creator
Partner - Creator

Qlik Cloud Data Integration Configuration Issues

Hello everyone,

 

I am new to QCDI and at the moment, I am creating a laboratory in order to test Qlik Cloud Data Integration. However, I cannot manage to make it work. On AWS, I have created a Red Hat machine in which I have installed Data Movement, a Windows machine with SQL Server and a demo database (AdventureWorks2019) along with Direct Access. Furthermore, I have also signed up for a Snowflake trial. My idea is to move data from SQL Server to Snowflake using QCDI. The problems I am facing are the following:

1. The Linux Machine does not ping the Windows machine. On the contrary, the Windows machine can see the Linux environment.

2. I cannot connect directly with Qlik Cloud to SQL Server on AWS. I have one SA user, and it is the same I use to connect to the local instance with SQL Server Management Studio.

rolmontero_1-1682357799883.png

 

rolmontero_2-1682357970849.png

 

Things that I have done so far:

1. Disable firewall on Windows machine and enable these ports:

rolmontero_0-1682357764565.png

2. Both gateways are up and running

rolmontero_3-1682358142248.png

 

Am I missing an AWS configuration to connect these pieces?

 

Best regards

 

 

5 Replies
TimGarrod
Employee
Employee

Did you install the SQL Server driver on the gateway machine?
rolmontero
Partner - Creator
Partner - Creator
Author

Hello @TimGarrod ,

 

I have not installed the SQL Driver whatsoever. I will search for a guide to do so.

 

Thanks

TimGarrod
Employee
Employee

rolmontero
Partner - Creator
Partner - Creator
Author

Hello everyone,

I have configured the machines from scratch again, and I was able to install the MSSQL Driver 17 on the RedHat server. Additionally, both Windows machine with SQL Server and Linux with Data Movement can see each other. Furthermore, I have also configured the replication section from MSSQL. I have created a QCDI task, and I am currently on the onboard section, but I am getting the following error:

Service returned unsuccessful status code '404' on 'GET' at '/v1/replicate-agents/$onboarding_LANDING_SAAS_MANAGED$/tasks/7WDfBKBdJ_o_0VCnrg-JF68YuySq6blk/source-tables' with 'Not Found' - content: '{"errors":[{"title":"Failed to retrieve source tables","detail":"QEM-PROXY-REQUEST-FAILED-1, Proxy request to remote Data gateway failed, QEM-19, HTTP request failed, Check connection on Data gateway to Replicate server","code":"REPLICATE-AGENT-GET-SOURCE-TABLES-FAILED","status":404,"meta":{"id":"te129aO3BKwhUJXVDchUN4Hd6MQPPeP-","serverName":"local_repsrv","ctx":{"msgId":"VnZ8T3vO-twCgP1cxce6CLw-vvNOxXH5","guid":null,"detailedMessage":"SYS,GENERAL_EXCEPTION,Command get_table_list failed when getting the list.","exceptionCode":"GENERAL_EXCEPTION","errorMessage":"SYS-E-HTTPFAIL, Command get_table_list failed when getting the list.."},"code":"QEM-SERVICE-24"}}],"traceId":"00000000000000006f28edca2b81029c"}'

 

From the regular Qlik connection, I can access the tables and load data from that database.

rolmontero_0-1683317638630.png

 

Best regards

rolmontero
Partner - Creator
Partner - Creator
Author

Hello again,

Just in case you happen to stumble upon that error, it was only due to a lack of permissions on the database you would like to replicate. In my case, I am using SQL Server – Adventure Works database. I added these permissions to the user I am using in this lab by following this instructions:

Required permissions

To use Microsoft SQL Server (Log-Based) as a source in a landing task, the user specified in the Microsoft SQL Server (Log-Based) connection properties must be one of the following:

  • A member of both the db_owner database role and the sysAdmin fixed server role.
  • A member of the db_owner database role, but not a member of sysAdmin fixed server role. This also requires you to perform the procedures described in Setting up a non-sysadmin user in a standalone environment below.

 

rolmontero_0-1683578601283.png

 

Best regards