Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
TobiasW
Partner - Contributor III
Partner - Contributor III

Can't reach Qlik Lineage URL

Hey everyone,

I have an issue with the lineage connector, i have the following in my log:

2022-08-11 12:31:29.1671 1 Topshelf.HostFactory INFO Configuration Result:
[Success] Name Qlik Lineage Connector
[Success] DisplayName Qlik Lineage Connector Service
[Success] ServiceName Qlik Lineage Connector
2022-08-11 12:31:29.2453 1 Topshelf.HostConfigurators.HostConfiguratorImpl INFO Topshelf v4.3.0.0, .NET Framework 4.8.4110.0 (4.0.30319.42000)
2022-08-11 12:31:29.2765 1 QLCService INFO QLCService v1.1.0.0
2022-08-11 12:31:29.3242 1 Topshelf.Runtime.Windows.WindowsHostEnvironment DEBUG Started by the Windows services process
2022-08-11 12:31:29.3242 1 Topshelf.Builders.RunBuilder DEBUG Running as a service, creating service host.
2022-08-11 12:31:29.3242 1 Topshelf.Runtime.Windows.WindowsServiceHost INFO Starting as a Windows service
2022-08-11 12:31:29.3242 1 Topshelf.Runtime.Windows.WindowsServiceHost DEBUG [Topshelf] Starting up as a windows service application
2022-08-11 12:31:29.3242 6 Topshelf.Runtime.Windows.WindowsServiceHost INFO [Topshelf] Starting
2022-08-11 12:31:29.3398 6 Topshelf.Runtime.Windows.WindowsServiceHost DEBUG [Topshelf] Current Directory: C:\Program Files\Qlik\LineageConnector
2022-08-11 12:31:29.3398 6 Topshelf.Runtime.Windows.WindowsServiceHost DEBUG [Topshelf] Arguments:
2022-08-11 12:31:30.1211 6 QLCService INFO Starting QLCService
2022-08-11 12:31:30.2773 6 QLCService WARN Could not read C:\ProgramData\Qlik\LineageConnector\svc.config, loads default
2022-08-11 12:31:30.7937 6 QLCService INFO Audit logging: False, Full
2022-08-11 12:31:30.7937 6 QLCService INFO Running as service
2022-08-11 12:31:30.7937 6 QLCService INFO Use Authentication: True
2022-08-11 12:31:30.7937 6 QLCService INFO Authentication type: Internal
2022-08-11 12:31:30.7937 6 QLCService INFO Disable scheduler: False
2022-08-11 12:31:30.7937 6 QLCService INFO Persistence engine: LiteDB
2022-08-11 12:31:33.9049 6 QLCService INFO Application path is C:\ProgramData\Qlik\LineageConnector
2022-08-11 12:31:33.9049 6 QLCService INFO Using DataDirectory C:\ProgramData\Qlik\LineageConnector
2022-08-11 12:31:33.9206 6 BackupJobService INFO Database backup created: C:\ProgramData\Qlik\LineageConnector\app-settings.dat -> C:\ProgramData\Qlik\LineageConnector\backup\app-settings-20220811_123133.dat
2022-08-11 12:31:34.2643 6 QLCService INFO Database migration. Current version 0
2022-08-11 12:31:34.2643 6 QLCService INFO Database up to date, version is 0
2022-08-11 12:31:34.2800 6 QLCService INFO License domain used: Domain.local
2022-08-11 12:31:34.2800 6 QLCService INFO Licensed to for domain until 12.08.2022 00:00:00
2022-08-11 12:31:34.7650 6 QLCService INFO Audit logging: False, Full
2022-08-11 12:31:34.7650 6 QLCService INFO Checking existing URL reservations to endpoint=https://*:4114/ [NTLM=False]
2022-08-11 12:31:34.8119 16 DependencyExplorerCacheService INFO Dependency Explorer cache service initialized
2022-08-11 12:31:34.8119 16 QLCService INFO Starting graph database instances
2022-08-11 12:31:34.8119 16 InstanceManager INFO Initializing asset databases...
2022-08-11 12:31:34.8119 16 InstanceManager INFO Loading prj databases
2022-08-11 12:31:34.8119 16 InstanceManager INFO Done!
2022-08-11 12:31:34.8119 16 QLCService INFO Checking category consistency
2022-08-11 12:31:34.8275 16 QLCService INFO Database thread done, waiting for services...
2022-08-11 12:31:34.9369 6 QLCService INFO No existing reservation found.
2022-08-11 12:31:34.9369 6 QLCService INFO Adding URL reservation to endpoint=https://*:4114/ and user=EVERYONE
2022-08-11 12:31:35.0775 6 QLCService ERROR Error in Startup System.Exception: Error trying to reserve URL endpoint. Make sure service account is local admin and no other application is using 'https://*:4114/'
bei QLCService.Installer.SetupConfigurationHelper.VerifyUrlReservation(String urlEndpoint, Boolean isNtlmEndpoint)
bei QLCService.QLCSelfHost.Start()
2022-08-11 12:31:35.0932 6 Topshelf.Runtime.Windows.WindowsServiceHost INFO [Topshelf] Started

