Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The other day, my scheduled publish tasks all failed and a scheduled metadata reload didn't finish. These tasks have all been running perfectly for months, every day. I am running NPrinting May 2022 SR4 and Qlik Sense Enterprise Feb 2023 patch 1. I see this error in the Scheduler log about 3 hours before the failures:
Qlik.NPrinting.Scheduler 22.15.14.0 Qlik.NPrinting.Scheduler.Service.PeriodicCleaner 20230810T021058.338-04:00 ERROR EWHSERVER2690 0 0 0 0 0 0 0 0 Unexpected error in CleanUp method. ERROR: System.Net.WebException: The remote name could not be resolved: '***server name***'↓↓ at System.Net.HttpWebRequest.GetResponse()↓↓ at Qlik.NPrinting.Repo.Service.HubPublishingService.SendRequestPayload[T](String address, String httpMethod, Byte[] payload, String contentType, String userId, String userDirectory) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\HubPublishingService.cs:line 283↓↓ at Qlik.NPrinting.Repo.Service.HubPublishingService.GetPublishedReports(Hub hub, Dictionary`2 md, String valueComparisonMethod) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\HubPublishingService.cs:line 581↓↓ at Qlik.NPrinting.Repo.Service.HubPublishingService.GetExpiringSharedContents(Hub hub) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\HubPublishingService.cs:line 443↓↓ at Qlik.NPrinting.Repo.Service.HubPublishingService.CleanUpExpiredContent(Hub hub) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\HubPublishingService.cs:line 466↓↓ at Qlik.NPrinting.Repo.Service.PeriodicCleanupService.<>c__DisplayClass11_0.<DeleteItems>b__2(ISession s, Guid id) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\PeriodicCleanupService.cs:line 168↓↓ at Qlik.NPrinting.Repo.Service.PeriodicCleanupService.<>c__DisplayClass18_1`1.<ExecuteBatchAction>b__0(ISession s) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\PeriodicCleanupService.cs:line 354↓↓ at Qlik.NPrinting.Repo.Service.SessionManager.<>c__DisplayClass7_0.<WithSession>b__0(ISession s) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo.Common\Service\SessionManager.cs:line 49↓↓ at Qlik.NPrinting.Repo.Service.SessionManager.WithSession[T](Func`2 body, IsolationLevel isolationLevel, Boolean readOnly) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo.Common\Service\SessionManager.cs:line 76↓↓ at Qlik.NPrinting.Repo.Service.PeriodicCleanupService.ExecuteBatchAction[T](IList`1 records, Action`2 action) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\PeriodicCleanupService.cs:line 347↓↓ at Qlik.NPrinting.Repo.Service.PeriodicCleanupService.CleanUp(PeriodicCleanUpType type) in C:\Jws\release-may2022-Zv2Y0uMG9\server\NPrinting\src\Repo\Service\PeriodicCleanupService.cs:line 105
A couple hours after that, an import task runs successfully, and then 45 minutes later, this error appears about 60 times:
Qlik.NPrinting.Scheduler 22.15.14.0 Qlik.NPrinting.Scheduler.Service.LoadBalancer 20230810T054549.664-04:00 WARN EWHSERVER2690 0 0 0 0 0 0 0 0 Connection navigator=qliksense;proxyurl=https://***servername***/;appid=3a9a0d38-cb35-4b5b-b590-e9f6bb11ca7a;identity=ewhserver2690\nprintadmin recorded an error in startup
And then this one:
Qlik.NPrinting.Scheduler 22.15.14.0 Qlik.NPrinting.Scheduler.Service.ConnectionStatusMonitor 20230810T054553.541-04:00 ERROR EWHSERVER2690 0 0 0 0 0 0 0 0 ConnectionStatusMonitor: Maximum number of errors reached and all allocations are on error for connection navigator=qliksense;proxyurl=https://***servername***/;appid=3a9a0d38-cb35-4b5b-b590-e9f6bb11ca7a;identity=ewhserver2690\nprintadmin. Setting connection status to error.
Any ideas what would cause the initial error? Thanks for your help.
Hi @Lauri
All this looks like domain network issues. The fact that server names couldn't be resolved means that there are underlying issues with network. Apart from that make sure all service account credentials are working as expected and that C drive on NPrinting server is not full (this is often forgotten and overlooked)
cheers
Hi,
Maybe the Windows Domain User that run the Qlik NPrinting services has the password expired or somebody changed it.
Be sure that the Run Verification in the connection page has lines green.
Best Regards,
Ruggero