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

Error Cannot access to Qlik Lineage Connector

Hi community,

I just install Qlik Lineage Connector on a test environment. Then, I use an admin AD account which have all rights. No trouble during setup, eveything seems to be ok but my browser displayed error 404.

The log display this error : 

2022-07-12 16:14:40.2242 1 QLCService INFO QLCService v1.1.0.0
2022-07-12 16:14:40.2711 7 QLCService INFO Starting QLCService
2022-07-12 16:14:40.1779 1 Topshelf.HostFactory INFO Configuration Result:
[Success] Name Qlik Lineage Connector
[Success] DisplayName Qlik Lineage Connector Service
[Success] ServiceName Qlik Lineage Connector
2022-07-12 16:14:40.2242 1 Topshelf.HostConfigurators.HostConfiguratorImpl INFO Topshelf v4.3.0.0, .NET Framework 4.8.4110.0 (4.0.30319.42000)
2022-07-12 16:14:40.2394 1 Topshelf.Runtime.Windows.WindowsHostEnvironment DEBUG Started by the Windows services process
2022-07-12 16:14:40.2394 1 Topshelf.Builders.RunBuilder DEBUG Running as a service, creating service host.
2022-07-12 16:14:40.2394 1 Topshelf.Runtime.Windows.WindowsServiceHost INFO Starting as a Windows service
2022-07-12 16:14:40.2394 1 Topshelf.Runtime.Windows.WindowsServiceHost DEBUG [Topshelf] Starting up as a windows service application
2022-07-12 16:14:40.2551 7 Topshelf.Runtime.Windows.WindowsServiceHost INFO [Topshelf] Starting
2022-07-12 16:14:40.2551 7 Topshelf.Runtime.Windows.WindowsServiceHost DEBUG [Topshelf] Current Directory: C:\Program Files\Qlik\LineageConnector
2022-07-12 16:14:40.2551 7 Topshelf.Runtime.Windows.WindowsServiceHost DEBUG [Topshelf] Arguments:
2022-07-12 16:14:40.4426 7 QLCService INFO Audit logging: False, Full
2022-07-12 16:14:40.4426 7 QLCService INFO Running as service
2022-07-12 16:14:40.4426 7 QLCService INFO Use Authentication: True
2022-07-12 16:14:40.4426 7 QLCService INFO Authentication type: Internal
2022-07-12 16:14:40.4426 7 QLCService INFO Disable scheduler: False
2022-07-12 16:14:40.4426 7 QLCService INFO Persistence engine: LiteDB
2022-07-12 16:14:40.5835 7 QLCService INFO Application path is C:\ProgramData\Qlik\LineageConnector
2022-07-12 16:14:40.5835 7 QLCService INFO Using DataDirectory C:\ProgramData\Qlik\LineageConnector
2022-07-12 16:14:40.5988 7 BackupJobService INFO Database backup created: C:\ProgramData\Qlik\LineageConnector\app-settings.dat -> C:\ProgramData\Qlik\LineageConnector\backup\app-settings-20220712_161440.dat
2022-07-12 16:14:40.6621 7 QLCService INFO Database migration. Current version 0
2022-07-12 16:14:40.6621 7 QLCService INFO Database up to date, version is 0
2022-07-12 16:14:40.6769 7 QLCService INFO License domain used: DEMO.LOCAL
2022-07-12 16:14:40.6769 7 QLCService INFO Licensed to for domain until 13/07/2022 00:00:00
2022-07-12 16:14:40.8024 7 QLCService INFO Audit logging: False, Full
2022-07-12 16:14:40.8024 7 QLCService INFO Checking existing URL reservations to endpoint=https://*:4114/ [NTLM=False]
2022-07-12 16:14:40.8176 11 DependencyExplorerCacheService INFO Dependency Explorer cache service initialized
2022-07-12 16:14:40.8176 11 QLCService INFO Starting graph database instances
2022-07-12 16:14:40.8176 11 InstanceManager INFO Initializing asset databases...
2022-07-12 16:14:40.8176 11 InstanceManager INFO Loading prj databases
2022-07-12 16:14:40.8176 11 InstanceManager INFO Done!
2022-07-12 16:14:40.8176 11 QLCService INFO Checking category consistency
2022-07-12 16:14:40.8176 11 QLCService INFO Database thread done, waiting for services...
2022-07-12 16:14:40.8488 7 QLCService INFO No existing reservation found.
2022-07-12 16:14:40.8488 7 QLCService INFO Adding URL reservation to endpoint=https://*:4114/ and user=EVERYONE
2022-07-12 16:14:41.0221 7 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/'
à QLCService.Installer.SetupConfigurationHelper.VerifyUrlReservation(String urlEndpoint, Boolean isNtlmEndpoint)
à QLCService.QLCSelfHost.Start()
2022-07-12 16:14:41.0221 7 Topshelf.Runtime.Windows.WindowsServiceHost INFO [Topshelf] Started


Could you give an hand ?

Thanks

Labels (1)
6 Replies
Vinay_B
Support
Support

Hi @lucpechali 

Below is the guide to installing Lineage connector: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/QlikLineageConnectors/ql... 

Does the issue still occur?

Please make sure to use the Local admin account for the installation. Qlik Lineage Connectors are by default set up to use the Local System account as the running account. This needs to be changed under Microsoft Services if the default does not have read access to your file environment.

By looking at the log, some other service is consuming the local server  "https://localhost:4114 or http://<servername>:4114"

 

 

 

If this resolves your query, please click on "Accept as Solution" for confirmation. Thanks!
lucpechali
Partner - Contributor III
Partner - Contributor III
Author

Hi Vinay_B

I followed the installation guide correctly.
However, even on a new machine without any product and with internet access, I never got it to work.
Is there a particular configuration of .Net for this product that I would have missed ?

TobiasW
Partner - Contributor III
Partner - Contributor III

Hello Lucpechali,

I face the same error right now. Did you find a solution?

I tried multiple ports and different users. Nothing helped sadly.

lucpechali
Partner - Contributor III
Partner - Contributor III
Author

Unfortunately, no

TobiasW
Partner - Contributor III
Partner - Contributor III

@lucpechali 

I found a solution for myself: Solved: Can't reach Qlik Lineage URL - Qlik Community - 1967703

Maybe you wanna give it a try.

amara25
Contributor
Contributor

When the company I worked for started the Data Lake journey we followed an archeticture that had the Data Lake feed the raw data to the Data Warehouse. That essentially required all new DW use cases to flow through the DL first. The pros to that really help the DL as a product more than the DW since the DL wants to provide that view of all datasets across the company for exploration and ML use cases. We have use cases however where more real-time reporting will go to both systems seperately via events. This avoids any processing in-between the DL and DW. We basically default to DL->DW unless there's a requirement that can't be met because of that pattern. I think lineage is a little easier with DL->DW vs. having two seperate pipelines but it'll all depend on the requirements from the end-users.