These Messages got my attention:

2022-08-11 12:31:30.2773 6 QLCService WARN Could not read C:\ProgramData\Qlik\LineageConnector\svc.config, loads default

2022-08-11 12:31:35.0775 6 QLCService ERROR Error in Startup System.Exception: Error trying to reserve URL endpoint. Make sure service account is local admin and no other application is using 'https://*:4114/'
bei QLCService.Installer.SetupConfigurationHelper.VerifyUrlReservation(String urlEndpoint, Boolean isNtlmEndpoint)
bei QLCService.QLCSelfHost.Start()

So I tried different users and made sure they have access to the svc.config (they all had) and they were local admins.
>Didn't help

I tried configuring another Port
> I got still the Warning that the svc.config couldn't be read, but it showed the new port in the Error message, so from my point of view: It was able to read the config file

Tested if something was already running on the port with "netstat -ano -p tcp" according to this article: Determine which program uses or blocks a port – Print Support Center
>Nothing on Port 4114 or any other Port i tried

I tested it on a QlikSense Server; QlikView Server and a Clean Server
>Always the same result

Downloaded an older Version from the Download Portal (original used the Download Link from Qlik SaaS)
>Still the same Error

Can I get some more Logs somehow or does anyone has an idea what could be the issue?

Thanks in advance!
Tobi

Labels (1)
2 Solutions

Accepted Solutions
TobiasW
Partner - Contributor III
Partner - Contributor III
Author

Hey everyone,

i figured out how to "fix" it, but I honestly still don't know what actual the issue is.

In the svc.config change:

"UseTLS": true; to "UseTLS": false;

Honestly I have no idea why this helps, but in my case it worked.

Maybe someone could explain it? Especially for other users who get this kind of issue!

Best regards,
Tobi

View solution in original post

qlikjarbratt
Employee
Employee

Hi Tobi and Felix,

We had anomaly behaviours with reserving the URL endpoints and binding the self-signed certificate to use TLS. We have done some work in order to automatically recover from these events, especially if these are carried out outside of the service itself.

We just released a new installer which will (hopefully) resolve these issues you are seeing

Release December 2022 SR2 · qlik-download/lineage-connector (github.com)

The information node will soon highlight in QLC as well to indicate there is a new version out.

Best regards,

Marcus @Anonymous QLC team

View solution in original post

5 Replies
TobiasW
Partner - Contributor III
Partner - Contributor III
Author

Hey everyone,

i figured out how to "fix" it, but I honestly still don't know what actual the issue is.

In the svc.config change:

"UseTLS": true; to "UseTLS": false;

Honestly I have no idea why this helps, but in my case it worked.

Maybe someone could explain it? Especially for other users who get this kind of issue!

Best regards,
Tobi

schefflera
Contributor III
Contributor III

Hey Tobi,

same with me. After UseTLS = false, it works properly.

TLS has something to do with the secure transfer from data (former SSL).

Would be nice to have further info about how to solver the issue without turning off security entries! Maybe someone from Qlik Tech knows it?

Kinde regards,

Felix

qlikjarbratt
Employee
Employee

Hi Tobi and Felix,

We had anomaly behaviours with reserving the URL endpoints and binding the self-signed certificate to use TLS. We have done some work in order to automatically recover from these events, especially if these are carried out outside of the service itself.

We just released a new installer which will (hopefully) resolve these issues you are seeing

Release December 2022 SR2 · qlik-download/lineage-connector (github.com)

The information node will soon highlight in QLC as well to indicate there is a new version out.

Best regards,

Marcus @Anonymous QLC team

BhaskarD
Contributor
Contributor

Hey, 

Working with new Qlik Lineage connector October-2023 Release. But, facing the same issue. We must change the svc.config file to access.

Hope, this might get fix soon for Secure Access.

barin691
Contributor
Contributor

To me it's more like Qlik is a tool you should only need because you've made a series of bad decisions, like a payday loan service, or a clean needle program.

Like those tools it's situationally useful, but if you had avoided those initial bad decisions, there's no need for that kind of tool at all.