Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
RemcoS
Contributor II

Connect Qlik Cloud Trial to local SQL Server, how on earth...

Hi,

In my former job we had Qlik Sense connected to Snowflake and that worked really well. Now I want to show Qlik in my new organization and to do so I want to show things. But I cannot get it connected to my local SQL server. How can this be done? I am familiar with the load script etc. but I am lost with ODBC connections, wich one to choose, how to set up etc. The next question is how to get the Vizlib extensions to work. I imported the zip file but I cannot see the extensions... Help...

Labels (1)
4 Replies
JonnyPoole
Former Employee

To connect to your local SQL Server you'll need to deploy the 'Direct Access - Data Gateway' on a windows server within your firewall.  

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/direct-access-g...

Once installed, the gateway can connect to your SQL Server from within your network and that solves the firewall issue. 

From Qlik Cloud, you will then select the highlighted connection option and proceed with the rest of the connectivity details and credentials. 

JonnyPoole_0-1709251003538.png

 

In this setup, the cloud is never given access to the data gateway machine. All communication from gateway to qlik cloud is outbound from the gateway to the cloud over port 443.

 

JonnyPoole_1-1709251046419.png

 

 

RemcoS
Contributor II
Author

Thank you, all rather complex... I get stuck when it comes to the generation of the key in the CMD box. 

Sequence:

C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent>connectoragent qcs set_config --tenant_url ****ri15atw7yps.de.qlikcloud.com
DirectAccessAgent Control Program completed successfully.

Then:

C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent>connectoragent qcs generate_keys
DirectAccessAgent Control Program completed successfully.

Then:

C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent>connectoragent gcs get_registration
connector-agent starting as standard .net core process....

But where I expect to get a key I get:

{"TimeStamp":"01-03-2024 08:44:38.676","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"environment-info: Gateway version=1.6.3, processor count=4, working set=31 MB, OS=Microsoft Windows NT 10.0.19045.0, TimeZone offset=1:00","Exception":null}
{"TimeStamp":"01-03-2024 08:44:38.766","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"AGENT_PORT=0","Exception":null}
{"TimeStamp":"01-03-2024 08:44:38.767","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Using default port from config 0","Exception":null}
{"TimeStamp":"01-03-2024 08:44:38.767","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Setting CONNECTOR_AGENT_PORT for non-default port","Exception":null}
{"TimeStamp":"01-03-2024 08:44:39.316","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"dcaas url: ","Exception":null}
{"TimeStamp":"01-03-2024 08:44:40.401","Thread":"1","Level":"ERROR","Message":"System.InvalidOperationException: Dynamic port binding is not supported when binding to localhost. You must either bind to 127.0.0.1:0 or [::1]:0, or both.\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.LocalhostListenOptions..ctor(Int32 port)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.ParseAddress(String address, Boolean& https)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IEnumerable`1 listenOptions, AddressBindContext context, CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host)\r\n at Qlik.ConnectorAgent.AgentProcessBase.StartAgent(Boolean isService)","Exception":null}

 

Any idea how to proceed?

 

Thank you!

RemcoS
Contributor II
Author

It seems that does not work when the SQL server is a local installation.... grrr

JonnyPoole
Former Employee

"

You installed the gateway directly on the SQL Server instance? Yes I could see potential problems. The help has this blurb in it (below). Did you also happen to have another Qlik Sense product on the same server? That will also cause a conflict.

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/direct-access-g...

  • Direct Access gateway should be installed on a dedicated Windows Server as stipulated in the system requirements below. Do not install it on the actual database server or alongside other Qlik products, including but not limited to, Qlik DataTransfer, Qlik Sense Desktop, and Qlik Sense Enterprise.