Hi Team,

We're facing some issues with our Replicate installation on Red Hat Linux. We're unable to stop or restart services, and we're also having trouble accessing the Qlik Replicate Console. Any assistance you can provide would be greatly appreciated. When we kill process id after that we are able to start service also access URL what can be cause for this 

Thanks!

I have a SQL Server database that has merge replication configured with another SQL Server, I need to replicate some tables using Qlik Replicate, we know that CDC cannot be activated, I would like to know what the restrictions are in relation to transactional replication, if This impacts merge replication that already exists, if Qlik uses other logs than the one already being used by MERGE.

Hello,

I just finished a fresh install of Qlik NPrinting May 2021 SR2 and am looking to connect to Qlik Sense which is also on May 2021 (Patch 4).

When verifying the connection, I get all green checkmarks, but when it comes time to generating the Qlik metadata, it just times out with no intelligent error message:

When I check the NPrinting log files, I do see this:

20211124T113220.167-05:00 [39] INFO Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator - Engine.Navigator.QlikSense.SDK 21.14.5.0 Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator 20211124T113220.166-05:00 INFO MYNPRINTINGSERVER1 0 0 0 0 0 0 0 0 trying to get login cookie via a qlikTicket from: https://MYQLIKSENSESERVER1.fss.anitech.com/hub/?qlikTicket=CLjdwBN92wWXWzwJ

And then right above it, I see:

20211124T110319.461-05:00 [26] ERROR Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator - Engine.Navigator.QlikSense.SDK 21.14.5.0 Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator 20211124T110319.461-05:00 ERROR MYNPRINTINGSERVER1 0 0 0 0 0 0 0 0 An issue occurred in MashupServer.GetAuthenticationCookiesAndConsumeQlikTicket. Proceeding anyway by using Windows authentication to load the mashup page. ERROR: System.Net.WebException: The remote server returned an error: (400) Bad Request.↓↓ at System.Net.HttpWebRequest.GetResponse()↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.TryGetResponse(HttpWebRequest request) in C:\Jws\release-may2021-QJBWLpX4f\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\QRSApi.cs:line 92↓↓ at Engine.Navigator.QlikSense.SDK.QRSApi.GetQlikTicket(QlikSenseConnectionString conn) in C:\Jws\release-may2021-QJBWLpX4f\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\QRSApi.cs:line 437↓↓ at Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator.GetAuthenticationCookiesAndConsumeQlikTicket() in C:\Jws\release-may2021-QJBWLpX4f\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\Rendering\SenseAuthenticator.cs:line 98↓↓ at Engine.Navigator.QlikSense.SDK.Rendering.SenseAuthenticator.RefreshAuthCookies() in C:\Jws\release-may2021-QJBWLpX4f\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\Rendering\SenseAuthenticator.cs:line 74

Aside from generating the certificate from the Central node and copying it over to the NPrinting server, are there any other steps I need to take to get past this? The NPrinting metadata generation only fails because it seems like it's just simply timing out. Not sure where else to be looking. For background information, we also have three rim nodes which are used as load balancing engines, but I don't think I need to generate anything from them.

Thanks for your time!

Hi Support,

We have recently seen an issue where the Qlik Enterprise Manager service fails to start with the QEM logs indicating the following error:
"[ERROR] REPO-E-FACSQLREP, Failed to connect to SQLite repository 'C:\Program Files\Attunity\Enterprise Manager\data\rtdata.sqlite' "

We were able to resolve the issue by stopping the QEM service and renaming the rtdata.sqlite file to rtdata_old.sqlite, and then renaming the rtdata.new.sqlite file to rtdata.sqlite. After then running the command to upgrade the repository (aemctl.exe repository upgrade), the QEM service was able to run and the console could be accessed.

Previously when we have seen an issue with a data repository file it has been a result of memory or disk space issues on the server. However, in this case, there have been no reported memory/disk space issues on the server. What we'd like to understand is what are the possible reasons the rtdata.sqlite file becomes unreadable/corrupted.

This instance of Enterprise Manager is v2023.11.0.259

Thanks,

Nak