Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
we have a problem with Qlikview Server since 2 weeks. We have installed the Qlikview Server May2022 SR2 version.
When from a client we try to connect with NT autentication we receive the error in the subject title. Using Alternative Identity it connects properly.
I try to restart the qlikview service and nothing happens, restarting the machine the NT connection wroks properly for some time (2-3 hours) but at one moment it stop to works.
If I check the webserver log when it works I can read this, connecting with ip name
Warning Fail Connect to: ccnqlik2019 Error:No connection could be made because the target machine actively refused it [::ffff:192.168.14.74]:4747
20230407T121731.622+0200 Information Connect to server: ccnqlik2019
20230407T121733.625+0200 Information Connect to server: ccnqlik2019
20230407T121735.628+0200 Information Connect to server: ccnqlik2019
20230407T121737.631+0200 Information Connect to server: ccnqlik2019
this, connecting with machine name
20230407T123407.718+0200 Information Success Connect to: ccnqlik2019
When it doesn't works
20230407T102734.661+0200 Error Request failed: m_Comm.Receive() received zero bytes.
20230407T102734.661+0200 Error Request failed: m_Comm.Receive() received zero bytes.
20230407T102740.160+0200 Error Request failed: m_Comm.Receive() received zero bytes.
There is no antivirus and all ports are open on qlikview server. It seems an error based on port 4747
Any suggest?
Thank you
The error in the Web Server logs may mean that the QlikView Server is under heavy load/too busy to respond. Have you checked the QlikView Server Events log for errors/warnings? Best to have High Verbosity for logging enabled when troubleshooting.
Best Regards
Hi @menta,
Suggest that you start with the following two Qlik Knowledgebase articles:
Best Regards
Hi Chip,
I had already seen these KB. But they didn't help me. We don't use IIS but we use Qlikview webserver and port 4747 is open to all. The oddity is that if we receive the error and restart the server (not just the Qlik services) for a short time, the connection happens without problems.
The error in the Web Server logs may mean that the QlikView Server is under heavy load/too busy to respond. Have you checked the QlikView Server Events log for errors/warnings? Best to have High Verbosity for logging enabled when troubleshooting.
Best Regards