Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are having issues attempting to set up an Azure MSSQL database source - when testing the connection we receive the following error from Qlik (v2025.11):
RetCode: SQL_ERROR SqlState: FA004 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Failed to authenticate the user '8ffcd3a2-3e1b-4d6a-9ef0-993832e9c228' in Entra ID (Authentication option is 'ActiveDirectoryServicePrincipal').
00000945: 2026-05-12T17:17:09:683127 [AT_GLOBAL ]I: Qlik Replicate Server Log (V2025.11.0.285 3b9bf2f6ae88 Linux 6.12.13-200.fc41.aarch64 #1 SMP PREEMPT_DYNAMIC Sat Feb 8 20:30:50 UTC 2025 x86_64 64-bit, Revision:3a2220d5f81c24e3e19825b06ce8db2bbe0c9b7d, PID: 944) started at Tue May 12 17:17:09 2026 (at_logger.c:2763)
00000945: 2026-05-12T17:17:09:683762 [AT_GLOBAL ]I: Licensed to Qlik Replicate Express users (software license acceptance implied)Express license: You are running the Express Edition with reduced functionality (245 days remaining) (at_logger.c:2773)
00000945: 2026-05-12T17:17:09:683831 [AT_GLOBAL ]I: Log file encryption base "HbIFY1L3uWqjkVDdH/tnnQ==" (at_logger.c:2784)
00000945: 2026-05-12T17:17:09:683869 [INFRASTRUCTURE ]I: Crypto mode: Standard. (at_logger.c:1607)
00000945: 2026-05-12T17:17:09:692779 [SERVER ]T: The server is listening on TCP port 3550 (server.c:838)
00000945: 2026-05-12T17:17:09:719219 [UTILITIES ]I: Scheduler configuration has been loaded. (scheduler.c:606)
00000947: 2026-05-12T17:17:09:719831 [INFRASTRUCTURE ]I: Log cleanup thread successfully initialized and running. (logger.c:860)
00000945: 2026-05-12T17:17:09:726196 [TASK_MANAGER ]I: Feature flags for process are: (ar_feature_flags.c:232)
00000948: 2026-05-12T17:17:09:874422 [COMMUNICATION ]T: Client is connected to 127.0.0.1:3550 on port 50544 (at_lgnet.c:1713)
00000945: 2026-05-12T17:17:09:876632 [COMMUNICATION ]T: Accepted a new connection on port 3550 from 127.0.0.1:50544 (at_lgnet.c:1432)
00000945: 2026-05-12T17:17:09:958410 [SERVER ]I: Client session (ID 1248848983) allocated (dispatcher.c:276)
00000945: 2026-05-12T17:17:09:958809 [SERVER ]T: New session created (Session #1248848983) (server.c:2268)
00000948: 2026-05-12T17:17:10:73663 [REST_SERVER ]W: Failed to initialize pam configuration, pam authentication disabled. (atctl_serve.c:275)
00000948: 2026-05-12T17:17:10:76127 [REST_SERVER ]I: Agent was started successfully (listening on port 44444). (atctl_serve.c:402)
00000948: 2026-05-12T17:17:12:775409 [COMMUNICATION ]T: Accepted a new connection on port 44444 from 10.89.0.4:41488 (at_lgnet.c:1432)
00000948: 2026-05-12T17:17:12:847440 [COMMUNICATION ]T: Accepted a new connection on port 44444 from 10.89.0.4:41492 (at_lgnet.c:1432)
00000953: 2026-05-12T17:17:17:961280 [SERVER ]T: Validating ODBC driver for provider: 'ODBC Driver 18 for SQL Server' (sqlserver_endpoint_imp.c:1180)
00000953: 2026-05-12T17:17:17:964731 [SERVER ]T: Using provider: 'ODBC Driver 18 for SQL Server' (sqlserver_endpoint_imp.c:1249)
00000953: 2026-05-12T17:17:17:965066 [SERVER ]T: The folder '/opt/microsoft/msodbcsql18/lib64/' exists (sqlserver_api.c:80)
00000953: 2026-05-12T17:17:17:965633 [SERVER ]T: Get list files from folder '/opt/microsoft/msodbcsql18/lib64/' with filter. The result is '1' files (sqlserver_api.c:87)
00000953: 2026-05-12T17:17:17:966500 [SERVER ]I: ODBC driver 'ODBC Driver 18 for SQL Server' found as installed (sqlserver_endpoint_util.c:404)
00000953: 2026-05-12T17:17:17:966512 [SERVER ]T: ODBC driver 'ODBC Driver 18 for SQL Server' found as installed (sqlserver_endpoint_util.c:405)
00000953: 2026-05-12T17:17:17:966622 [SERVER ]T: ODBC driver 'ODBC Driver 17 for SQL Server' found as *NOT* installed (sqlserver_endpoint_util.c:405)
00000953: 2026-05-12T17:17:17:966728 [SERVER ]T: ODBC driver 'ODBC Driver 13 for SQL Server' found as *NOT* installed (sqlserver_endpoint_util.c:405)
00000953: 2026-05-12T17:17:17:967124 [SERVER ]T: App name connection parameter (user agent) is 'APP=QlikReplicate/2025.11 (microsoftazuresqlmscdc)' (sqlserver_endpoint_util.c:319)
00000953: 2026-05-12T17:17:17:967129 [SERVER ]T: sqlserver_src_set_odbc_connection_string(): connection string (without credentials): 'DRIVER={ODBC Driver 18 for SQL Server};SERVER=sql-eap-weu-lgrr-qa.database.windows.net;DATABASE=eap-db-lgrr-qa-11;Trusted_Connection=no;Encrypt=yes;TrustServerCertificate=yes;APP=QlikReplicate/2025.11 (microsoftazuresqlmscdc);' (sqlserver_endpoint_util.c:259)
00000953: 2026-05-12T17:17:18:10105 [SERVER ]I: Source endpoint 'Microsoft Azure SQL (MS-CDC)' is using provider syntax 'SQLServer' (provider_syntax_manager.c:1004)
00000945: 2026-05-12T17:17:18:910371 [SERVER ]T:
00000945: 2026-05-12T17:17:38:105472 [SERVER ]T:
00000945: 2026-05-12T17:17:39:116993 [SERVER ]T:
00000953: 2026-05-12T17:17:39:300155 [SERVER ]T: RetCode: SQL_ERROR SqlState: FA004 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Failed to authenticate the user '8ffcd3a2-3e1b-4d6a-9ef0-993832e9c228' in Entra ID (Authentication option is 'ActiveDirectoryServicePrincipal').
Error code 0xA190; state 41360 [1022502] (ar_odbc_conn.c:584)
00000953: 2026-05-12T17:17:39:300693 [SERVER ]T: Connection failure error codes are: 00026,00904,10054,4060,01222,55,64,121,1231,233,109,18401,6005,40613 (provider_syntax_manager.c:3076)
00000953: 2026-05-12T17:17:39:301391 [SERVER ]T: Table error codes are: 16943,208,11529,1904,1750,8180,207 (provider_syntax_manager.c:3135)
00000953: 2026-05-12T17:17:39:301412 [SERVER ]T: Table error codes are: 16943,208,11529,1904,1750,8180,207 (provider_syntax_manager.c:3135)
00000953: 2026-05-12T17:17:39:301506 [SERVER ]T: Data failure error codes are: 7125,8114,6522,511 (provider_syntax_manager.c:3106)
00000953: 2026-05-12T17:17:39:301530 [SERVER ]T: Data failure error codes are: 7125,8114,6522,511 (provider_syntax_manager.c:3106)
00000953: 2026-05-12T17:17:39:301793 [SERVER ]T: Connection failure error codes are: 00026,00904,10054,4060,01222,55,64,121,1231,233,109,18401,6005,40613 (provider_syntax_manager.c:3076)
00000953: 2026-05-12T17:17:39:302360 [SERVER ]T: Failed to connect [1022500] (sqlserver_endpoint_imp.c:2354)
00000953: 2026-05-12T17:17:39:302615 [SERVER ]T: Entering 'sqlserver_endpoint_free_imp' (sqlserver_endpoint_imp.c:2672)
00000953: 2026-05-12T17:17:39:300155 [SERVER ]E: RetCode: SQL_ERROR SqlState: FA004 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Failed to authenticate the user '8ffcd3a2-3e1b-4d6a-9ef0-993832e9c228' in Entra ID (Authentication option is 'ActiveDirectoryServicePrincipal').
Error code 0xA190; state 41360 [1022502] (ar_odbc_conn.c:584)
00000953: 2026-05-12T17:17:39:302360 [SERVER ]E: Failed to connect [1022500] (sqlserver_endpoint_imp.c:2354)
We are able to connect to the source endpoint using the same ODBC driver using python, on the same machine running Qlik Replicate:
((replicate) ) bash-5.1$ python3 test_odbc.py
Testing connection to Azure SQL Database with: Driver={ODBC Driver 18 for SQL Server};Server=tcp:sql-eap-weu-lgrr-qa.database.windows.net,1433;Database=eap-db-lgrr-qa-11;Authentication=ActiveDirectoryServicePrincipal;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;UID=8ffcd3a2-3e1b-4d6a-9ef0-993832e9c228;PWD=*******;
('Microsoft SQL Azure (RTM) - 12.0.2000.8 \n\tApr 14 2026 20:27:12 \n\tCopyright (C) 2025 Microsoft Corporation\n',)
✓ Connection successful
No other logs as we cant set up a task. Has anyone else had any experience with this error?
Hi Team,
We have one question regarding the quarterly DB2 zos source archival activities.
Previously, during a similar archival activity, we experienced very high latency issues due to huge transaction volumes generated in the source logs. Additionally, a few Qlik tasks encountered data missing issues because of resource constraints during heavy processing.
To mitigate the issue, we later increased the infrastructure resources by doubling the disk space, CPU, and RAM capacity.
Could you please help us understand the best practices or recommended approach for handling these kinds of large-volume archival activities? We would like to know the recommended planning, tuning, or operational strategies to minimize latency and avoid data loss/issues in Qlik replication tasks during such events.
Your guidance and recommendations would be very helpful for us.
Thanks,
Shyam Sundar.
Hi everyone,
I've been working on improving the structure and performance of my Qlik load scripts and front-end apps, and I want to make sure I'm following the most current best practices... not just what was recommended 3 or 4 years ago.
I'm looking for resources that cover topics like:
My question to the community: What are the most current and reliable sources you use to guide your development decisions? For example:
Any links, authors, or resources you'd recommend would be greatly appreciated. Thanks in advance!
Hi,
I am using a proxy to connect Talend Studio to the internet. While I can see the projects assigned to me in 'Studio Projects', the Git branches fail to load. Aside from *.github.com, what other URLs or endpoints need to be whitelisted for Git synchronization to work properly?
Thanks.
Thanks to those other links in the Qlik community, I managed to configure the connection between Entra ID and Qlik Sense through OIDC :
- Qlik Sense for Windows: How to configure OIDC with... - Qlik Community - 1812401
- How To: Configure Qlik Sense Enterprise SaaS to us... - Qlik Community - 1704442
However, I still have a problem with claims. When I disable OIDC optional claims, I can login successfully, but when I add them back to have information about my users such as email or display name, I have an error 400.
Did someone manage to make it work ?
Recently, our Salesforce connection has been encountering the following error:
INVALID_OPERATION: The SOAP Login operation is not available in the API version specified (56.0). Refer to the documentation for supported versions.
Our Salesforce connection version is 15.290.0 (Qlik Sense) and 15.160.0 (QlikView)
Is anyone else facing the same issue? Based on some Salesforce articles, it appears that the SOAP login method will be retired soon. Is there any plan from Qlik to update the connector to support the newer login method?
Thank you.
Hi Team,
We are facing an issue with Document CALs in QlikView Server.
The server shows all Document CALs as assigned, but when checking individual documents in QMC, many CAL assignments are not visible under User Documents → Document CALs.
We have already:
However, some Document CALs still appear to be occupied/orphaned and are not getting released.
Could anyone please suggest the recommended/safest way to release unused or stale Document CALs in QlikView?
Thanks in advance.
Hi all,
I’m trying to find details on the planned 2026 major releases for Qlik NPrinting, QlikView, and Qlik Sense, but I haven’t seen anything in the release notes or roadmap materials. I know there is a technical preview for Qlik NPrinting but no update on when the initial release is expected to come out.
If anyone has insight, confirmations, or links to official guidance, I’d really appreciate it.
Thanks in advance.
Using version "February 2025 SR1" although I didn't see that in the topic selection so I picked the 2024 version.
I have created a new NPrinting report, clicked Edit Template, and added a simple level and table. I can Preview as XLSX if there are only a handful of rows, but once I try to Preview with a large amount of data (like 300 rows, which is still only about 10% of the anticipated size), the Preview locks up with a Processing message. It does not time out or produce an error, and I usually abort after 30 minutes or so. Our internal support team does not see an issue on the server. Once I have this issue, the Preview locks up on even the small dataset again. They restarted all the services earlier in the week, and it worked again on the very small number of rows. Is it the case that the XLSX preview can't handle much data? I'm not sure how to continue developing the report without being able to preview with realistic data.